Documentation Workflow
Update documentation to reflect code changes. Ensure all user-facing features are documented and API changes are recorded.
Acceptance Criteria
- • README updated if user-facing features changed
- • API documentation updated for endpoint changes
- • Code comments added for complex logic
- • CHANGELOG updated with notable changes
- • Migration guide written if breaking changes
Steps
- •Identify what code changed (read git diff or task description)
- •Determine documentation impact:
- •New features need user docs
- •API changes need API docs
- •Breaking changes need migration guide
- •Update relevant documentation files
- •Add inline code comments where logic is complex
- •Update CHANGELOG.md if not already done
- •Verify all links and references are valid
Documentation Types
User Documentation
- •README.md - Quick start, installation
- •docs/USER-GUIDE.md - Comprehensive usage
API Documentation
- •docs/API-REFERENCE.md - Endpoint specs
- •OpenAPI/Swagger if applicable
Developer Documentation
- •DEVELOPERS.md - Setup, architecture
- •CLAUDE.md - Codebase conventions
Best Practices
- •Use clear, concise language
- •Include code examples
- •Keep docs close to code when possible
- •Test all documented commands