spec-review
Skill2 starsChanged 4 months agoMITView on GitHub
Validates a spec against the factory's Definition of Ready. Use before the DoR gate or when asked to "review spec".
49 other projects use a version of this.
Adopted by
Most recently taken up by
- philoserf/claude-code-configtheir own version, first seen Nov 15, 2026
- xsyubin/clue-lenstheir own version, first seen Nov 15, 2026
- komluk/scaffoldingtheir own version, first seen Nov 15, 2026
- markkj/skillstheir own version, first seen Nov 11, 2026
- utopia-rise/fmod-gdextensiontheir own version, first seen Nov 9, 2026
- crsmithdev/alephtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use get-pr-reviews, push-everything and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
saffron-healthSkillget-pr-reviews
Get nicely formatted output of the last review comments on a PR. Used internally by other skills.
Also in 3 projects that use this
saffron-healthSkillpush-everything
Stage ALL changes in the repository (not just session changes), commit, and push. Use when you need to commit all pending changes.
Also in 3 projects that use this
NVIDIASkillgenerate-spec
Produce a feature specification covering API changes, backward compatibility, cross-language impact, performance, and a file-level change plan. Use when designing a new feature, planning a significant change, or the user asks to spec something out.
Also in 3 projects that use this
telefrekSkillspec-init
Bootstrap the spec corpus for this project
Also in 3 projects that use this
AWSSkillimplement-spec
Implement the result of /to-spec and /to-tickets in code.
Also in 8 projects that use this
ArvorCoSkillspecify
Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.
Also in 3 projects that use this
- +2 more from saffron-health
Other versions49 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 49
- microsoft/winappCli★ 1.4ksame name
- utopia-rise/godot-kotlin-jvm★ 995same name
- utopia-rise/fmod-gdextension★ 954same name
- cashew-labs/libretto★ 911same name
- saffron-health/libretto★ 911same name
- liza-mas/liza★ 418same name
- HHU3637kr/skills★ 148same name
- saffron-health/opencode-gui★ 59same name
- agent-ix/quoin★ 20same name
- microsoft/WinAppVSCE★ 18same name
39 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 repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- as-is-learnSkill
- as-isSkill
- as-is-syncSkill
- clarifySkill
- consistencySkill
- context-reportSkill
- convergeSkill
- harness-initSkill
- implement-taskSkill
- orchestrateSkill
- repo-addSkill
- repo-mapSkill
- spec-createSkill
- system-mapSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 44 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
EVERY acceptance criterion is verifiable Gherkin (observable and measurable outcome.
- Distinctive: line 22
No secrets, credentials or real customer data in the document.
- Very specific: line 23
No pending [NEEDS CLARIFICATION] markers (resolve with /clarify.
- Distinctive: line 34
Do not edit the spec: report.
“Common” is measured: kept by at least 6 in 10 of the 44 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
Review spec $ARGUMENTS against this Definition of Ready. For each point: PASS / FAIL + evidence (cite the line) or what is missing.
The factory's DoR
- Problem and goal in business language, with no implicit technical solution.
- Stories meet INVEST; none estimated > 8 points without splitting.
- EVERY acceptance criterion is verifiable Gherkin (observable and measurable outcome; no "must be robust/fast/friendly").
- Out of scope explicit and non-empty.
- Edge cases enumerated (nulls, concurrency, third-party errors, permissions).
- Business rules numbered and consistent with knowledge/business-rules.md.
- Dependencies and assumptions listed; blockers marked.
- Regulatory/personal-data requirements identified where applicable.
- NFRs with numbers (SLO, latency, volume), not adjectives.
- No secrets, credentials or real customer data in the document.
- No pending
[NEEDS CLARIFICATION]markers (resolve with /clarify; the decisions are recorded in the Clarifications section). - SC-xx success criteria measurable and technology-agnostic (threshold and deadline; certifiable in F7 and checkable against knowledge/usage.md).
- Stories prioritized [P1]/[P2]/[P3]; the P1s on their own constitute a viable and independently testable MVP.
Complement: the CROSS-consistency with business rules, ADRs, as-is and task plan is audited by /consistency; recommend it if it has not been run yet.
Final verdict: READY FOR DoR / NEEDS CHANGES (prioritized list). Do not edit the spec: report; changes are applied by the create-review-improve cycle.
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.

