7. Writing & Documentation

Automates updating API documentation to reflect real-time API changes, ensuring documentation accuracy and consistency.

Creates plan documents from templates for new implementation work, feature documentation, and development task organization.

Exports design documentation to PDF, HTML, or Markdown for distribution, presentations, and archiving.

Reviews RSPress documentation for completeness, accuracy, and Twoslash code example quality.

Performs comprehensive quality audits on CLAUDE.md context files to ensure efficiency, token optimization, and release readiness.

Archives outdated design documentation, including superseded or deprecated features, to maintain a current and organized knowledge base.

Provides Zinsser-based writing standards for clear technical documentation, commit messages, and PR descriptions.

Provides version-specific, accurate information on Zellij keyboard shortcuts, configuration, and feature behavior by cross-referencing official documentation and actual configurations.

Automates documentation of implemented features by analyzing conversation context and syncing with SPECLAN specification directory.

Creates structured Product Requirements Documents (PRDs) with acceptance criteria for planning new features, migrations, or refactors.

Generates clear and concise technical documentation for software components, functions, APIs, and features.

Conducts user interviews to clarify requirements and generates a comprehensive Product Requirement Document (PRD).

Automates documentation maintenance by detecting code-documentation drift, validating examples, and generating/updating diagrams.

Transforms task-specific insights into reusable project documentation for consistent knowledge sharing and accessibility.

Extracts and codifies key learnings from planning sessions using files, converting them into structured documentation for reference.

Automates documentation updates by reverse-syncing code changes to documentation files, ensuring living documentation remains accurate and current.

Guides documentation writers to maintain cautious and flexible language, avoiding absolute terms in project directives and documentation files.

Generates clear documentation for skill functionality and automatic invocation conditions.

Provides standardized documentation for project conventions including error handling, logging, naming, and testing during SDD workflows.

Creates natural-sounding technical documentation, marketing copy, and emails. Reviews text for unnatural LLM patterns.

Provides a structured workflow for writing, refining, and reviewing technical specifications, designs, and test plans in a non-negotiable spec-driven development process.

Guides proper usage of Mintlify components to maintain consistency and accuracy in StackOne documentation within the group-documentation/docs/ directory.

Generates and edits high-quality markdown content for documentation, READMEs, and technical writing, ensuring proper syntax and structure.

Generates high-quality, spell-checked text content for HTML documents, including prose and descriptions.