speckit-plan
Skill34 starsChanged 47 days agoMITView 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
- finolabs/vibebizword for word, first seen Nov 15, 2026
- 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
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
- dogganidhal/agui-inspector★ 4100% same
- maumenvi/maia-cli★ 2100% 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 repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
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.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Check if .specify/extensions.yml exists in the project root.
- Very specific: line 26
If it exists, read it and look for entries under the hooks.before_plan key
- Very specific: line 27
If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that .specify/extensions.yml could not be read (include the …
- Very specific: line 30
If the hook has no condition field, or it is null/empty, treat the hook as executable
- Very specific: line 31
If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementation
- Very specific: line 32
When constructing command invocations from hook command names, replace dots (.) with hyphens (-).
- Very specific: line 56
If no hooks are registered or .specify/extensions.yml does not exist, skip silently
- Very specific: line 60
Setup: Run .specify/scripts/bash/setup-plan.sh --json from repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, FEATURE_DIR, BRANCH.
- Very specific: line 62
Load context: Read FEATURE_SPEC and .specify/memory/constitution.md.
- Very specific: line 64
Execute plan workflow: Follow the structure in IMPL_PLAN template to:
- Very specific: line 77
If it does not exist, or no hooks are registered under hooks.after_plan, skip to the Completion Report.
- Very specific: line 78
If it exists, read it and look for entries under the hooks.after_plan key.
- Very specific: line 79
If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that .specify/extensions.yml could not be read (include the …
- Common: line 147
Document the contract format appropriate for the project type
- Common: line 152
Document runnable validation scenarios that prove the feature works end-to-end
- Common: line 154
Use links or references to contracts and data model details instead of duplicating them
- Very specific: line 155
Do not include full implementation code, model/service/controller bodies, migrations, or complete test suites
- Very specific: line 156
Keep this artifact as a validation/run guide.
- Common: line 162
Use absolute paths for filesystem operations.
“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.
Files
User Input
$ARGUMENTSYou MUST consider the user input before proceeding (if not empty).
Pre-Execution Checks
Check for extension hooks (before planning):
- Check if
.specify/extensions.ymlexists in the project root. - If it exists, read it and look for entries under the
hooks.before_plankey - 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, then continue normally - Filter out hooks where
enabledis explicitlyfalse. Treat hooks without anenabledfield as enabled by default. - For each remaining hook, do not attempt to interpret or evaluate hook
conditionexpressions:- If the hook has no
conditionfield, or it is null/empty, treat the hook as executable - If the hook defines a non-empty
condition, skip the hook and leave condition evaluation to the HookExecutor implementation
- If the hook has no
- When constructing command invocations from hook command names, replace dots (
.) with hyphens (-). For example,speckit.git.commit→/speckit-git-commit. - For each executable hook, output the following based on its
optionalflag:- Optional hook (
optional: true):## Extension Hooks **Optional Pre-Hook**: {extension} Command: `/{command}` Description: {description} Prompt: {prompt} To execute: `/{command}` - Mandatory hook (
optional: false):
After emitting the block above you MUST actually invoke the hook and wait for it to finish before continuing. Run it the same way you would run the command yourself in this agent/session (the invocation may differ from the literal## Extension Hooks **Automatic Pre-Hook**: {extension} Executing: `/{command}` EXECUTE_COMMAND: {command} Wait for the result of the hook command before proceeding to the Outline.{command}id shown above, e.g. a skills-mode agent runs it as/skill:speckit-...or$speckit-...). Emitting the block alone does not run the hook.
- Optional hook (
- If no hooks are registered or
.specify/extensions.ymldoes not exist, skip silently
Outline
- Setup: Run
.specify/scripts/bash/setup-plan.sh --jsonfrom repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, FEATURE_DIR, BRANCH. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot"). - Load context: Read FEATURE_SPEC and
.specify/memory/constitution.md. Load IMPL_PLAN template (already copied). - Execute plan workflow: Follow the structure in IMPL_PLAN template to:
- Fill Technical Context (mark unknowns as "NEEDS CLARIFICATION")
- Fill Constitution Check section from constitution
- Evaluate gates (ERROR if violations unjustified)
- Phase 0: Generate research.md (resolve all NEEDS CLARIFICATION)
- Phase 1: Generate data-model.md, contracts/, quickstart.md
- Re-evaluate Constitution Check post-design
Mandatory Post-Execution Hooks
You MUST complete this section before reporting completion to the user.
Check if .specify/extensions.yml exists in the project root.
- If it does not exist, or no hooks are registered under
hooks.after_plan, skip to the Completion Report. - If it exists, read it and look for entries under the
hooks.after_plankey. - 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, then continue to the Completion Report. - Filter out hooks where
enabledis explicitlyfalse. Treat hooks without anenabledfield as enabled by default. - For each remaining hook, do not attempt to interpret or evaluate hook
conditionexpressions:- If the hook has no
conditionfield, or it is null/empty, treat the hook as executable - If the hook defines a non-empty
condition, skip the hook and leave condition evaluation to the HookExecutor implementation
- If the hook has no
- When constructing command invocations from hook command names, replace dots (
.) with hyphens (-). For example,speckit.git.commit→/speckit-git-commit. - For each executable hook, output the following based on its
optionalflag:- Mandatory hook (
optional: false) — You MUST emitEXECUTE_COMMAND:for each mandatory hook:
After emitting the block above you MUST actually invoke the hook and wait for it to finish before continuing. Run it the same way you would run the command yourself in this agent/session (the invocation may differ from the literal## Extension Hooks **Automatic Hook**: {extension} Executing: `/{command}` EXECUTE_COMMAND: {command}{command}id shown above, e.g. a skills-mode agent runs it as/skill:speckit-...or$speckit-...). Emitting the block alone does not run the hook. - Optional hook (
optional: true):## Extension Hooks **Optional Hook**: {extension} Command: `/{command}` Description: {description} Prompt: {prompt} To execute: `/{command}`
- Mandatory hook (
Completion Report
Command ends after Phase 1 design. Report branch, IMPL_PLAN path, and generated artifacts.
Phases
Phase 0: Outline & Research
- Extract unknowns from Technical Context above:
- For each NEEDS CLARIFICATION → research task
- For each dependency → best practices task
- For each integration → patterns task
Generate and dispatch research agents:
For each unknown in Technical Context: Task: "Research {unknown} for {feature context}" For each technology choice: Task: "Find best practices for {tech} in {domain}"- Consolidate findings in
research.mdusing format:- Decision: [what was chosen]
- Rationale: [why chosen]
- Alternatives considered: [what else evaluated]
Output: research.md with all NEEDS CLARIFICATION resolved
Phase 1: Design & Contracts
Prerequisites: research.md complete
- Extract entities from feature spec →
data-model.md:- Entity name, fields, relationships
- Validation rules from requirements
- State transitions if applicable
- Define interface contracts (if project has external interfaces) →
/contracts/:- Identify what interfaces the project exposes to users or other systems
- Document the contract format appropriate for the project type
- Examples: public APIs for libraries, command schemas for CLI tools, endpoints for web services, grammars for parsers, UI contracts for applications
- Skip if project is purely internal (build scripts, one-off tools, etc.)
- Create quickstart validation guide →
quickstart.md:- Document runnable validation scenarios that prove the feature works end-to-end
- Include prerequisites, setup commands, test/run commands, and expected outcomes
- Use links or references to contracts and data model details instead of duplicating them
- Do not include full implementation code, model/service/controller bodies, migrations, or complete test suites
- Keep this artifact as a validation/run guide; implementation details belong in
tasks.mdand the implementation phase
Output: data-model.md, /contracts/*, quickstart.md
Key rules
- Use absolute paths for filesystem operations; use project-relative paths for references in documentation
- ERROR on gate failures or unresolved clarifications
Done When
- Plan workflow executed and design artifacts generated
- Extension hooks dispatched or skipped according to the rules in Mandatory Post-Execution Hooks above
- Completion reported to user with branch, plan path, and generated artifacts
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.

