npx claudepluginhub mayurpise/draft --plugin draftThis skill uses the workspace's default tool permissions.
Draft is a methodology for structured software development: **Context → Spec & Plan → Implement**
Displays Correctless workflow pipeline by intensity level, lists all 26 commands with gating annotations, and shows project setup status. Quick /chelp reference.
Orchestrates git-only agile workflows with checkpoint-based flow control for task cycles, daily standups, sprints, and retrospectives. Use for 'run workflow', 'what's next', or guided development steps.
Guides creation of Claude Code slash commands using YAML frontmatter, XML tags like <objective> and <process>, dynamic context, and argument handling.
Share bugs, ideas, or general feedback.
Draft is a methodology for structured software development: Context → Spec & Plan → Implement
/draft:implement before a track has an approved spec and plandraft/tracks.md for existing active tracks before creating new onesRead context first. Follow the workflow.
init → new-track → implement → review
↑ |
└───────────┘ (auto-invoked at phase boundaries)
| Command | Purpose | Auto-Invokes |
|---|---|---|
/draft:init | Initialize project context | -- |
/draft:new-track | Create feature/bug track with spec and plan | debug (bug tracks), tech-debt (refactor tracks) |
/draft:implement | Execute tasks from plan with TDD | review (phase boundaries), testing-strategy (TDD context) |
/draft:review | Three-stage code review | coverage (if TDD enabled), bughunt (with --full) |
Setup & Navigation:
/draft | This overview | /draft:index | Monorepo service aggregation |
|---|
Planning & Architecture:
| Command | Purpose |
|---|---|
/draft:decompose | Module decomposition with dependency mapping |
/draft:adr | Architecture Decision Records (record, evaluate, design) |
/draft:tech-debt | Technical debt analysis across 6 dimensions |
/draft:change | Handle mid-track requirement changes |
Code Quality:
| Command | Purpose |
|---|---|
/draft:quick-review | Lightweight 4-dimension code review (~2 min) |
/draft:bughunt | Exhaustive 14-dimension bug hunt |
/draft:deep-review | Module lifecycle audit (ACID compliance) |
/draft:coverage | Code coverage report (target 95%+) |
/draft:testing-strategy | Test plan design with coverage targets |
/draft:learn | Discover coding patterns and update guardrails |
Debugging:
| Command | Purpose |
|---|---|
/draft:debug | Structured debugging (reproduce → isolate → diagnose → fix) |
Operations:
| Command | Purpose |
|---|---|
/draft:deploy-checklist | Pre-deployment verification with rollback triggers |
/draft:incident-response | Incident lifecycle (triage → communicate → mitigate → postmortem) |
/draft:standup | Git activity standup summary (read-only) |
/draft:status | Show progress overview |
/draft:revert | Git-aware rollback |
Authoring:
| Command | Purpose |
|---|---|
/draft:documentation | Technical docs (readme, runbook, api, onboarding) |
Integration:
| Command | Purpose |
|---|---|
/draft:jira-preview | Generate Jira export for review |
/draft:jira-create | Push issues to Jira via MCP |
/draft:init to initialize your project/draft:new-track "your feature description"/draft:implement to execute tasks/draft:statusEvery feature follows this lifecycle:
Auto-invocations: The primary workflow has built-in quality gates — /draft:implement auto-invokes /draft:review at phase boundaries, and /draft:review auto-invokes /draft:coverage when TDD is enabled.
Four commands form an audit spectrum from quick to narrow to broad to deep:
| Command | Scope | Time | Question It Answers | Output |
|---|---|---|---|---|
/draft:quick-review | File/PR/diff | ~2 min | "Any obvious issues in this change?" | 4-dimension findings with severity |
/draft:review | Change-scoped (track, diff, commits) | ~10 min | "Does this change meet spec and quality gates?" | Three-stage review report with verdict |
/draft:bughunt | Codebase-scoped (repo, paths, track) | ~20 min | "What bugs exist in this code?" | Severity-ranked bug report + regression tests |
/draft:deep-review | Module-scoped (single service/component) | ~30 min | "Is this module production-ready?" | ACID compliance audit + implementation spec |
/draft:quick-review — fast 4-dimension review, no track context needed/draft:review — validates against spec, checks quality gates/draft:bughunt — 14-dimension sweep with verification protocol/draft:deep-review — ACID compliance, resilience, observability audit/draft:review full (includes bughunt), then /draft:deep-review for critical modulesSome AI tools provide built-in bug hunt agents (e.g., Claude Code's bughunt agent). These are complementary to /draft:bughunt — the built-in agents offer fast parallel sweeps with auto-fix, while Draft's bughunt adds context-aware analysis using your architecture, tech-stack, and product context for better false-positive elimination. For maximum coverage, run both.
When draft/ exists, these files guide development:
draft/architecture.md - Source of truth: comprehensive human-readable engineering referencedraft/.ai-context.md - Derived from architecture.md: token-optimized AI context (200-400 lines)draft/product.md - Product vision and goalsdraft/tech-stack.md - Technical constraintsdraft/workflow.md - TDD and commit preferencesdraft/guardrails.md - Hard guardrails, learned conventions, learned anti-patternsdraft/tracks.md - Active work itemsUsed throughout plan.md files:
| Marker | Meaning |
|---|---|
[ ] | Pending |
[~] | In Progress |
[x] | Completed |
[!] | Blocked |
You can also use natural language:
| Say this... | Runs this |
|---|---|
| "set up the project" | /draft:init |
| "index services", "aggregate context" | /draft:index |
| "new feature", "add X" | /draft:new-track |
| "start implementing" | /draft:implement |
| "what's the status" | /draft:status |
| "undo", "revert" | /draft:revert |
| "break into modules" | /draft:decompose |
| "check coverage" | /draft:coverage |
| "deep review", "module audit", "production audit" | /draft:deep-review |
| "hunt bugs", "find bugs" | /draft:bughunt |
| "review code", "review track", "check quality" | /draft:review |
| "document decision", "create ADR" | /draft:adr |
| "requirements changed", "scope changed", "update the spec" | /draft:change |
| "learn patterns", "update guardrails", "discover conventions" | /draft:learn |
| "preview jira", "export to jira" | /draft:jira-preview |
| "create jira", "push to jira" | /draft:jira-create |
| "quick review", "fast review" | /draft:quick-review |
| "debug this", "investigate bug" | /draft:debug |
| "deploy checklist", "pre-deploy" | /draft:deploy-checklist |
| "test strategy", "testing plan" | /draft:testing-strategy |
| "tech debt", "catalog debt" | /draft:tech-debt |
| "standup", "what did I do" | /draft:standup |
| "incident", "outage", "post-mortem" | /draft:incident-response |
| "write docs", "documentation", "runbook" | /draft:documentation |
/draft (this command) for overview/draft:status to see current statedraft/tracks/<track_id>/spec.md for requirementsdraft/tracks/<track_id>/plan.md for task details