documentation-engineer▌
charon-fan/agent-playbook · updated Apr 8, 2026
Expert in creating clear, comprehensive, and maintainable technical documentation.
Documentation Engineer
Expert in creating clear, comprehensive, and maintainable technical documentation.
When This Skill Activates
Activates when you:
- Ask to write documentation
- Request README creation
- Mention "docs" or "document this"
- Need API documentation
Documentation Types
1. README
Every project should have a README with:
# Project Name
Brief description (what it does, why it exists)
## Quick Start
Installation and usage in 3 steps or less.
## Installation
Detailed installation instructions.
## Usage
Examples of common usage patterns.
## Configuration
Environment variables and configuration options.
## Development
How to run tests, build, and develop locally.
## Contributing
Guidelines for contributors.
## License
License information.
2. API Documentation
For each endpoint/function:
- Description: What it does
- Parameters: Name, type, required/optional, description
- Return value: Type and structure
- Errors: Possible errors and conditions
- Examples: Usage examples
3. Code Comments
Comment why, not what:
// Bad: Sets the count to zero
count = 0;
// Good: Reset count for new measurement cycle
count = 0;
// Bad: Check if user is admin
if (user.role === 'admin') {
// Good: Only admins can bypass approval workflow
if (user.role === 'admin') {
4. Architecture Documentation
- System overview
- Component relationships
- Data flow
- Design decisions
- Trade-offs considered
Documentation Principles
- Be Clear: Use simple, direct language
- Be Concise: Respect the reader's time
- Be Accurate: Keep docs in sync with code
- Be Complete: Cover all public interfaces
- Be Current: Update docs when code changes
Writing Guidelines
Headings
- Use sentence case for headings
- Start with a verb or noun
- Be descriptive
Code Examples
- Show before/after when appropriate
- Include import statements
- Show expected output
- Handle edge cases
Links
- Use relative links for internal docs
- Include anchors for sections
- Test that links work
Diagrams
- Use Mermaid for flowcharts and sequences
- Keep diagrams simple
- Add a title and legend
Documentation Checklist
README
- Project description
- Quick start guide
- Installation instructions
- Usage examples
- Configuration guide
- Contributing guidelines
Code Docs
- All public functions documented
- Parameters and returns documented
- Examples provided for complex functions
- Edge cases documented
API Docs
- All endpoints documented
- Request/response schemas
- Authentication requirements
- Error responses documented
- Rate limits documented
Scripts
Generate documentation structure:
python scripts/generate_docs.py
Validate documentation:
python scripts/validate_docs.py
References
references/readme-template.md- README templatereferences/api-template.md- API documentation templatereferences/style-guide.md- Documentation style guide
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★56 reviews- ★★★★★Chaitanya Patil· Dec 28, 2024
documentation-engineer reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Arya Smith· Dec 28, 2024
documentation-engineer has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Liam Park· Dec 24, 2024
Registry listing for documentation-engineer matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Aisha Martin· Dec 16, 2024
documentation-engineer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Piyush G· Nov 19, 2024
I recommend documentation-engineer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Arya Zhang· Nov 19, 2024
documentation-engineer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Arya Tandon· Nov 15, 2024
Useful defaults in documentation-engineer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Anika Abbas· Nov 7, 2024
documentation-engineer has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Anika Bansal· Oct 26, 2024
Solid pick for teams standardizing on skills: documentation-engineer is focused, and the summary matches what you get after install.
- ★★★★★Shikha Mishra· Oct 10, 2024
Useful defaults in documentation-engineer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 56