Documentation as Code

Writes Java documentation: Javadoc comments, README files. Generates docs via Maven javadoc plugin.

Writes documentation in code: JSDoc/TSDoc comments, README files, API examples. Generates docs via TypeDoc.

Writes Python documentation: docstrings (Google/NumPy style), README files. Generates docs via Sphinx.

Writes documentation in code: Rust doc comments (///), README.md, examples in doc tests. Understands cargo doc generation.

Understands docs-as-code principles: Markdown/AsciiDoc, version-controlled documentation alongside infrastructure code. Can write runbooks and operational procedures in Git-managed repositories. Follows team conventions for README files and architecture decision records (ADRs).

Understands documentation as code principle: documentation in Git alongside code. Writes README for infrastructure repositories, creates simple runbooks in Markdown. Knows Markdown basics, uses templates for documentation.

Documents infrastructure components in docs-as-code format: README.md for Terraform modules with input/output descriptions, basic runbooks in Markdown for routine operations. Uses terraform-docs for module documentation auto-generation and keeps records of infrastructure decisions.

Understands docs-as-code principles for language tooling projects: grammar documentation, parser behavior specs, and API references in version-controlled formats. Writes documentation alongside compiler/LSP code changes. Follows team standards for technical documentation.

Understands docs-as-code principles for test documentation: test plans, test cases, and checklists in Markdown/Git. Maintains test documentation alongside source code in version control. Follows team conventions for organizing and updating QA documentation.

Documents security findings: vulnerability reports, test results, security checklists in Markdown. Follows documentation templates.

Knows basic documentation-as-code concepts for release engineering and can apply them in typical tasks. Uses standard tools and follows established team practices. Understands when and why this approach is applied.

Understands the documentation-as-code principle: documentation stored in Git, versioned alongside code, reviewed through pull requests. Can create and edit Markdown files in a repository, submit PRs with documentation changes.

Implements docs-as-code: comprehensive Javadoc, Spring REST Docs, AsciiDoc for guides.

Implements docs-as-code: OpenAPI generation from NestJS, TypeDoc for libraries, Docusaurus for guides. Integrates in CI.

Implements docs-as-code: Sphinx/MkDocs, OpenAPI generation, code examples as tests.

Implements docs-as-code: comprehensive rustdoc, mdBook for guides, automated API docs generation. Integrates documentation in CI.

Documents cloud infrastructure as code: terraform-docs for automated module README generation, Architecture Decision Records (ADR) for key decisions. Maintains diagrams-as-code through Mermaid/PlantUML for network topologies and architecture diagrams.

Implements documentation as code: auto-generation from Terraform (terraform-docs), Helm (helm-docs), OpenAPI. Configures MkDocs/Docusaurus for internal documentation, CI/CD for auto-publishing. Creates architecture decision records (ADR).

Implements docs-as-code practices in the team: documentation review as part of PR process, automated doc builds, and integration with CI/CD. Understands trade-offs between wiki-based and Git-based documentation. Ensures architecture decisions are captured as ADRs.

Creates comprehensive infrastructure documentation as code: ADR (Architecture Decision Records) for infrastructure decisions, runbooks with automatic CI validation. Generates network diagrams from Terraform through inframap, maintains inventory documentation and configures automatic publishing through MkDocs.

Implements docs-as-code for language tooling: auto-generated API docs from source, interactive grammar playground documentation, and versioned language specification. Uses documentation generators (TypeDoc, rustdoc, godoc) as part of build pipeline. Maintains changelog automation from commit history.

Implements docs-as-code workflows for QA: test documentation auto-generated from test management tools, living test plans updated with each release, and traceability matrices in version control. Uses static site generators for test documentation portals. Automates test coverage reports as documentation artifacts.

Creates security documentation: test plans, security assessment reports, runbooks in git-managed docs. Automates report generation.

Confidently applies documentation-as-code for release engineering in non-standard tasks. Independently selects the optimal approach and tools. Analyzes trade-offs and proposes improvements to existing solutions.

Implements docs-as-code in the development workflow: documentation requirements in PR checklists, automated API reference generation (OpenAPI, GraphQL schema), and developer guides co-located with code. Establishes documentation standards for the team and ensures consistency.

Fully works in docs-as-code workflow: branch, write, PR, review, merge, deploy. Configures CI/CD for automated documentation building and publishing. Uses linting (markdownlint, vale) for text quality control.

Designs documentation strategy: living docs, Spring REST Docs automation, versioned API docs.

Designs documentation strategy: automated API docs, living documentation, versioned guides. Implements docs-as-code pipeline.

Designs documentation strategy for Python services: Sphinx/MkDocs-driven API documentation with autodoc, type-annotated interface references, and versioned migration guides. Implements doctest-based documentation verification. Creates comprehensive developer onboarding docs and operational runbooks co-located with service code.

Designs documentation strategy: living documentation, automated architecture diagrams, versioned docs. Implements docs-as-code pipeline.

Designs documentation-as-code for cloud platform: auto-generated architecture diagrams from Terraform state, self-documenting modules with examples, automated docs pipeline in CI. Introduces Backstage/internal developer portal with up-to-date infrastructure documentation.

Designs documentation system for DevOps: unified portal (Backstage) with auto-generated documentation, runbooks with monitoring integration. Implements docs-as-code pipeline: automated validation, link checking, freshness alerts.

Designs documentation architecture for engineering teams: developer portals (Backstage, Docusaurus), automated doc pipelines, and documentation quality metrics. Ensures documentation coverage tracks with feature delivery. Establishes doc review processes and ownership models. Mentors team on effective technical writing.

Designs infrastructure documentation system: auto-generation from IaC code (terraform-docs, ansible-doc), live architecture diagrams through Mermaid/D2, service catalog integration. Implements documentation testing (broken links, schema validation), creates postmortem templates and designs knowledge base for on-call engineers.

Designs comprehensive documentation systems for language tools: interactive documentation with embedded code execution, version-aware API references, and migration guides generated from breaking change detection. Implements documentation testing (doctests) as part of CI. Mentors team on documentation architecture.

Designs documentation systems for QA processes: living quality dashboards, automated test evidence generation, and compliance documentation as code. Implements bidirectional traceability between requirements, test cases, and defects in version control. Mentors team on effective QA documentation practices.

Designs security documentation framework: threat model docs, security architecture docs, automated evidence collection for compliance. Versions security policies.

Expertly applies documentation-as-code for release engineering to design complex systems. Optimizes existing solutions and prevents architectural mistakes. Conducts code reviews and trains colleagues on best practices.

Designs enterprise documentation architecture: multi-project documentation sites, cross-reference systems, and architecture documentation frameworks (C4, arc42). Implements documentation pipelines that aggregate content from multiple repositories. Creates documentation governance standards for client-facing technical deliverables.

Designs documentation strategy for the product: living documentation, automated API docs from source annotations (Swagger, TypeDoc), versioned guides aligned with release cycles. Implements documentation quality gates in CI/CD. Creates architectural documentation standards (ADRs, C4 diagrams) and ensures team adoption.

Designs scalable docs-as-code processes: multi-repo documentation, cross-references, automated content generation. Implements content reuse (snippets, includes, variables). Creates custom CI checks for documentation quality gates.

Defines documentation standards: mandatory Javadoc, API doc requirements, review process.

Defines documentation standards: mandatory TSDoc, API doc requirements, review process. Implements documentation quality gates.

Defines documentation standards: mandatory docstrings, review process, quality gates.

Defines documentation standards: mandatory doc comments, review process, freshness metrics. Implements documentation quality gates.

Defines infrastructure documentation standards: ADR template, runbook structure, service catalog format. Introduces docs-as-code workflow — PR-based updates, automated freshness checks, documentation coverage metrics. Trains teams on documentation culture.

Defines organizational documentation standards: mandatory documentation for each service, ADR and runbook templates, review processes. Designs Internal Developer Portal with service catalog, automated documentation and search.

Defines documentation-as-code strategy for the engineering organization. Establishes documentation standards, review processes, and quality metrics across teams. Drives developer portal adoption for centralized documentation discovery. Ensures documentation practices support compliance and audit requirements.

Defines infrastructure documentation standards for the organization: mandatory sections for each Terraform module, runbook and playbook templates, ADR standards. Implements docs-as-code pipeline with review process, reviews team documentation for completeness and coordinates on-call handbook creation.

Defines documentation strategy for language tooling platform: unified documentation portal, multi-version documentation hosting, and contributor documentation standards. Establishes documentation review processes and quality gates. Creates guidelines for interactive examples and playground integration in documentation.

Defines Documentation as Code strategy at the team/product level for QA documentation. Establishes standards for test documentation versioning. Conducts reviews.

Defines security documentation standards: required documents per project, templates, review process. Implements docs-as-code for security policies and procedures.

Establishes documentation-as-code standards for the release engineering team and makes architectural decisions. Defines the technical roadmap considering this skill. Mentors senior engineers and influences practices of adjacent teams.

Defines documentation strategy for consulting/architecture practice. Establishes standards for architecture deliverables, solution documentation, and client-facing technical content. Creates documentation templates and frameworks for repeatable engagements. Drives adoption of documentation-as-code across client projects.

Defines documentation-as-code strategy at the product/department level. Establishes standards for API documentation, architecture decision records, and developer guides. Drives adoption of developer portal (Backstage, Docusaurus) for centralized documentation. Creates governance for documentation ownership and maintenance.

Defines organizational docs-as-code standard: workflows, branching strategy for docs, review processes, quality metrics. Coordinates team migration to docs-as-code approach. Creates contribution guidelines for developers.

Shapes documentation strategy for Java platform organization: Javadoc standards, developer portal with automated API reference aggregation, and documentation governance. Drives documentation as a competitive advantage for internal platform adoption. Establishes documentation quality as an engineering KPI across Java teams.

Shapes documentation strategy: platform-wide docs-as-code, automated generation, developer portal. Defines documentation governance.

Shapes documentation strategy for Python platform organization: Sphinx/MkDocs infrastructure, automated doc builds from type hints and docstrings, and developer portal governance. Drives documentation as a core engineering practice across Python teams. Establishes open-source documentation standards for public Python packages.

Shapes documentation strategy: platform-wide docs-as-code, automated generation, developer experience. Defines documentation governance.

Shapes enterprise-level documentation strategy: unified service catalog, automated architecture documentation from IaC, knowledge base for operational procedures. Designs internal developer platform with self-service docs, API reference and interactive architecture explorer.

Develops knowledge management strategy for engineering organization: Internal Developer Portal (Backstage/Port), automated documentation, living docs. Defines knowledge platform architecture: from auto-generation to AI-powered search and recommendations.

Defines enterprise documentation strategy: platform docs-as-code, developer experience standards, and documentation governance across the organization. Drives cultural shift toward treating documentation as a first-class engineering artifact. Evaluates and selects documentation platform investments.

Shapes knowledge management strategy for company infrastructure: Internal Developer Portal architecture with auto-generated documentation, Backstage integration with IaC repositories. Defines technical writing standards for infrastructure, AI-assisted documentation roadmap and documentation coverage metrics for compliance.

Defines organizational documentation strategy for language tooling ecosystem: unified documentation standards, multi-language documentation infrastructure, and open-source documentation practices. Drives documentation as a competitive advantage for developer tool adoption. Shapes industry standards for language documentation.

Defines enterprise QA documentation strategy: standardized quality reporting, compliance documentation automation, and test evidence management as code. Drives adoption of living documentation practices across QA teams. Shapes organizational culture around documentation-driven quality assurance.

Designs security knowledge management: organizational security wiki, automated policy distribution, compliance evidence management. Defines documentation governance.

Shapes documentation-as-code strategy for release engineering at the organizational level. Defines best practices and influences technology choices beyond their own team. Is a recognized expert in this area.

Defines enterprise documentation strategy across all architecture practices. Establishes documentation as a core deliverable in architecture governance. Drives standardization of architecture documentation frameworks (TOGAF, C4) across the organization. Influences industry practices through published reference architectures and documentation standards.

Defines enterprise documentation-as-code strategy: platform-level documentation infrastructure, developer portal governance, and documentation quality as an engineering KPI. Shapes organizational culture around documentation as a competitive advantage. Drives cross-team documentation standardization and knowledge management.

Shapes documentation-as-code strategy at the corporate level. Defines how docs-as-code integrates with SDLC, developer experience, and knowledge management. Ensures scalability of the approach as the organization grows.