doc-workflowslisted

# Documentation Workflows ## Purpose Automate documentation generation and maintenance for codebases and products. Generate READMEs, API documentation, knowledge base articles, and keep docs in sync with code changes. Implement doc-driven development patterns where specs are written before code. ## When to Use - User asks to write or update documentation - User needs a README generated for a project or module - User asks to create API documentation - User wants to document code changes or architecture decisions - User needs a knowledge base article or wiki page - User asks to keep docs in sync with code - User wants to implement llms.txt for AI-friendly documentation ## Examples **Example 1: README generation** ``` User: "Generate a README for this project" Claude: [Uses doc-workflows] I'll analyze the project structure: - Detected: TypeScript/React project with Supabase backend - Package.json scripts: dev, build, test, lint - Environment variables: 4 required (.env.example found) # Project Name ## Overview [Generated from package.json description and CLAUDE.md] ## Quick Start ```bash npm install cp .env.example .env # Fill in required values npm run dev ``` ## Architecture [Generated from directory structure analysis] ## API Reference [Generated from route files] ``` **Example 2: Doc sync after code changes** ``` User: "I just refactored the auth module, update the docs" Claude: [Uses doc-workflows] Analyzing changes: Files modified: - src/auth/jwt.ts (renamed