User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Pre-Execution Checks
Check for extension hooks (before planning):
- Check if
.specify/extensions.yml exists in the project root.
- If it exists, read it and look for entries under the
hooks.before_plan key
- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
- Filter out hooks where
enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
- For each remaining hook, do not attempt to interpret or evaluate hook
condition expressions:
- If the hook has no
condition field, 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
- When constructing slash commands 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
optional flag:
- Optional hook (
optional: true):## Extension Hooks
**Optional Pre-Hook**: {extension}
Command: `/{command}`
Description: {description}
Prompt: {prompt}
To execute: `/{command}`
- Mandatory hook (
optional: false):## Extension Hooks
**Automatic Pre-Hook**: {extension}
Executing: `/{command}`
EXECUTE_COMMAND: {command}
Wait for the result of the hook command before proceeding to the Outline.
- If no hooks are registered or
.specify/extensions.yml does not exist, skip silently
Outline
Setup: Run .specify/scripts/powershell/setup-plan.ps1 -Json from repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_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
- Phase 1: Update agent context by running the agent script
- Re-evaluate Constitution Check post-design
Stop and report: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.
Check for extension hooks: After reporting, check if .specify/extensions.yml exists in the project root.
- If it exists, read it and look for entries under the
hooks.after_plan key
- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
- Filter out hooks where
enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
- For each remaining hook, do not attempt to interpret or evaluate hook
condition expressions:
- If the hook has no
condition field, 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
- When constructing slash commands 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
optional flag:
- Optional hook (
optional: true):## Extension Hooks
**Optional Hook**: {extension}
Command: `/{command}`
Description: {description}
Prompt: {prompt}
To execute: `/{command}`
- Mandatory hook (
optional: false):## Extension Hooks
**Automatic Hook**: {extension}
Executing: `/{command}`
EXECUTE_COMMAND: {command}
- If no hooks are registered or
.specify/extensions.yml does not exist, skip silently
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.md using 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.)
Agent context update:
- Update the plan reference between the
<!-- SPECKIT START --> and <!-- SPECKIT END --> markers in CLAUDE.md to point to the plan file created in step 1 (the IMPL_PLAN path)
Output: data-model.md, /contracts/*, quickstart.md, updated agent context file
Key rules
- Use absolute paths for filesystem operations; use project-relative paths for references in documentation and agent context files
- ERROR on gate failures or unresolved clarifications
1---
2name: "speckit-plan"
3description: "Execute the implementation planning workflow using the plan template to generate design artifacts."
4argument-hint: "Optional guidance for the planning phase"
5compatibility: "Requires spec-kit project structure with .specify/ directory"
6metadata:
7 author: "github-spec-kit"
8 source: https://skillmd.com/skills/unoplatform/speckit-plan
9 upstream: "templates/commands/plan.md"
10user-invocable: true
11disable-model-invocation: false
12---
13
14
15## User Input
16
17```text
18$ARGUMENTS
19```
20
21You **MUST** consider the user input before proceeding (if not empty).
22
23## Pre-Execution Checks
24
25**Check for extension hooks (before planning)**:
26- Check if `.specify/extensions.yml` exists in the project root.
27- If it exists, read it and look for entries under the `hooks.before_plan` key
28- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
29- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
30- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
31 - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
32 - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
33- When constructing slash commands from hook command names, replace dots (`.`) with hyphens (`-`). For example, `speckit.git.commit` → `/speckit-git-commit`.
34- For each executable hook, output the following based on its `optional` flag:
35 - **Optional hook** (`optional: true`):
36 ```
37 ## Extension Hooks
38
39 **Optional Pre-Hook**: {extension}
40 Command: `/{command}`
41 Description: {description}
42
43 Prompt: {prompt}
44 To execute: `/{command}`
45 ```
46 - **Mandatory hook** (`optional: false`):
47 ```
48 ## Extension Hooks
49
50 **Automatic Pre-Hook**: {extension}
51 Executing: `/{command}`
52 EXECUTE_COMMAND: {command}
53
54 Wait for the result of the hook command before proceeding to the Outline.
55 ```
56- If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
57
58## Outline
59
601. **Setup**: Run `.specify/scripts/powershell/setup-plan.ps1 -Json` from repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_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").
61
622. **Load context**: Read FEATURE_SPEC and `.specify/memory/constitution.md`. Load IMPL_PLAN template (already copied).
63
643. **Execute plan workflow**: Follow the structure in IMPL_PLAN template to:
65 - Fill Technical Context (mark unknowns as "NEEDS CLARIFICATION")
66 - Fill Constitution Check section from constitution
67 - Evaluate gates (ERROR if violations unjustified)
68 - Phase 0: Generate research.md (resolve all NEEDS CLARIFICATION)
69 - Phase 1: Generate data-model.md, contracts/, quickstart.md
70 - Phase 1: Update agent context by running the agent script
71 - Re-evaluate Constitution Check post-design
72
734. **Stop and report**: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.
74
755. **Check for extension hooks**: After reporting, check if `.specify/extensions.yml` exists in the project root.
76 - If it exists, read it and look for entries under the `hooks.after_plan` key
77 - If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
78 - Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
79 - For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
80 - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
81 - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
82 - When constructing slash commands from hook command names, replace dots (`.`) with hyphens (`-`). For example, `speckit.git.commit` → `/speckit-git-commit`.
83 - For each executable hook, output the following based on its `optional` flag:
84 - **Optional hook** (`optional: true`):
85 ```
86 ## Extension Hooks
87
88 **Optional Hook**: {extension}
89 Command: `/{command}`
90 Description: {description}
91
92 Prompt: {prompt}
93 To execute: `/{command}`
94 ```
95 - **Mandatory hook** (`optional: false`):
96 ```
97 ## Extension Hooks
98
99 **Automatic Hook**: {extension}
100 Executing: `/{command}`
101 EXECUTE_COMMAND: {command}
102 ```
103 - If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
104
105## Phases
106
107### Phase 0: Outline & Research
108
1091. **Extract unknowns from Technical Context** above:
110 - For each NEEDS CLARIFICATION → research task
111 - For each dependency → best practices task
112 - For each integration → patterns task
113
1142. **Generate and dispatch research agents**:
115
116 ```text
117 For each unknown in Technical Context:
118 Task: "Research {unknown} for {feature context}"
119 For each technology choice:
120 Task: "Find best practices for {tech} in {domain}"
121 ```
122
1233. **Consolidate findings** in `research.md` using format:
124 - Decision: [what was chosen]
125 - Rationale: [why chosen]
126 - Alternatives considered: [what else evaluated]
127
128**Output**: research.md with all NEEDS CLARIFICATION resolved
129
130### Phase 1: Design & Contracts
131
132**Prerequisites:** `research.md` complete
133
1341. **Extract entities from feature spec** → `data-model.md`:
135 - Entity name, fields, relationships
136 - Validation rules from requirements
137 - State transitions if applicable
138
1392. **Define interface contracts** (if project has external interfaces) → `/contracts/`:
140 - Identify what interfaces the project exposes to users or other systems
141 - Document the contract format appropriate for the project type
142 - Examples: public APIs for libraries, command schemas for CLI tools, endpoints for web services, grammars for parsers, UI contracts for applications
143 - Skip if project is purely internal (build scripts, one-off tools, etc.)
144
1453. **Agent context update**:
146 - Update the plan reference between the `<!-- SPECKIT START -->` and `<!-- SPECKIT END -->` markers in `CLAUDE.md` to point to the plan file created in step 1 (the IMPL_PLAN path)
147
148**Output**: data-model.md, /contracts/*, quickstart.md, updated agent context file
149
150## Key rules
151
152- Use absolute paths for filesystem operations; use project-relative paths for references in documentation and agent context files
153- ERROR on gate failures or unresolved clarifications