Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From draft
Routes documentation authoring requests to the appropriate specialist. Generates and updates README, API docs, runbooks, and onboarding guides.
npx claudepluginhub mayurpise/draft --plugin draftHow this skill is triggered — by the user, by Claude, or both
Slash command
/draft:docsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
`/draft:docs` provides a single namespace for all documentation generation and maintenance tasks.
Generates and maintains technical documentation in readme, runbook, API, and onboarding modes using structured writing principles.
Writes clear technical documentation: READMEs, API references, runbooks, architecture docs, and onboarding guides for developers and ops teams.
Generates documentation from code including API references, developer guides, READMEs, and architecture overviews. Matches existing styles and avoids overwriting in brownfield codebases.
Share bugs, ideas, or general feedback.
/draft:docs provides a single namespace for all documentation generation and maintenance tasks.
Currently focused on the documentation specialist. Future expansion may include additional authoring helpers under the same router.
| User Intent Keywords | Dispatches To | Purpose |
|---|---|---|
| write docs, documentation, readme, runbook, api docs, onboarding guide, generate docs | /draft:documentation | Technical documentation authoring (readme, runbook, api, onboarding) |
User: "write a README for the new service"
→ dispatches to /draft:documentation readme
User: "generate an API reference and runbook for the billing module"
→ dispatches to /draft:documentation api runbook
User: "create onboarding guide for new engineers"
→ dispatches to /draft:documentation onboarding
The documentation command reads heavily from draft/architecture.md, draft/.ai-context.md, draft/product.md, and draft/tech-stack.md (plus graph artifacts when present).
Prefer /draft:docs going forward for all authoring requests. The legacy direct form remains for compatibility (see migration guidance).