create-spec
Skill447 starsChanged 5 months agoNo licenceView on GitHub
Create a structured feature specification with self-contained task files organized into parallel execution waves. Use this skill when the user says "create a spec", "plan this feature", "write up an implementation plan", "break this into tasks", or after any planning conversation where the user wants to capture decisions as actionable spec files. Also use when the user says "/create-spec" or wants to decompose a feature into work items that agents can implement independently. This skill produces local spec files under specs/{feature}/ — no GitHub integration.
We split this skill into the rules it gives an agent
14 rules. 0 are common, 12 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
2
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 15 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.
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- leonvanzyl/claude-code-pro-workflow-demo★ 4100% same
Wrote their own version · 17
- gittower/git-flow-next★ 458same name
- Levix0501/kiko-skills★ 170same name
- holgerleichsenring/specification-first-agentic-development★ 37same name
- dominicletz/elixir-skills★ 34same name
- NitinJ/specforge★ 4same name
- ReStartAllKill/skills★ 2same name
- sanzhardanybayev/synergy★ 2same name
- sikbrad/spark-harness-template★ 2same name
- araujoleonardo/skills★ 1same name
- itsyasirkhandev/spec-driven-development★ 1same name
7 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.
Used alongsideProjects with it also use review-spec, create-plan and 2 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.
dekozaSkillreview-spec
Use when a diff must be reviewed against the spec, ticket, or issue that originated it — missing requirements, scope creep, and requirements implemented wrongly — producing cited findings and nothing else. One axis of a two-axis review, independently invocable. Triggers on: "spec review", "does this match the ticket", "review the PR against the spec", "did we build what was asked", "spec axis". Does not judge code style — that is review-standards.
Also in 3 projects that use this
JetBrainsSkillcreate-plan
Research the codebase and create an implementation plan with architecture notes, design document, and track decomposition. Use when starting a new feature or large change.
Also in 3 projects that use this
MicrosoftSkillpr-review
Verify the technical accuracy of a vscode-docs pull request against the VS Code source code in microsoft/vscode. Use when reviewing a docs PR for factual correctness: setting names, command IDs, default values, API shapes, keybindings, versioned availability, and described behavior.
Also in 3 projects that use this
- MicrosoftSkill
handoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 4 projects that use this
In this repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- .claude/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-sdkSkill
- better-auth-best-practicesSkill
- checkpointSkill
- create-agentic-appSkill
- create-specSkill
- find-skillsSkill
- frontend-designSkill
- implement-featureSkill
- mcp-builderSkill
- nextjsSkill
- playwright-cliSkill
- review-prSkill
- security-scannerSkill
- shadcnSkill
- ship-itSkill
- skill-creatorSkill
- vercel-react-best-practicesSkill
- web-design-guidelinesSkill
- ai-sdkSkill
- better-auth-best-practicesSkill
- checkpointSkill
- find-skillsSkill
- frontend-designSkill
- implement-featureSkill
- mcp-builderSkill
- nextjsSkill
- playwright-cliSkill
- review-prSkill
- security-scannerSkill
- shadcnSkill
- ship-itSkill
- skill-creatorSkill
- vercel-react-best-practicesSkill
- web-design-guidelinesSkill
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.