speckit-plan
Skill1 starsChanged 4 days agoLicence not identifiedView on GitHub
Execute the implementation planning workflow using the plan template to generate design artifacts.
133 other projects use a version of this, 112 of them edited; 98 of 111 edited versions we compared changed its rules; 7 new projects in the last 4 weeks, against 11 the 4 before.
How people change it
98 of 111 edited versions changed its rules, and some changes recur.
Of the 111 edited versions we compared: 13 keep every rule, 98 made changes of their own.
Rules people drop
- If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that
.specify/extensions.ymlcould not be read (include the parser error) and that no hooks were checked, including any mandatory (optional: false) hooks registered there, …dropped by 97 of 98 - If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that
.specify/extensions.ymlcould not be read (include the parser error) and that no hooks were checked, including any mandatory (optional: false) hooks registered there, …dropped by 97 of 98 - Document runnable validation scenarios that prove the feature works end-to-enddropped by 38 of 98
- Use links or references to contracts and data model details instead of duplicating themdropped by 38 of 98
- Do not include full implementation code, model/service/controller bodies, migrations, or complete test suitesdropped by 38 of 98
- Keep this artifact as a validation/run guide; implementation details belong in
tasks.mdand the implementation phasedropped by 38 of 98 - When constructing command invocations from hook command names, replace dots (
.) with hyphens (-). For example,speckit.git.commit→/speckit-git-commit.dropped by 16 of 98 - Use absolute paths for filesystem operations; use project-relative paths for references in documentationdropped by 10 of 98
Rules people add
- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normallyadded by 94 of 98
- Update the plan reference between the
<!-- SPECKIT START -->and<!-- SPECKIT END -->markers inCLAUDE.mdto point to the plan file created in step 1 (the IMPL_PLAN path)added by 39 of 98 - Update the appropriate agent-specific context fileadded by 9 of 98
- Add only new technology from current planadded by 9 of 98
- A rule we can't quote: its licence doesn't allow itadded by 2 of 98
- A rule we can't quote: its licence doesn't allow itadded by 2 of 98
- A rule we can't quote: its licence doesn't allow itadded by 2 of 98
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Cooling: 7 new projects took it in the last 4 weeks, 0.6× the 4 weeks before.
Most recently taken up by
- jaroslawherod/micold-ai-ideword for word, first seen Nov 15, 2026
- Kemetra/Seshat-BIedited, first seen Nov 15, 2026
- Azure/agent-landing-zoneedited, first seen Nov 14, 2026
- Azure/GPT-RAGedited, first seen Nov 14, 2026
- dceoy/speckit-agent-skillsedited, first seen Nov 14, 2026
- thinkmorestupidless/ankkaedited, first seen Nov 11, 2026
Used with
Projects with it also use speckit-agent-context-update, speckit-git-commit 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.
Microsoft AzureSkillspeckit-agent-context-update
Refresh the managed Spec Kit section in coding agent context file(s)
Also in 13 projects that use this
Sorcha-PlatformSkillspeckit-git-commit
Auto-commit changes after a Spec Kit command completes
Also in 35 projects that use this
Sorcha-PlatformSkillspeckit-git-feature
Create a feature branch with sequential or timestamp numbering
Also in 35 projects that use this
patterson-agentsSkillspeckit-baseline
Generate feature specifications by analyzing existing source code.
Also in 3 projects that use this
patterson-agentsSkillclaude-command-converter
Convert Claude Code commands (.claude/commands/*.md) to standard Agent Skills (skills/*/SKILL.md). Use when migrating slash commands to portable skill format, creating skills from existing commands, or standardizing command definitions across AI runtimes.
Also in 3 projects that use this
Microsoft AzureSkillagentic-workflows
Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.
Also in 3 projects that use this
- +3 more from Sorcha-Platform
Other versions133 projects use a version of this.
Word for word · 18
- pamburus/hl★ 3.3k100% same
- nornir-automation/nornir★ 1.6k100% same
- dotCMS/core★ 971100% same
- nota-daw/nota★ 542100% same
- haru/redmine_ai_helper★ 107100% same
- alfredoperez/speckit-companion★ 105100% same
- getgantry/gantry★ 90100% same
- zalando-incubator/agentic-identity-broker★ 79100% same
- raccioly/docguard★ 34100% same
- dogganidhal/agui-inspector★ 4100% same
8 more not listed
Edited · 112
- pmndrs/react-spring★ 29k82% same
- unoplatform/uno★ 10k81% same
- elsa-workflows/elsa-core★ 7.9k89% same
- hhyo/Archery★ 7.1k97% same
- cloudposse/atmos★ 1.4k82% same
- Azure/agent-landing-zone★ 1.2k96% same
- Azure/GPT-RAG★ 1.2k96% same
- meshtastic/Meshtastic-Apple★ 96382% same
- georgedouzas/sports-betting★ 81295% same
- automateyournetwork/netclaw★ 71880% same
102 more not listed
Wrote their own version · 3
- sunhaoyu-1990/Claude-Code-Cock★ 8same name
- sarveshtalele/mcp-skills-registry★ 2same name
- TienDat-Vna/BackSpec★ 1same 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 repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- speckit-specifySkill
- speckit-tasksSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. 4 are common, 0 are distinctive, and 15 are very specific to this project.
4
Common
Most of the 111 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
15
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — 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 111 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.

