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.
Phase Commands
| 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.
Epic Flow (Multi-Spec)
For features too large for a single spec, use epic triage to decompose into dependency-aware specs.
triage -> [spec-1, spec-2, spec-3...] -> implement each in order
Entry points:
/ralph-specum:triage <goal> -- create or resume an epic/ralph-specum:start -- detects active epics, suggests next unblocked spec
File structure:
specs/
_epics/<epic-name>/
epic.md # Triage output (vision, specs, dependency graph)
research.md # Exploration + validation research
.epic-state.json # Progress tracking across specs
.progress.md # Learnings and decisions
Management Commands
| Command | Purpose |
|---|
/ralph-specum:status | Show all specs and progress |
/ralph-specum:switch <name> | Change active spec |
/ralph-specum:cancel | Cancel active execution |
/ralph-specum:refactor | Update spec files after execution |
Common Workflows
Quick workflow
/ralph-specum:start my-feature "Build X" --quick
# Runs all phases automatically, starts execution
# May run one unattended prototype request after requirements
Guided development
/ralph-specum:start my-feature "Build X"
# Fact-first grilling at each phase
# Review and approve each artifact
/ralph-specum:implement
Large feature
/ralph-specum:triage "Build entire auth system"
# Decomposes into: auth-core, auth-oauth, auth-rbac
/ralph-specum:start # Picks next unblocked spec
References
references/phase-transitions.md -- Read for phase flow, prototype overlay entry and return, quick ownership, recovery, or phase skipping