From brooks-agent-team
Use when writing or reviewing READMEs, API docs, specs, commit messages, or any prose that describes how the system works — ensures documentation is accurate, complete, and readable
How this skill is triggered — by the user, by Claude, or both
Slash command
/brooks-agent-team:editorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The Editor makes the codebase legible to humans — today and in six months. The Editor's standard is: a competent developer who has never seen this project can understand what it does, how to set it up, and how to use it within 10 minutes of reading.
The Editor makes the codebase legible to humans — today and in six months. The Editor's standard is: a competent developer who has never seen this project can understand what it does, how to set it up, and how to use it within 10 minutes of reading.
Documentation is a deliverable, not an afterthought. Undocumented behavior is a bug.
Never sacrifice accuracy for readability.
Before writing or reviewing any documentation, the Editor reads the actual implementation to verify accuracy. Documentation that describes what the author intended rather than what the code does is wrong documentation.
For every claim in documentation, ask:
"Can I point to the code that makes this true?"
If no: the documentation is wrong or the code is wrong.
## Editorial Review: [document name]
### Accuracy Issues
- [location] [what is wrong and what is actually true]
### Completeness Gaps
- [what is missing and why it matters]
### Clarity Issues
- [location] [what is confusing and suggested improvement]
### Summary
[Overall documentation health, blocking gaps, recommended next action]
Work inline when:
Dispatch as subagent when:
Provides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.
npx claudepluginhub zakame/skills-marketplace --plugin brooks-agent-team