Skill

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.

From deckrd
Install
1
Run in your terminal
$
npx claudepluginhub aglabo/deckrd --plugin deckrd
Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets
View in Repository
assets/inits/deckrd-rules/deckrd-rule-commit-linkage.md
assets/inits/deckrd-rules/deckrd-rule-document-naming.md
assets/inits/deckrd-rules/deckrd-rule-file-structure.md
assets/inits/deckrd-rules/deckrd-rule-id-system.md
assets/inits/deckrd-rules/deckrd-rule-traceability.md
assets/inits/docs/README.md
assets/prompts/decision-record.prompt.md
assets/prompts/implementation.prompt.md
assets/prompts/requirements.prompt.md
assets/prompts/rev.prompt.md
assets/prompts/review-explore.prompt.md
assets/prompts/review-fix.prompt.md
assets/prompts/review-harden.prompt.md
assets/prompts/review.prompt.md
assets/prompts/specifications.prompt.md
assets/prompts/tasks.prompt.md
assets/templates/decision-record.template.md
assets/templates/implementation-checklist.template.md
assets/templates/implementation.template.md
assets/templates/requirements.template.md
Skill Content
<!-- markdownlint-disable line-length -->

Deckrd

Goals → Requirements → Specifications → Implementation → Tasks

Skill Announcement (REQUIRED)

Before every command, YOU MUST output:

"I am executing /deckrd [COMMAND] for module [MODULE_NAME]."

No announcement = violation. Restart with announcement.

Before Every Command (REQUIRED)

  1. Read .local/deckrd/session.json — confirm active module and current step
  2. Validate command order — if out of order, STOP and report
  3. Load the reference listed below — NEVER proceed without it

Reference selection:

Current StateNext CommandReference
(none)initcommands/init.md
init completedmodulecommands/module.md
module completedreqcommands/req.md
req completedspeccommands/spec.md
spec completedimplcommands/impl.md
impl completedtaskscommands/tasks.md
anyreviewcommands/review.md
init completedrevcommands/rev.md

Gate Rule: each command requires the previous command's document. No skipping.

project is 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

Examples

New feature from goals:

"I want to add a retry mechanism to the HTTP client." → /deckrd init my-project/http-retryreqspecimpltasks

Existing code, no docs:

"This module has no documentation. Reverse-engineer it." → /deckrd rev --to reqspecimpltasks

Small bug fix:

Troubleshooting

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.

Similar Skills
cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.5k
Stats
Parent Repo Stars1
Parent Repo Forks0
Last CommitMar 20, 2026