spec-plan
Skill5 starsChanged 7 days agoLicence not identifiedView on GitHub
Turn a SPEC.md (plus its SPEC_REVIEW_REPORT.md when one exists) into an IMPLEMENTATION_PLAN.md — the verdict, the evidence from any prior builds, the target shape, the dependency-wave order with a gate per wave, the LOC budget, the structural rules that make the observed failures impossible, and the single fork decision — and, when the waves are big enough to execute one at a time, into per-wave DETAILED_IMPLEMENTATION_PLAN_WN.md documents. Use when asked to "plan the implementation", "make an implementation plan for SPEC.md", "how should we build this spec", "break this spec into waves", or between spec-review (READY) and spec-build. Pairs with spec-writing (authors the spec), spec-review (audits it), and spec-build (implements it, test-first—this plan is what that skill executes).
12 other projects use a version of this.
Adopted by
Most recently taken up by
- Buddhilive/buddhi-clitheir own version, first seen Nov 1, 2026
- renanlido/tia-harnesstheir own version, first seen Nov 1, 2026
- xfstudio/skillstheir own version, first seen Oct 13, 2026
- pierre-lecocq/claude-skillstheir own version, first seen Oct 11, 2026
- martinffx/ateliertheir own version, first seen Oct 9, 2026
- cassianodiniz/casstheir own version, first seen Oct 3, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- martinffx/atelier★ 51same name
- JunhuaLiu1/awesome-skills★ 14same name
- renanlido/tia-harness★ 12same name
- xfstudio/skills★ 9same name
- cassianodiniz/cass★ 4same name
- cassianodiniz/Titan★ 4same name
- p-larsson/spec-orbit★ 2same name
- Buddhilive/buddhi-cli★ 1same name
- h3y6e/spec-skills★ 0same name
- MarcosCamara01/sddguard★ 0same name
2 more not listed
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 repository6 other files it gives its agents.
- spec-buildSkill
- spec-modelSkill
- spec-proofSkill
- spec-proposalSkill
- spec-reviewSkill
- spec-writingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 8 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 10 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.
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.