<essential_principles>
</essential_principles>
- Generate full documentation suite - README, CONTRIBUTING, CODE_OF_CONDUCT, CHANGELOG, architecture, API docs
- Generate a single document - Create or replace one specific document
- Update existing documentation - Refresh docs based on code changes
- Audit documentation - Check what's missing or outdated
Wait for response before proceeding.
After reading the workflow, follow it exactly.
<reference_index>
All domain knowledge in references/:
Styling: github-styling.md (badges, emoji, collapsible sections, modern conventions) Document Types: doc-types.md (what each document should contain, best practices) Code Analysis: code-analysis.md (how to extract info from source files) </reference_index>
<template_index>
Output templates in templates/:
| Template | Purpose |
|---|---|
| readme-template.md | Modern README with all sections |
| contributing-template.md | Contribution guidelines |
| code-of-conduct-template.md | Community standards |
| changelog-template.md | Version history format |
| architecture-template.md | System design documentation |
| api-docs-template.md | API reference format |
| </template_index> |
<workflows_index>
| Workflow | Purpose |
|---|---|
| generate-full-suite.md | Create complete documentation set |
| generate-single-doc.md | Create one specific document |
| update-docs.md | Refresh existing docs from code |
| audit-docs.md | Check documentation completeness |
| </workflows_index> |
<success_criteria> Documentation is complete when:
- All generated docs accurately reflect the codebase
- README provides working quick-start example
- Installation instructions are tested
- API documentation covers all public interfaces
- Styling is consistent across all documents
- Links between documents work correctly </success_criteria>