spec-kit
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Drive GitHub's Spec Kit (spec-driven development) using the real `specify` CLI and its `/speckit.*` slash commands. Use this whenever the user wants to build a feature spec-first, mentions Spec Kit / spec-driven development / SDD, asks to run `/speckit.specify`, `/speckit.plan`, `/speckit.tasks`, `/speckit.implement`, `/speckit.constitution`, `/speckit.clarify`, `/speckit.analyze`, or `/speckit.checklist`, or asks to scaffold a project with `specify init`. Also use it to turn a spec-kit tasks.md into GitHub issues (`/speckit.taskstoissues`). Also trigger when someone says "write the spec then the plan then the tasks", "set up spec-driven development here", "turn this idea into a spec and implement it", or wants a disciplined spec → plan → tasks → implement workflow for a new feature or greenfield project, even if they don't name Spec Kit explicitly. Do NOT use for one-off code edits or when the user just wants a quick informal design doc.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- aiagentkit-labs/agentic-dev-kittheir own version, first seen Nov 8, 2026
- rloisell/rl-agents-n-skillstheir own version, first seen Jun 5, 2026
- shaunburdick/skillstheir own version, first seen Apr 19, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- rloisell/rl-agents-n-skills★ 8same name
- shaunburdick/skills★ 1same name
- aiagentkit-labs/agentic-dev-kit★ 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 repository8 other files it gives its agents.
- dev-sparkSkill
- evidence-first-troubleshootingSkill
- exec-requestsSkill
- humanizerSkill
- nntSkill
- session-reflectSkill
- sigma-computingSkill
- web-perfSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 1 is distinctive, and 9 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
9
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 3 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.