From ralph-specum
Guides spec-driven development through phases: research, requirements, design, tasks, autonomous task-by-task implementation. Decomposes large epics into ordered specs with progress tracking.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ralph-specum:spec-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Spec-driven development transforms feature requests into structured specs through sequential phases, then executes them task-by-task.
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
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.
| 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 |
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 specFile 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
| 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 |
/ralph-specum:start my-feature "Build X" --quick
# Runs all phases automatically, starts execution
/ralph-specum:start my-feature "Build X"
# Interactive interviews at each phase
# Review and approve each artifact
/ralph-specum:implement
/ralph-specum:triage "Build entire auth system"
# Decomposes into: auth-core, auth-oauth, auth-rbac
/ralph-specum:start # Picks next unblocked spec
references/phase-transitions.md -- Detailed phase flow, state transitions, quick mode behavior, phase skippingnpx claudepluginhub tzachbon/smart-ralph --plugin ralph-specumOrchestrates spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates. Activates for structured feature planning or 'use spec-driven'.
Creates structured specifications before coding. Use when starting new projects, features, or significant changes with ambiguous requirements.
Creates structured specifications before coding to clarify requirements and reduce ambiguity. Useful when starting new projects, features, or significant changes.