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)
From dev-spec-kit
Run the dev-spec-kit spec-driven loop on a request — route, spec (EARS), evidence-bound tasks, TDD, proofs, graph, approval, PR.
How this command is triggered — by the user, by Claude, or both
Slash command
/dev-spec-kit:dev-spec-kitThe summary Claude sees in its command listing — used to decide when to auto-load this command
Use the dev-spec-kit-workflow skill on the following request. Start with `dev-spec-kit route` and report the chosen mode + reason before doing anything else. Honor every hard rule in the skill — especially: no done without green proofs, quick mode still writes a test, and stop at the human gates. Request: $ARGUMENTS
Use the dev-spec-kit-workflow skill on the following request. Start with dev-spec-kit route and report the chosen
mode + reason before doing anything else. Honor every hard rule in the skill — especially: no done
without green proofs, quick mode still writes a test, and stop at the human gates.
Request: $ARGUMENTS
npx claudepluginhub pratiyush/dev-spec-kit