spec-driven-development
Skill0 starsChanged 17 days agoNo licenceView on GitHub
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.
103 other projects use a version of this, 57 of them edited.
Adopted by
Most recently taken up by
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- mariano-aguero/spec-driven-development-skilltheir own version, first seen Nov 8, 2026
- ishandutta2007/Awesome-Agent-Skillsedited, first seen Nov 8, 2026
- MMACABRE/SKILLSedited, first seen Nov 8, 2026
- steven123397/nexuskit-skillsedited, first seen Nov 1, 2026
- rumotion/ai-agent-project-templatetheir own version, first seen Nov 1, 2026
Used with
Projects with it also use using-agent-skills, idea-refine 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.
LLl0k0laDSkillusing-agent-skills
Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
Also in 44 projects that use this
LLl0k0laDSkillidea-refine
Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.
Also in 54 projects that use this
MrCipherSmithSkillconstraint-driven-development
Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
Also in 16 projects that use this
HK-hubSkillobservability-and-instrumentation
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
Also in 36 projects that use this
seikaikyoSkilldoubt-driven-development
對非平凡決策啟動新鮮 context 對抗審查(找碴不背書),在修正還便宜的時候抓出錯誤方向。適用:高風險改動(production、資安敏感邏輯、不可逆操作)、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。
Also in 44 projects that use this
- +7 more from LLl0k0laD
Other versions103 projects use a version of this.
Word for word · 4
- Assist-phung-van-dung/claude-skills★ 0100% same
- elvladislavo/claude-skills★ 0100% same
- kitloomlk-stack/spec-driven-planning-kit★ 0100% same
- VorElze/hermes-office-skills★ 0100% same
Edited · 57
- addyosmani/agent-skills★ 114k100% same
- ollaya-dev/ollaya★ 1.4k99% same
- shashankswe2020-ux/whoop-mcp★ 17495% same
- vinvcn/addyosmani-agent-skills-zh★ 4632% same
- sampleXbro/agentsmesh★ 2795% same
- jaskirat1616/grok-skills★ 2299% same
- ishandutta2007/Awesome-Agent-Skills★ 2196% same
- HK-hub/AgentSkills★ 695% same
- coreplanelabs/switchboard★ 597% same
- lza6/claw-code-tingfeng★ 595% same
47 more not listed
Wrote their own version · 42
- kdlbs/kandev★ 1.1ksame name
- jasonkneen/kiro★ 753same name
- magnus919/agent-skills★ 172same name
- FredAntB/Spec-Driven-Development★ 153same name
- tranhieutt/software_development_department★ 71same name
- drvoss/everything-copilot-cli★ 48same name
- krzysztofsurdy/code-virtuoso★ 36same name
- jmxt3/gitscape.ai★ 33same name
- VoDaiLocz/kilo-kit-mcp★ 28same name
- mariano-aguero/spec-driven-development-skill★ 11same name
32 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 repository7 other files it gives its agents.
- code-reviewSkill
- java-junitSkill
- java-springbootSkill
- 软件开发总调度Skill
- spring-boot-openapi-documentationSkill
- springboot-patternsSkill
- writing-design-docsSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 92 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — 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 92 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.

