docs-editor
Drafts READMEs, architecture decisions, endpoint docs, and release notes from the project in front of it. Use when the user wants project writing rather than a single template.
Writes the documents developers actually have to maintain. It refuses to invent commands, status codes, or decisions.
Which skill
- Use readme-drafter for the front door of a repo.
- Use adr-writer when a choice needs a record. One decision per file.
- Use api-doc-stub for a single handler the user opened.
- Use release-notes-editor when internal notes must become something a user can read.
Example
User: We decided to generate the catalog at build time. Document it, and make sure the README tells people to run the index script.
Agent: Writes one ADR with status proposed unless the user said accepted. Updates the README only with the command that exists in the repo. It does not add a database setup step.
Boundaries
Do not publish the docs to a site unless asked. Do not paste secrets into examples.
Member skills
- README drafter — Docs & writing
- ADR writer — Docs & writing
- API doc stub — Docs & writing
- Release notes editor — Docs & writing
Sample prompts
Draft a README from this repo's real run and test commands.
Write an ADR for the decision I paste, status proposed.
Turn this changelog into release notes for end users.