Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
Claude Code Spec Workflow
Earlier Claude Code-only slash-command workflow (Requirements -> Design -> Tasks -> Implementation, plus a bug-fix flow), superseded by the same author's MCP server.
Last push 2025-09-07; README notice says development moved to Spec Workflow MCP and this version 'will receive limited updates' (checked 2026-10-25)
In Spec-driven development
Where it stands apart
- Is it actively maintained? dormant, sunsetting, or archived (0% of 19 others)
- How is it mainly sustained? individual with revenue (paid app, tier, ads, or donations) (11% of 18 others)
- Which shared standard or format does it mainly build on? the Kiro spec layout (requirements in EARS, design, tasks files) (11% of 19 others)
- After implementation, what built-in step keeps specs and code aligned? (if several, the first that applies) nothing built in (22% of 18 others)
- Which coding agents does it work with? one to four named third-party agents (11% of 18 others)
What it shares with most of the community
- How is the main thing licensed? permissive open source (MIT/Apache/BSD) (74% of 19 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? yes (79% of 19 others)
- Do you need an account to use it? no account (74% of 19 others)
- Who is it for? developers (100% of 19 others)
- Once code exists, what is the spec? a planning scaffold: code becomes the truth after implementation (53% of 19 others)
- What format are specs written in? markdown from templates or free-form (67% of 18 others)
- Where do specs live? plain files in the project repository (89% of 19 others)
- How is the path from idea to code structured? a fixed sequence of phases (e.g. requirements, design, tasks) (53% of 19 others)
- Does a human approve the spec or plan before code is written? yes, the workflow waits for approval (50% of 18 others)
- By default, once a plan is approved, how is implementation run? the human drives it, phase by phase or task by task (50% of 18 others)
- What does it offer teams beyond sharing files in git? (if both, pick the paid product) nothing beyond git (50% of 18 others)
Nearest neighbors
- PRP (Product Requirement Prompts) 76% of 17 shared answers match
- Conductor (Google) 71% of 17 shared answers match
- Spec Workflow MCP 71% of 17 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | stands apart dormant, sunsetting, or archived | source 2026-10-25 |
| How is the main thing licensed? | permissive open source (MIT/Apache/BSD) MIT | source 2026-10-25 |
| How is it mainly sustained? | stands apart individual with revenue (paid app, tier, ads, or donations) Individual author; README carries a Buy Me A Coffee donation button. | source 2026-10-26 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | yes | source 2026-10-25 |
| Do you need an account to use it? | no account Local slash commands and dashboard; needs Claude Code (own login), none with the maker. | source 2026-10-26 |
| Who is it for? | developers | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | stands apart the Kiro spec layout (requirements in EARS, design, tasks files) Requirements -> Design -> Tasks layout via Claude Code slash commands. | source 2026-10-26 |
| Once code exists, what is the spec? | a planning scaffold: code becomes the truth after implementation | source 2026-10-25 |
| After implementation, what built-in step keeps specs and code aligned? (if several, the first that applies) | stands apart nothing built in | source 2026-10-25 |
| What format are specs written in? | markdown from templates or free-form | source 2026-10-25 |
| Where do specs live? | plain files in the project repository | source 2026-10-25 |
| Which coding agents does it work with? | stands apart one to four named third-party agents Claude Code only. | source 2026-10-25 |
| What form does it mainly ship in? | prompts, skills, or slash commands installed into an agent (even if a CLI installs them) | source 2026-10-25 |
| How is the path from idea to code structured? | a fixed sequence of phases (e.g. requirements, design, tasks) Requirements -> Design -> Tasks -> Implementation. | source 2026-10-25 |
| Does a human approve the spec or plan before code is written? | yes, the workflow waits for approval Phase-by-phase approval (not re-verified in current README). | source 2026-10-25 |
| By default, once a plan is approved, how is implementation run? | the human drives it, phase by phase or task by task | source 2026-10-25 |
| What does it offer teams beyond sharing files in git? (if both, pick the paid product) | nothing beyond git | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/Pimzino/claude-code-spec-workflow · read 2026-10-25
RSS for this project · Its own release feed
Are you a maintainer? Claiming and correcting projects is coming soon.