7. Writing & Documentation

Step-by-step guide for creating and updating Claude skills to extend capabilities with specialized knowledge, workflows, or tool integrations.

Summarizes documentation hub state, providing system architecture, module responsibilities, technology stack, and glossary overviews.

Records architectural decisions and trade-offs to a markdown file for team reference and historical clarity during development.

Guides users through a structured workflow for co-authoring technical documentation, proposals, and specifications, ensuring clarity and reader effectiveness through iterative refinement.

Introductory wiki for the skills system, detailing mandatory workflows, search tools, and brainstorming triggers for effective implementation.

Analyzes codebase documentation alignment, detects drift, identifies undocumented code, and extracts missing glossary terms to improve documentation quality.

Applies Test-Driven Development to process documentation: test with subagents before writing, then iterate for bulletproof results.

Automates creation of core project documentation files (system architecture, key responsibilities, glossary, tech stack) via codebase analysis.

Offers comprehensive guidance for navigating and utilizing the official Godot game engine documentation, including API references and tutorials.

Provides deep contextual insights from Ryan's technical writings on OpenPKG, TypeScript tooling, and agent-native architecture.

Comprehensive Godot Engine knowledge base integrating official documentation and source code analysis for developers.

Generates comprehensive Product Requirements Documents (PRDs) for new features or projects, detailing specifications, goals, and requirements.

Provides expert guidance on crafting clear and effective acceptance criteria for user stories, covering formats, best practices, and quality standards.

Accesses official Microsoft documentation for Azure, .NET, Microsoft 365, and other Microsoft technologies, including architecture, tutorials, and best practices.

Generates detailed feature specifications with phases, test cases, and progress tracking through user interviews for new feature planning.

Accesses Base UI (@base-ui/react) official documentation for component, handbook, and API inquiries.

Automates documentation synchronization by analyzing code changes, detecting drift, and proposing structure updates to maintain alignment with the codebase.

Reference guide for GSD checkpoint documentation, supporting teams in navigating development milestones and processes.

Updates and maintains Python documentation to adhere to Google-style standards, including docstrings, inline comments, and import organization for clarity and consistency.

Provides a concise overview of recent features and changes in the GSD product through documented release notes.

Generates clear, step-by-step task plans from requirements specifications to guide development before coding begins.

Generates Product Requirements Documents (PRDs) with user stories for rube-goldberg-tui task orchestration, convertible to automated execution formats.

Reference guide for the continuation format in GSD sessions, enabling standardized session documentation and communication.

Ensures strict compliance with markdownlint rules and professional markdown best practices for technical documentation.