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",…
Install / Use
npx skills add tzachbon/smart-ralph --skill spec-workflowInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of spec-workflow
spec-workflow scores 87/100 on our quality scale, 1715th of 2,769 Automation skills we index.
Its SKILL.md is 4.5 KB long, well organised into 16 sections with 6 code examples: a solid amount of guidance for an agent.
It has 550 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so spec-workflow is actively maintained.
- Our last check on 2026-10-11 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
spec-workflow compared with similar skills
All 4 of these similar skills score higher than spec-workflow; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| spec-workflow (this skill)by tzachbon | 87 | 550 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.8k | 9d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.8k | 10d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 82.0k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 40.0k | 8d ago | CLAUDE.md |
Frequently asked questions
- How do I install spec-workflow?
- Run
npx skills add tzachbon/smart-ralph --skill spec-workflow. The install tabs above show the steps for each supported agent. - Which AI agents does spec-workflow work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is spec-workflow safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is spec-workflow still maintained?
- The repository was last updated about 2 months ago, so spec-workflow is actively maintained.
Skill content
View source on GitHubname: spec-workflow description: 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. version: 0.2.0
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
Related Skills
taste-skill
117.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.8kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
82.0k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
40.0kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
