7. Writing & Documentation

Generates structured task plans from specifications before code implementation, ensuring clear development pathways.

Automates compression of technical documentation while preserving execution equivalence via validation checks.

Step-by-step guide for creating new Mastra agents and verticals within the Hey Jarvis MCP project.

Automates documentation synthesis from Codex logs, outputting structured content to the repository's docs/ directory.

Updates README documentation to reflect current gameplay mechanics and observation space specifications in AI/ML projects.

Enforces concise and clear technical writing standards for standalone documentation in Markdown and AsciiDoc, excluding code documentation.

Provides examples and patterns for writing effective agent and skill descriptions used as routing keys in Claude's invocation system.

Generates content using MDX, enabling Markdown with embedded JSX components for documentation, blogs, and content-heavy sites.

Automates correction of missing or incomplete JSDoc comments, module-level documentation, and @returns tags in code.

Generates comprehensive technical documentation including READMEs, API specs, changelogs, runbooks, and SDK code from project analysis.

Translates Doc-Smith generated documentation into multiple languages with batch processing support for documents and images.

Generates and updates technical documentation from code repositories, text files, and media assets, supporting creation, structure building, and modification.

Validates structure, content, and integrity of Doc-Smith documentation including YAML, links, and image paths.

Analyzes differences between English master and target language i18n files, generating task manifests with missing keys and English values for translation teams.

Validates translations by checking placeholder preservation, length, encoding, and common errors for i18n file updates and review.

Translates English text to target languages while preserving placeholders and formatting for UI strings, i18n, and localization needs.

Determines if strings require translation in localization workflows, enabling validation of translation files and task list creation.

Automates creation of technical documentation including API references, README sections, and migration guides through codebase analysis.

Automates synchronization of technical documentation with codebase, updating auto-generated sections and validating cross-references.

Creates detailed implementation plans with code examples, file paths, and verification steps for engineers transitioning between development tasks or onboarding to new codebases.

Guides creation of compact, effective technical documentation including API specs, READMEs, and architecture guides.

Creates Hugo-formatted blog posts for LeetCode problem solutions using standard templates and current timestamps from user-provided problem statements.

Creates user stories, requirements, and feature specifications for software development projects.

Reviews and validates user story documents to ensure requirements are clear and ready for development.