spec-workflow

# 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 ``` Each phase produces a markdown artifact in `./specs/<name>/`. Normal mode pauses for approval between phases. Quick mode runs all phases then auto-starts execution. ### 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 | ## Epic Flow (Multi-Spec) For features too large for a single spec, use epic triage ...