Not in the top 1,000 by GitHub stars
echoVic/spec-flow
A Claude Code skill for structured, spec-driven development with phase-by-phase workflow and living documentation
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
3ae2516ec921 → 3ae2516ec921
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 3ae2516ec921
No earlier version was observed for comparison.
Heat
0.3- Star growth, last 7 daysNot available
- Star growth, last 24 hoursNot available
- Rank movement, last 7 daysNot available
- Commits, last 30 daysNot available
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekNot available
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
30-day change not yet available: not enough history.
Individual skills in this repository
How it works
spec-flow
When your agent uses it
Spec-driven development workflow. Interactive phase-by-phase confirmation from proposal to implementation. Trigger: 'spec-flow', 'spec mode', 'need a plan', 'structured development', 'write a spec', 'feature spec', 'technical spec', '需求文档', '技术方案', '任务拆解', '规格驱动', '写个方案', '做个规划', '结构化开发', 'plan this feature', 'break this down', 'design doc'. Creates .spec-flow/ directory with proposal, requirements, design, and tasks.
What it loads into context
Frontmatter
136 tokensAlways available to the agent
SKILL.md
1,585 tokensWhen the skill is activated
Reference documents
10,885 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Core Principles
- Parameters
- Language Rule
- Interaction Rules
- Five-Phase Workflow
- Directory Structure
- Steering Documents (Optional)
- Phase Transitions
- Compatibility
Scripts executed separately
scripts/execute-task.shscripts/init-spec-flow.shscripts/validate-spec-flow.py
Files
.gitignoreasset359 bytesCONTRIBUTING.mddoc4,987 bytesLICENSEasset1,064 bytesREADME.mddoc4,694 bytesSKILL.mdcore5,755 bytesreferences/ears-format.mddoc6,610 bytesreferences/examples/feature-example.mddoc8,782 bytesreferences/execution-modes.mddoc2,088 bytesreferences/interaction-rules.mddoc1,354 bytesreferences/task-decomposition.mddoc7,440 bytesreferences/workflow.mddoc7,360 bytesscripts/execute-task.shruns9,514 bytesscripts/init-spec-flow.shruns5,324 bytesscripts/validate-spec-flow.pyruns10,844 bytestemplates/design.md.templateasset4,467 bytestemplates/proposal.md.templateasset1,911 bytestemplates/requirements.md.templateasset3,537 bytestemplates/steering/constitution.md.templateasset2,297 bytestemplates/steering/product.md.templateasset2,203 bytestemplates/steering/structure.md.templateasset4,227 bytestemplates/steering/tech.md.templateasset3,294 bytestemplates/tasks.md.templateasset5,012 bytes
Read SKILL.md
# Spec-Flow - Structured Development Workflow
Structured workflow for complex feature development. Creates living documentation that guides implementation and serves as team reference.
## Core Principles
1. **One phase at a time** — NEVER generate documents for subsequent phases in advance
2. **Mandatory confirmation** — After each phase, STOP and wait for user confirmation
3. **User-driven progression** — Only proceed when user says "continue"/"ok"/"next"/"继续"/"好"
## Parameters
| 参数 | 说明 |
|------|------|View the complete source on GitHubSkills included
- spec-flow
Repository facts
- License
- MIT
- Created
- Jan 5, 2026
- Last pushed
- Feb 16, 2026
- Forks
- 7
- Open issues
- 0
- Project activity
- Slowing
Before you install
Network or broad shellAutomated signals, not a guarantee
Checked Nov 5, 2026
- No broad tool permissions
- No dangerous shell commands
- 11 network referencesin 3 files: README.md:3 CONTRIBUTING.md:19 scripts/validate-spec-flow.py:269
- No hidden or obfuscated text
- No instruction overrides
- 3 executable scriptsin 3 files: scripts/execute-task.sh:1 scripts/init-spec-flow.sh:1 scripts/validate-spec-flow.py:1
- No access to secrets
- No requests to vote in Hot
Show all 14 signals by file
CONTRIBUTING.md
README.md
- Network accessline 3
[](https://opensource.org/licenses/MIT) - Network accessline 21
# Claude Code cd ~/.claude/skills && git clone https://github.com/echoVic/spec-flow.git - Network accessline 22
cd ~/.claude/skills && git clone https://github.com/echoVic/spec-flow.git - Network accessline 24
# OpenClaw cd ~/.openclaw/workspace/skills && git clone https://github.com/echoVic/spec-flow.git - Network accessline 25
cd ~/.openclaw/workspace/skills && git clone https://github.com/echoVic/spec-flow.git - Network accessline 27
# Blade cd ~/.blade/skills && git clone https://github.com/echoVic/spec-flow.git - Network accessline 28
cd ~/.blade/skills && git clone https://github.com/echoVic/spec-flow.git
scripts/execute-task.sh
- Executable scriptline 1
#!/bin/bash
scripts/init-spec-flow.sh
- Executable scriptline 1
#!/bin/bash
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Signal confidence: 14 facts
- Network access in code of documentationCONTRIBUTING.md:19Low confidence
- Network access in code of documentationCONTRIBUTING.md:20Low confidence
- Network access in prose of documentationREADME.md:3Low confidence
- Network access in code of documentationREADME.md:21Low confidence
- Network access in code of documentationREADME.md:22Low confidence
- Network access in code of documentationREADME.md:24Low confidence
- Network access in code of documentationREADME.md:25Low confidence
- Network access in code of documentationREADME.md:27Low confidence
- Network access in code of documentationREADME.md:28Low confidence
- Executable script in code of a file that runsscripts/execute-task.sh:1High confidence
- Executable script in code of a file that runsscripts/init-spec-flow.sh:1High confidence
- Executable script in code of a file that runsscripts/validate-spec-flow.py:1High confidence
- Network access in code of a file that runsscripts/validate-spec-flow.py:269High confidence
- Network access in code of a file that runsscripts/validate-spec-flow.py:271High confidence
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Native | Frontmatter field argument-hint in SKILL.md | .claude/skills/<skill-name>/ |
| Codex | Compatible | Standard SKILL.md SKILL.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.