spec-driven
Skill1 starsChanged 41 days agoMITView on GitHub
Turn requirements into a short executable spec before coding. Use when building features with acceptance criteria, multi-step product work, or ambiguous requests.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- adeonir/agent-skillstheir own version, first seen Nov 6, 2026
- Snowflake-Labs/coco-skillstheir own version, first seen Nov 1, 2026
- NoatToan/claude-code-pluginstheir own version, first seen Nov 1, 2026
- stoa-platform/stoatheir own version, first seen Nov 1, 2026
- microsoft/FSQtheir own version, first seen Oct 13, 2026
- zazzcode/zazz-skillstheir own version, first seen Aug 1, 2026
Used with
Projects with it also use implement.
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.
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 3 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- agencia-conversion/agentic-seo-skills★ 51same name
- Snowflake-Labs/coco-skills★ 49same name
- microsoft/FSQ★ 23same name
- stoa-platform/stoa★ 9same name
- adeonir/agent-skills★ 8same name
- creoaurea-devlab/agentic-skills★ 4same name
- zazzcode/zazz-skills★ 4same name
- 90sRehem/agent-skills★ 2same name
- b12consulting/skills★ 2same name
- hbarbosa02/alaz-mcp-nestjs★ 2same name
4 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 repository49 other files it gives its agents.
- accessibilitySkill
- address-feedbackSkill
- agent-disciplineSkill
- agent-handoffSkill
- api-designSkill
- architecture-decisionSkill
- brainstormSkill
- browser-verifySkill
- code-reviewSkill
- containerizeSkill
- context-efficientSkill
- create-prSkill
- database-changesSkill
- debug-systematicSkill
- dependency-upgradeSkill
- docs-groundedSkill
- error-handlingSkill
- explore-codebaseSkill
- fix-ciSkill
- frontend-designSkill
- git-commitSkill
- git-worktreeSkill
- incident-triageSkill
- incremental-slicesSkill
- legacy-changeSkill
- migrate-codeSkill
- minimal-diffSkill
- observabilitySkill
- parallel-workSkill
- performance-auditSkill
- plan-before-codeSkill
- python-qualitySkill
- react-componentsSkill
- refactor-safeSkill
- release-notesSkill
- security-reviewSkill
- setup-ciSkill
- shell-safetySkill
- ship-checklistSkill
- simplify-codeSkill
- skill-authoringSkill
- skill-routerSkill
- tddSkill
- threat-modelSkill
- triage-issuesSkill
- typescript-strictSkill
- verify-workSkill
- write-docsSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
3
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 35
Do not invent product requirements silently.
- Distinctive: line 36
Prefer measurable acceptance over vague quality words.
- Distinctive: line 37
Keep the spec short enough to re-read in one glance.
“Common” is measured: kept by at least 6 in 10 of the 12 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 Driven
Process
- Extract must-haves vs nice-to-haves.
- Define acceptance checks that can pass/fail.
- List out-of-scope items.
- Identify data model / API / UI surfaces touched.
- Get confirmation when requirements conflict or are incomplete.
- Implement against the acceptance checks.
- Verify each check.
Spec Format
Problem: ...
Users / trigger: ...
Must:
- ...
Must not:
- ...
Acceptance:
- [ ] ...
Out of scope:
- ...Rules
- Do not invent product requirements silently.
- Prefer measurable acceptance over vague quality words.
- Keep the spec short enough to re-read in one glance.
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.