7. Writing & Documentation

Fixes syntax errors in Mermaid diagrams used within technical documentation.

Configures, manages, and troubleshoots glossary terms for Docusaurus documentation sites, including feature explanations.

Creates structured implementation plans with task breakdown, dependency mapping, risk assessment, and file-level details for features and projects.

Enforces consistent style in documentation and code via markdown structure, voice compliance, and formatting validation against project standards.

Guides users in creating structured product requirements documents (PRDs) with user stories, acceptance criteria, and business rationale through collaborative workshopping.

Generates comprehensive technical design documents via collaborative workshopping, including discovery, alternatives exploration, and iterative feedback for new features or projects.

Generates comprehensive technical documentation for UI components including Storybook 9 stories, API references, usage examples, and migration guides.

Generates comprehensive documentation for component libraries including API references, usage examples, and migration guides.

Guides product managers in creating concise product one-pagers to articulate opportunities and requirements before development begins.

Generates maintainable technical documentation from legacy codebases, prioritizing future developer needs and system understanding.

Generates structured implementation plans with bite-sized tasks for engineers new to a codebase, enabling rapid onboarding and task execution.

Edits Mintlify documentation site, ensures docs.json consistency, and runs accessibility and broken-link checks.

Edits LCP protocol documentation in BOLT-style, covering TLVs, message formats, and state flow within the docs/protocol/ directory.

Lists all available skills and their activation methods for user reference.

Transforms markdown notes into engaging technical blog posts for both programmers and non-technical readers.

Uses test-driven development principles to validate process documentation through subagent testing and iterative refinement.

Offers a structured guide for repository navigation, specifying applicable Codex skills (e.g., go-lcpd, protocol spec) for each section.

Validates specification files for completeness, consistency, and adherence to standard formats.

Analyzes requirements and Event Storming outputs to generate structured specifications, enforcing separation of requirements from implementation through document-centric workflows.

Generates WYSIWID-style design documentation for Go projects, maintaining terminology consistency with the codebase.

Generates architectural wikis with source code traceability, including overviews, module docs, and interactive static sites for codebase structure explanation.

Promotes inclusive and respectful terminology in code, documentation, and comments to ensure accessibility and professionalism.

Simulates a skeptical peer reviewer to identify weak claims, missing baselines, and unclear explanations in academic papers before submission.

Automates codebase documentation synchronization by auditing and updating Swagger, feature guides, and general documentation.