7. Writing & Documentation

Standardizes clear, executable, and maintainable usage examples for APIs, CLIs, libraries, and frameworks through documented patterns.

Enables technical documentation creation with Mermaid diagrams, complex tables, code blocks, and mathematical expressions using GitHub Flavored Markdown standards.

Specializes in multilingual documentation, i18n framework implementation, and translation-ready content creation with quality assurance.

Applies the Diátaxis framework to organize documentation into tutorials, how-to guides, reference, and explanation for structured content management.

Guides creation of high-quality README files with scannable structure, plain language, and user-focused content to welcome and guide developers.

Validates markdown links in documentation for format, path, broken, and external link compliance.

Enables token-efficient knowledge delivery through layered disclosure (metadata → content → resources), optimizing context usage and scalability for documentation systems.

Converts vague requirements into measurable specifications using UX principles and quantification frameworks for clear technical documentation.

Guide for creating English-only content on ose-platform-web Hugo site using PaperMod theme, covering structure, date-prefixed filenames, and frontmatter requirements.

Organizes command documentation with consistent structure, usage examples, and troubleshooting sections to ensure clarity and maintainability.

Guides creation of testable acceptance criteria using Gherkin syntax (Given-When-Then) for user stories and specifications.

Enforces universal markdown content quality standards including active voice, heading hierarchy, accessibility compliance, and professional formatting for documentation across platforms.

Verifies factual accuracy in technical documentation using WebSearch and WebFetch, covering syntax, versions, code, and API validation with confidence classification.

Creates standardized runbooks for incident response, troubleshooting, and recovery procedures to ensure reliable system operations and effective on-call readiness.

Provides standardized reference documentation structure for agents, including project guidance, conventions, related agents, and Skills.

Provides a keyword-searchable interface for accessing AIWorkflowOrchestrator project specifications, ensuring consistency with design and implementation.

Structures complex problem-solving into clear, evidence-based reasoning steps with concise summaries for accountable decision documentation.

Applies IEEE 830 and Doc as Code standards to structure technical documentation, ensuring reusability and clarity through templates and validation workflows.

Designs documentation architecture with topic-based organization, 500-line file splitting, and naming conventions to enhance maintainability and discoverability.

Provides a comprehensive guide for creating content on ayokoding-web Hugo site using Hextra theme, including bilingual strategy, annotation standards, and frontmatter patterns.

Provides best practices for RESTful API documentation using OpenAPI/Swagger, covering resource design, authentication, and error responses.

Assists in defining testable acceptance criteria using Given-When-Then format for clear user story specifications and verification steps.

Transforms user ideas into structured technical specifications (intent.md) and human summaries (overview.md) for development alignment and stakeholder communication.

Generates human-readable reports from technical Intent specifications, converting them into clear documentation for stakeholders and team members in multiple formats.