docslisted

# Docs — Project Documentation Generator Generate and update project documentation following the AI-DLC documentation standard. ## Usage ``` /docs # Update all documentation (README + manuals) /docs readme # Generate/update README.md only /docs changelog # Generate/update CHANGELOG.md only /docs security # Generate/update SECURITY.md only /docs manuals # Generate/update docs/manuals/ guides only /docs all # Generate everything ``` ## Documentation Standard All documentation follows the AI-DLC documentation standard. These are the rules — follow them exactly. ## README.md Structure The README is the primary document. It must be comprehensive, well-organized, and audience-aware. Length should be proportional to project complexity — a simple CLI tool may need 100-200 lines, while a full-stack application may need 400-700 lines. Prioritize completeness and accuracy over length targets. Follow this exact section order: ```markdown # Project Name **One-sentence tagline describing what it does and why.** > **Status:** Current deployment state, known blockers, phase info. --- ## Table of Contents [Anchor-linked navigation to every major section] --- ## How It Works [ASCII diagram or Mermaid showing the data/workflow pipeline] [Numbered steps explaining the flow] ## Features [Bulleted by category — e.g., Core, Analytics, Operational] [Format: **Feature name** — one-sentence description] ## Architecture [ASCII or Mermaid diagr