spec-to-plan
Skill1 starsChanged 6 months agoMITView on GitHub
Convert ISO spec requirements (StR, FR, NFR) into a TDD-based project plan with dependency analysis, parallel execution tracks, quality gates, and task decomposition. Creates /plan/plan.md and /plan/tasks/.
5 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- rubenmarcus/agent-skillstheir own version, first seen Nov 1, 2026
- agent-ix/quoinedited, first seen Jun 25, 2026
- michaelvl/agent-skillstheir own version, first seen May 17, 2026
- kambleakash0/agent-skillstheir own version, first seen Apr 6, 2026
- eugenepyvovarov/mcpbundler-agent-skills-marketplacetheir own version, first seen Feb 15, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- agent-ix/quoin★ 2026% same
Wrote their own version · 4
- eugenepyvovarov/mcpbundler-agent-skills-marketplace★ 12same name
- kambleakash0/agent-skills★ 10same name
- rubenmarcus/agent-skills★ 2same name
- michaelvl/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- spec-app-reviewSkill
- spec-blueprintSkill
- spec-dependency-analysisSkill
- spec-evidence-analysisSkill
- spec-failure-domain-analysisSkill
- specifySkill
- spec-integrity-analysisSkill
- spec-matrixSkill
- spec-object-reviewSkill
- spec-reviewSkill
- spec-risk-complexity-analysisSkill
- spec-scope-boundary-analysisSkill
- spec-security-analysisSkill
- spec-us-to-frSkill
- spec-write-frSkill
- spec-write-itSkill
- spec-write-nfrSkill
- spec-write-strSkill
- spec-write-usSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill when:
- Distinctive: line 23
All requirements are atomic and testable.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Spec to Plan
This skill provides a structured workflow for converting ISO/IEC/IEEE 29148 compliant specifications into an executable, dependency-aware project plan with parallel execution tracks and quality gates.
Purpose
Use this skill when:
- You are starting a new implementation task based on an existing Spec.
- You need to generate a Test Plan before writing code (TDD).
- You want to ensure full traceability from Requirements (StR/FR/NFR) to Tests.
- You need to identify what can be parallelized vs what must be serial.
- You want quality gates to catch fundamental problems before downstream work is wasted.
Pre-conditions (Readiness Gate)
Task generation MAY begin only when ALL of the following are true:
- All requirements are atomic and testable.
- Ownership is assigned (see
spec-scope-boundary-analysis). - Dependencies are known (see
spec-dependency-analysis). - Risks are classified (see
spec-risk-complexity-analysis). - Verification strategy is defined (see
spec-evidence-analysis). - Failure-domain analysis is complete (see
spec-failure-domain-analysis).
Failure to meet these conditions WILL result in unstable tasking. If any condition is unmet, stop and complete the corresponding analysis skill first.
Steps
All steps required!
- Analysis: Analyze the spec structure and map dependencies.
- Test Plan: Generate the list of required tests.
- Execution Plan: Derive dependency graph, critical path, parallel tracks, quality gates, and task decomposition.
Output
This skill produces or updates:
<project_root>/plan/plan.md: The central living document containing requirements summary, dependency graph, execution tracks, quality gates, and test plan.<project_root>/plan/tasks/: Individual task files for distribution and tracking, with status, dependencies, and subtask breakdowns.<project_root>/plan/tasks/README.md: Task index showing completed work, active tracks, and coordination rules.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.