Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
How this command is triggered — by the user, by Claude, or both
Slash command
/story-driven:startThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Story-driven Development Ensures code changes deliver user value through structured workflow. ## Workflow **Skills** (main context) + **Subagents** (isolated context): 1. **Define** (`defining-stories` skill) - User story, criteria, story log 2. **Implement** (`implementing-stories` skill) - Red (failing test), Green (pass), skip refactor 3. **Refactor** (`refactor` subagent, fresh context) - Duplication removal, naming, loose coupling, high cohesion, single responsibility 4. **Verify** (`verify` subagent, fresh context) - Acceptance tests via acceptance-tester, full su...
Ensures code changes deliver user value through structured workflow.
Skills (main context) + Subagents (isolated context):
Define (defining-stories skill)
Implement (implementing-stories skill)
Refactor (refactor subagent, fresh context)
Verify (verify subagent, fresh context)
Code Review (preparing-review skill)
Acceptance Test (acceptance-testing skill, optional)
No arguments: Ask which phase (refer to Workflow for skill/subagent names)
With arguments: Invoke skill/subagent based on $ARGUMENTS intent
Skills share main context. Subagents (Refactor, Verify) provide fresh, isolated perspective.
npx claudepluginhub joshuarweaver/cascade-code-general-misc-4 --plugin kecbigmt-cc-plugins/craft-story-implementImplements a fully designed story by delegating each chunk to a subagent, running inline validation, and handling backlog assignment and cycle creation.
/atddGuides through ATDD workflow for defining and implementing user stories via five phases: workshop, distillation, development, demo, done.
/buildGuides feature implementation through structured phases: understand, design, build, verify, and test with approval gates at each step.
/spec-kitRuns a spec-driven development pipeline with four phases (specify, plan, tasks, implement) and explicit human checkpoints. Turns a feature description into verified code.
/workflowGuides developers through a structured pipeline (design→spec→plan→implement→test→verify→commit) with configurable step skipping and start points. Also detects greenfield vs legacy codebase scenarios.
/coding-flowStructures coding tasks (features, fixes, refactors, tests) into a sequential workflow with reviewer gates, subagent delegation, and skill-driven execution scaled by request size.