Document
A plugin system for Claude Code that adds skills, agents, guidelines, repo-aware configurations, and MCP integrations to supercharge your development workflow.
npx -y skills add sujeet-pro/agents-devkit --skill documentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Draft a technical document from an intent or a source. Triggers on "write the runbook / ADR / RCA / PR description / commit message / changelog / diagram / README / migration guide / API reference / experiment report / incident summary / onboarding doc / design doc". Markdown-first: produces a draft in a local file and NEVER publishes (no Confluence / Jira / Slack / GitHub posting — that is a separate concern). Reader-first voice: leads with the reader's question, cites every non-trivial claim to a repo path or quoted source, caps external quotes at 15 words, cuts filler. Audience-tuned (engineer / pm / exec / mixed) — the voice does not mix. GitHub context (PR / issue) is read via the gh CLI.
SKILL.md
3.7 KB, as published. Nobody here has run it
document — draft a technical document (markdown-first)
Turns an intent or a source into a markdown draft engineers actually use. Drafts to a local file. Never publishes. Posting to Confluence / Jira / Slack / GitHub is a separate concern — this skill stops at a clean markdown file and tells you where it is.
The full operating contract lives in this skill folder — read these as you need them:
| Aspect | File |
|---|---|
| How you write (voice, citation rules, anti-patterns) | persona.md |
| The phased process + Workflow orchestration | workflow.md |
| Hard rules + refusals + safety | rules.md |
| Per-artifact contract (lead-with / cap / must-include) | types.md |
Quick start
- Resolve
--typeagainsttypes.md. If the user didn't pass one, infer it from the intent ("write the runbook for…" → runbook) and state the inference in the output. - Gather sources (Phase 0 in
workflow.md). GitHub PR/issue context is theghCLI (gh pr view <url> --json …,gh issue view <url> --json …); repo facts come from Read / Grep / Glob; external links from WebFetch. For a doc that synthesizes multiple systems, fan out thecontext-gathereragent. - Read
persona.mdand adopt the reader-first voice for the chosen--audience(default: engineer). The voice does not mix audiences — pick one. - Draft to
--write-to <path>if given, else a sensible local path (types.mdsuggests one per artifact). Follow the type's lead-with / cap / must-include contract. - Validate (Phase 3): anti-pattern grep, citation check, length cap. Then report the draft path. Nothing is published.
Workflow is the default for multi-source docs
"Always have a workflow." A doc that synthesizes more than one system — an RCA, an ADR weighing alternatives, a migration guide spanning two services — gets the Workflow in workflow.md: fan out context-gatherer + per-section drafting in parallel, stitch, then run a completeness-critic pass that asks "what's missing, what's uncited, what did we assert without evidence?" before the draft survives. A simple, single-source doc (a commit message, a one-screen README section) is drafted inline — say you skipped the Workflow.
Modes
- default — gather, draft, validate, report the local draft path. Nothing is published.
-i— confirm the type, audience, and outline with the user before drafting; walk the draft section-by-section.--deep— use a stronger reasoning profile; auto-select for RCAs, design docs, and anything synthesizing 3+ sources.--write-to <path>— write the draft to a canonical repo path (e.g.docs/adr/0007-x.md) instead of a scratch path. Still a draft; still not published.