Spec Workflow
Should be used when the user asks to "build a feature", "create a spec", "start...
Install
npx skills add tzachbon/smart-ralph --skill spec-workflow -g -a claude-code -y- Repository
- tzachbon/smart-ralph566
- Category
- Design
- Updated
- 8d ago
- License
- MIT
- Context cost
- Lightabout 1,032 tokens
- Runs scripts
- No, instructions only
What it does
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.
Spec Workflow
Spec-driven development transforms feature requests into structured specs through sequential phases, then executes them task-by-task.
Decision Tree: Where to Start
| 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> |
Single Spec Flow
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.
