7. Writing & Documentation

Audits and refines system context documents for code alignment, C4 model compliance, and boundary clarity before finalization.

Drafts Architecture Decision Records (ADRs) with emphasis on clarity, formatting, and alignment with architectural values for comprehensive software design documentation.

Converts academic PDFs with formulas, figures, and references into clean Markdown format for seamless editing and documentation workflows.

Drafts and maintains system-context.md to ensure a single source of truth for system boundaries, ubiquitous language, and data flows.

Automates updating technical documentation following code changes, triggered by keywords like 'update docs' or 'update README'.

Generates clear, rigorous technical specifications using standardized templates for development alignment and implementability.

Refines technical specifications for clarity, consistency, and completeness, eliminating logical gaps and ambiguities.

Step-by-step guide for creating and scaffolding a new plugin in the marketplace.

Offers design principles and best practices for creating and organizing Claude Skills, emphasizing minimalism and purpose-focused design.

Automates Architecture Decision Record (ADR) creation using the OODA Loop, capturing scope, trade-offs, and formalizing decisions as mandatory blueprints for architectural design.

Step-by-step guide for adding new skills to existing plugins within the marketplace platform.

Creates a strategic plan for visualizing Architecture Decision Records (ADRs), including diagram selection, definition of terms, and quality assurance review.

Creates and revises scientific manuscripts, research papers, grant proposals, and literature reviews adhering to IMRAD structure and academic citation standards.

Drafts comprehensive design documents from domain models and technical specifications, enabling self-review and user consensus for implementation blueprints.

Generates a structured summary of AI sessions including task details, models used, and actions, saved as a Markdown file for documentation.

Guides tracking of numerical claims in the MOSAIC research paper to ensure accuracy and consistency before data incorporation.

Generates structured Product Requirements Documents (PRDs) for feature planning, including acceptance criteria.

Generates structured playbooks for Daedalus PRD user stories, providing step-by-step guidance for UI walkthroughs and evidence capture during testing.

Generates a product management constitution document from template, establishing project constraints and domain information for new initiatives.

Generates a structured Product Requirements Document (PRD) from product ideas or validated brainstorming sessions, converting concepts into clear specifications.

Generates structured design documents translating feature requirements into architectural specifications for AI implementation.

Guides conversion of bullet-point content into polished technical articles with natural language and professional style.

Generates clear and concise commit messages following standard conventions for version control systems.

Automates summarization of uncommitted Markdown content from source URLs, verifies facts, and enhances documentation notes.