Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tzachbon/spec-workflow
This skill should be used when the user asks to "build a feature", "create a spec", "start spec-driven development", "run research phase", "generate requirements", "create design", "plan tasks", "implement spec", "check spec status", "triage a feature", "create an epic", "decompose a large feature", or needs guidance on spec-driven development workflow, phase ordering, or epic orchestration.
Passed 16 of 21 test cases with the skill, and 15 of 21 without it.
and 1 more in the full report
3 fixed14 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
Can you list the exact sequential phase progression for a single specification flow from initiation through to execution?
| Checked | Without skill | With skill |
|---|---|---|
| The response lists research before requirements. | Missed | Passed |
| The response lists requirements before design. | Passed | Passed |
| The response lists design before tasks. | Passed | Passed |
| The response lists tasks before implement. | Passed | Passed |
The instructions your model reads when the skill loads.
Spec-driven development transforms feature requests into structured specs through sequential phases, then executes them task-by-task.
| Situation | Command |
|---|---|
| New feature, want guidance | /ralph-specum:start <name> <goal> |
| New feature, skip interviews | /ralph-specum:start <name> <goal> --quick |
| Large feature needing decomposition | /ralph-specum:triage <goal> |
| Resume existing spec | /ralph-specum:start (auto-detects) |
| Jump to specific phase | /ralph-specum:<phase> |
start/new -> research -> requirements -> design -> tasks -> implement
^
optional prototype overlay, then return
Each phase produces a markdown artifact under the resolved <basePath>/. Normal mode pauses for approval between phases. Quick mode runs all phases then auto-starts execution.
Prototype is an optional overlay, not a main phase. The main phase remains research, requirements, design, tasks, or execution; live prototype work is stored in activePrototypes. Resolve the configured spec root and basePath before any overlay operation. Follow references/phase-transitions.md when suggesting, starting, resuming, cancelling, or consuming prototype evidence.
| Command | Agent | Output | Purpose |
|---|---|---|---|
/ralph-specum:research | research-analyst | research.md | Explore feasibility, patterns, context |
/ralph-specum:requirements | product-manager | requirements.md | User stories, acceptance criteria |
/ralph-specum:design | architect-reviewer | design.md | Architecture, components, interfaces |
/ralph-specum:tasks | task-planner | tasks.md | POC-first task breakdown |
/ralph-specum:implement | spec-executor | commits | Autonomous task-by-task execution |
/ralph-specum:prototype | prototype-builder | prototypes/<id>.md | Test one falsifiable design question in isolation |
Normal mode may suggest prototype after research or requirements, and the user owns capture, verdict, handoff, and deletion decisions. Direct invocation is available from any main phase. Quick mode runs at most one agent-owned request after requirements, takes over the oldest design blocker when one exists, asks no decision questions, and always continues to design.
test cases passed, vs 15 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.