From deckrd
Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
How this skill is triggered — by the user, by Claude, or both
Slash command
/deckrd:deckrdThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- markdownlint-disable line-length -->
assets/inits/deckrd-rules/deckrd-rule-commit-linkage.mdassets/inits/deckrd-rules/deckrd-rule-document-naming.mdassets/inits/deckrd-rules/deckrd-rule-file-structure.mdassets/inits/deckrd-rules/deckrd-rule-id-system.mdassets/inits/deckrd-rules/deckrd-rule-traceability.mdassets/inits/docs/README.mdassets/prompts/decision-record.prompt.mdassets/prompts/implementation.prompt.mdassets/prompts/requirements.prompt.mdassets/prompts/rev.prompt.mdassets/prompts/review-explore.prompt.mdassets/prompts/review-fix.prompt.mdassets/prompts/review-harden.prompt.mdassets/prompts/review.prompt.mdassets/prompts/specifications.prompt.mdassets/prompts/tasks.prompt.mdassets/templates/decision-record.template.mdassets/templates/implementation-checklist.template.mdassets/templates/implementation.template.mdassets/templates/requirements.template.mdGoals → Requirements → Specifications → Implementation → Tasks
Before every command, YOU MUST output:
"I am executing /deckrd [COMMAND] for module [MODULE_NAME]."
No announcement = violation. Restart with announcement.
.local/deckrd/session.json — confirm active module and current stepReference selection:
| Current State | Next Command | Reference |
|---|---|---|
| (none) | init | commands/init.md |
| init completed | module | commands/module.md |
| module completed | req | commands/req.md |
| req completed | spec | commands/spec.md |
| spec completed | impl | commands/impl.md |
| impl completed | tasks | commands/tasks.md |
| any | review | commands/review.md |
| init completed | rev | commands/rev.md |
Gate Rule: each command requires the previous command's document. No skipping.
projectis project-scoped and can run any time. See commands/project.md. Full command list: commands/index.md Workflow overview: workflow.md Session management: session.md
New feature from goals:
"I want to add a retry mechanism to the HTTP client." →
/deckrd init my-project/http-retry→req→spec→impl→tasks
Existing code, no docs:
"This module has no documentation. Reverse-engineer it." →
/deckrd rev --to req→spec→impl→tasks
Small bug fix:
Session not found
Cause: init has not been run, or wrong directory.
Solution: Run /deckrd init <project> <project-type> first.
Command out of order
Cause: Trying to run spec before req, etc.
Solution: Check /deckrd status to see the current step, then run the correct next command.
Gate Rule violation
Cause: Required document from previous step is missing.
Solution: Complete the missing step before proceeding. Use /deckrd status to confirm.
npx claudepluginhub aglabo/deckrd --plugin deckrdOrchestrates spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates. Activates for structured feature planning or 'use spec-driven'.
Guides feature development from idea to implementation: creates EARS requirements, design documents, and task lists in .kiro/specs/.
Creates detailed implementation plans with bite-sized tasks, exact file paths, and TDD steps. Use when you have a spec before coding.