User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Pre-Execution Checks
Check for extension hooks (before convergence):
Check if .specify/extensions.yml exists in the project root.
If it exists, read it and look for entries under the hooks.before_converge 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 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 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 Goal.
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 {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.
If no hooks are registered or .specify/extensions.yml does not exist, skip silently
Goal
Close the gap between what a feature's specification, plan, and tasks call for and what the
codebase currently implements. Read spec.md, plan.md, and tasks.md as the sole
source of intent (with the constitution as governing constraints), assess the current
state of the code, determine which requirements, acceptance criteria, plan decisions, and
existing tasks are unmet, incomplete, or only partially satisfied, and append each piece
of remaining work as a new, traceable task at the bottom of tasks.md so that
/speckit-implement can complete it. This command MUST run only after
/speckit-implement has run on the current tasks.md, and after /speckit-tasks has produced a complete tasks.md.
This is not a diff tool and does not track changes. It assesses the present state
of the code relative to the feature's artifacts — no git, no branch comparison, no history.
Operating Constraints
APPEND-ONLY, NEVER REWRITE: The command's only write is appending a new
## Phase N: Convergence section to tasks.md. It MUST NOT:
- modify
spec.md or plan.md in any way;
- rewrite, renumber, reorder, or delete any existing task (including tasks from a prior
Convergence phase);
- modify, create, or delete any application code — completing the appended tasks is the
job of
/speckit-implement.
When the codebase already satisfies everything, the command MUST leave tasks.md
byte-for-byte unchanged (no empty Convergence header) and report a clean result.
Constitution Authority: The project constitution (.specify/memory/constitution.md) is
non-negotiable. Code that violates a MUST principle is the highest-severity finding and
produces a corresponding remediation task. If the constitution is an unfilled template,
skip constitution checks gracefully rather than failing.
Execution Steps
1. Initialize Convergence Context
Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks once from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Derive absolute paths:
- SPEC = FEATURE_DIR/spec.md
- PLAN = FEATURE_DIR/plan.md
- TASKS = FEATURE_DIR/tasks.md
- CONSTITUTION =
.specify/memory/constitution.md (if present)
If spec.md, plan.md, or tasks.md is missing, STOP with a clear, actionable message naming the
prerequisite command to run (/speckit-specify for a missing spec, /speckit-plan for a missing plan,
/speckit-tasks for missing tasks). Do not produce partial output.
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").
2. Load Artifacts (Progressive Disclosure)
Load only the minimal necessary context from each artifact:
From spec.md:
- Functional Requirements (FR-###)
- Success Criteria (SC-###) — include only items requiring buildable work; exclude
post-launch outcome metrics and business KPIs
- User Stories and their Acceptance Scenarios
- Edge Cases (if present)
From plan.md:
- Architecture/stack choices and technical decisions
- Data Model references
- Phases and named touch-points (files/components the plan says will be created or edited)
- Technical constraints
From tasks.md:
- Task IDs (to compute the next ID and next phase number)
- Descriptions, phase grouping, and referenced file paths
From constitution (if not an unfilled template):
- Principle names and MUST/SHOULD normative statements
3. Build the Intent Inventory
Create an internal model (do not echo raw artifacts):
- Requirements inventory: one stable key per FR-### / SC-### / user-story acceptance
scenario (e.g.
US1/AC2), plus the plan decisions and constitution principles that
impose buildable obligations.
- Code-scope map: from the file paths named in
plan.md and tasks.md, plus a keyword
search for the concepts each requirement describes, derive the set of source files and
components in scope for assessment. Bound the assessment to these — do not infer
scope beyond what the artifacts define.
4. Assess the Codebase and Classify Findings
For each item in the intent inventory, inspect the current code in scope and produce a
Finding only where there is a gap. Classify every finding by gap type:
missing: the required work is absent from the code entirely.
partial: the work exists but does not yet fully satisfy the requirement /
acceptance criterion / plan decision.
contradicts: the code does something that conflicts with stated intent or a
constitution MUST principle.
unrequested: the code contains work not called for by the spec, plan, or tasks
(surfaced for awareness — converge does not delete code, it only appends a task to
review/justify or remove it).
Each Finding records: a stable id, the source-ref it traces to, the gap-type, a
severity, and a short human-readable description with the evidence (the file/area observed).
Edge cases:
- Little or no code yet: treat the entire specified scope as
missing remaining work
rather than failing.
- Nothing remains: produce zero findings and follow the converged branch in Step 7.
5. Assign Severity
- CRITICAL: violates a constitution MUST principle, or a
missing/contradicts gap
that blocks baseline functionality of a P1 user story.
- HIGH: a
missing or partial gap on a core functional requirement or acceptance
criterion.
- MEDIUM: a
partial gap on a secondary requirement, or an unrequested addition with
unclear justification.
- LOW: minor partial gaps, polish, or low-risk
unrequested additions.
6. Present the In-Session Findings Summary
Before appending anything, output a compact, severity-graded summary (no file writes yet):
Convergence Findings
| ID |
Gap Type |
Severity |
Source |
Evidence |
Remaining Work |
| F1 |
missing |
HIGH |
FR-008 |
Example: no append-only guard detected in path/to/module.py when writing tasks.md |
Add append-only enforcement |
Summary metrics:
- Requirements / acceptance criteria checked
- Plan decisions checked
- Constitution principles checked (or "skipped — template")
- Findings by gap type (missing / partial / contradicts / unrequested)
- Findings by severity
7. Append Convergence Tasks (or report converged)
If there are one or more actionable findings (tasks_appended outcome):
Append to the end of tasks.md, per the append contract:
Scan all existing task IDs; let M be the maximum. Determine the next phase number N
(highest existing phase + 1).
Write a single new section header ## Phase N: Convergence.
Emit one checklist item per actionable finding, ordered CRITICAL/HIGH first, assigning
zero-padded IDs T{M+1:03d}, T{M+2:03d}, …:
- [ ] T042 <imperative description> per <source-ref> (<gap-type>)
<source-ref> traces the task to its origin: e.g. FR-003, SC-002,
US1/AC2, plan: storage decision, Constitution II.
<gap-type> is one of missing, partial, contradicts, unrequested.
Constitution-violation tasks MUST be emitted first and described as
CRITICAL.
Never reuse or renumber existing IDs. If a prior Convergence phase exists, add a new,
separately-numbered one below it — do not touch the old one.
If there are no actionable findings (converged outcome):
- Do not modify
tasks.md at all — no empty phase header.
- Report: "✅ Converged — the implementation satisfies the spec, plan, and tasks."
- Include the summary counts of what was checked.
8. Provide Next Actions (Handoff)
- On
tasks_appended: state how many tasks were appended under which phase, and recommend
running /speckit-implement to complete them; note that a follow-up converge
run will find fewer or no remaining items.
- On
converged: recommend proceeding to review / opening a PR. No further implement pass
is needed for this feature's specified scope.
9. Check for extension hooks
After producing the result, check if .specify/extensions.yml exists in the project root.
If it exists, read it and look for entries under the hooks.after_converge 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
Report the convergence outcome (converged or tasks_appended) in-session before listing
any hooks, so users can decide whether to run optional follow-up commands.
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 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}
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 {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.
If no hooks are registered or .specify/extensions.yml does not exist, skip silently
1---
2name: "speckit-converge"
3description: "Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it."
4compatibility: "Requires spec-kit project structure with .specify/ directory"
5metadata:
6 author: "github-spec-kit"
7 source: https://skillmd.com/skills/dceoy/speckit-converge
8 upstream: "templates/commands/converge.md"
9user-invocable: true
10disable-model-invocation: false
11---
12
13## User Input
14
15```text
16$ARGUMENTS
17```
18
19You **MUST** consider the user input before proceeding (if not empty).
20
21## Pre-Execution Checks
22
23**Check for extension hooks (before convergence)**:
24
25- Check if `.specify/extensions.yml` exists in the project root.
26- If it exists, read it and look for entries under the `hooks.before_converge` key
27- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
28- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
29- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
30 - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
31 - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
32- When constructing command invocations from hook command names, replace dots (`.`) with hyphens (`-`). For example, `speckit.git.commit` → `/speckit-git-commit`.
33- For each executable hook, output the following based on its `optional` flag:
34 - **Optional hook** (`optional: true`):
35
36 ```text
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
47 - **Mandatory hook** (`optional: false`):
48
49 ```text
50 ## Extension Hooks
51
52 **Automatic Pre-Hook**: {extension}
53 Executing: `/{command}`
54 EXECUTE_COMMAND: {command}
55
56 Wait for the result of the hook command before proceeding to the Goal.
57 ```
58
59 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 `{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.
60
61- If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently
62
63## Goal
64
65Close the gap between what a feature's specification, plan, and tasks call for and what the
66codebase currently implements. Read `spec.md`, `plan.md`, and `tasks.md` as the **sole
67source of intent** (with the constitution as governing constraints), assess the current
68state of the code, determine which requirements, acceptance criteria, plan decisions, and
69existing tasks are unmet, incomplete, or only partially satisfied, and **append each piece
70of remaining work as a new, traceable task** at the bottom of `tasks.md` so that
71`/speckit-implement` can complete it. This command MUST run only after
72`/speckit-implement` has run on the current `tasks.md`, and after `/speckit-tasks` has produced a complete `tasks.md`.
73
74This is **not** a diff tool and does **not** track changes. It assesses the present state
75of the code relative to the feature's artifacts — no git, no branch comparison, no history.
76
77## Operating Constraints
78
79**APPEND-ONLY, NEVER REWRITE**: The command's **only** write is appending a new
80`## Phase N: Convergence` section to `tasks.md`. It MUST NOT:
81
82- modify `spec.md` or `plan.md` in any way;
83- rewrite, renumber, reorder, or delete any existing task (including tasks from a prior
84 Convergence phase);
85- modify, create, or delete any application code — completing the appended tasks is the
86 job of `/speckit-implement`.
87
88When the codebase already satisfies everything, the command MUST leave `tasks.md`
89**byte-for-byte unchanged** (no empty Convergence header) and report a clean result.
90
91**Constitution Authority**: The project constitution (`.specify/memory/constitution.md`) is
92**non-negotiable**. Code that violates a MUST principle is the highest-severity finding and
93produces a corresponding remediation task. If the constitution is an unfilled template,
94skip constitution checks gracefully rather than failing.
95
96## Execution Steps
97
98### 1. Initialize Convergence Context
99
100Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` once from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Derive absolute paths:
101
102- SPEC = FEATURE_DIR/spec.md
103- PLAN = FEATURE_DIR/plan.md
104- TASKS = FEATURE_DIR/tasks.md
105- CONSTITUTION = `.specify/memory/constitution.md` (if present)
106 If `spec.md`, `plan.md`, or `tasks.md` is missing, STOP with a clear, actionable message naming the
107 prerequisite command to run (`/speckit-specify` for a missing spec, `/speckit-plan` for a missing plan,
108 `/speckit-tasks` for missing tasks). Do not produce partial output.
109 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").
110
111### 2. Load Artifacts (Progressive Disclosure)
112
113Load only the minimal necessary context from each artifact:
114
115**From spec.md:**
116
117- Functional Requirements (FR-###)
118- Success Criteria (SC-###) — include only items requiring buildable work; exclude
119 post-launch outcome metrics and business KPIs
120- User Stories and their Acceptance Scenarios
121- Edge Cases (if present)
122
123**From plan.md:**
124
125- Architecture/stack choices and technical decisions
126- Data Model references
127- Phases and named touch-points (files/components the plan says will be created or edited)
128- Technical constraints
129
130**From tasks.md:**
131
132- Task IDs (to compute the next ID and next phase number)
133- Descriptions, phase grouping, and referenced file paths
134
135**From constitution (if not an unfilled template):**
136
137- Principle names and MUST/SHOULD normative statements
138
139### 3. Build the Intent Inventory
140
141Create an internal model (do not echo raw artifacts):
142
143- **Requirements inventory**: one stable key per FR-### / SC-### / user-story acceptance
144 scenario (e.g. `US1/AC2`), plus the plan decisions and constitution principles that
145 impose buildable obligations.
146- **Code-scope map**: from the file paths named in `plan.md` and `tasks.md`, plus a keyword
147 search for the concepts each requirement describes, derive the set of source files and
148 components in scope for assessment. Bound the assessment to these — do **not** infer
149 scope beyond what the artifacts define.
150
151### 4. Assess the Codebase and Classify Findings
152
153For each item in the intent inventory, inspect the current code in scope and produce a
154`Finding` only where there is a gap. Classify every finding by **gap type**:
155
156- **`missing`**: the required work is absent from the code entirely.
157- **`partial`**: the work exists but does not yet fully satisfy the requirement /
158 acceptance criterion / plan decision.
159- **`contradicts`**: the code does something that conflicts with stated intent or a
160 constitution MUST principle.
161- **`unrequested`**: the code contains work not called for by the spec, plan, or tasks
162 (surfaced for awareness — converge does **not** delete code, it only appends a task to
163 review/justify or remove it).
164
165Each `Finding` records: a stable id, the `source-ref` it traces to, the `gap-type`, a
166severity, and a short human-readable description with the evidence (the file/area observed).
167
168**Edge cases:**
169
170- **Little or no code yet**: treat the entire specified scope as `missing` remaining work
171 rather than failing.
172- **Nothing remains**: produce zero findings and follow the converged branch in Step 7.
173
174### 5. Assign Severity
175
176- **CRITICAL**: violates a constitution MUST principle, or a `missing`/`contradicts` gap
177 that blocks baseline functionality of a P1 user story.
178- **HIGH**: a `missing` or `partial` gap on a core functional requirement or acceptance
179 criterion.
180- **MEDIUM**: a `partial` gap on a secondary requirement, or an `unrequested` addition with
181 unclear justification.
182- **LOW**: minor partial gaps, polish, or low-risk `unrequested` additions.
183
184### 6. Present the In-Session Findings Summary
185
186Before appending anything, output a compact, severity-graded summary (no file writes yet):
187
188## Convergence Findings
189
190| ID | Gap Type | Severity | Source | Evidence | Remaining Work |
191| --- | -------- | -------- | ------ | --------------------------------------------------------------------------------- | --------------------------- |
192| F1 | missing | HIGH | FR-008 | Example: no append-only guard detected in path/to/module.py when writing tasks.md | Add append-only enforcement |
193
194**Summary metrics:**
195
196- Requirements / acceptance criteria checked
197- Plan decisions checked
198- Constitution principles checked (or "skipped — template")
199- Findings by gap type (missing / partial / contradicts / unrequested)
200- Findings by severity
201
202### 7. Append Convergence Tasks (or report converged)
203
204**If there are one or more actionable findings** (`tasks_appended` outcome):
205
206Append to the **end** of `tasks.md`, per the append contract:
207
2081. Scan all existing task IDs; let `M` be the maximum. Determine the next phase number `N`
209 (highest existing phase + 1).
2102. Write a single new section header `## Phase N: Convergence`.
2113. Emit one checklist item per actionable finding, ordered CRITICAL/HIGH first, assigning
212 zero-padded IDs `T{M+1:03d}, T{M+2:03d}, …`:
213
214 ```markdown
215 - [ ] T042 <imperative description> per <source-ref> (<gap-type>)
216 ```
217
218 `<source-ref>` traces the task to its origin: e.g. `FR-003`, `SC-002`,
219 `US1/AC2`, `plan: storage decision`, `Constitution II`.
220
221 `<gap-type>` is one of `missing`, `partial`, `contradicts`, `unrequested`.
222
223 Constitution-violation tasks MUST be emitted first and described as
224 `CRITICAL`.
225
2264. Never reuse or renumber existing IDs. If a prior Convergence phase exists, add a new,
227 separately-numbered one below it — do not touch the old one.
228
229**If there are no actionable findings** (`converged` outcome):
230
231- Do **not** modify `tasks.md` at all — no empty phase header.
232- Report: **"✅ Converged — the implementation satisfies the spec, plan, and tasks."**
233- Include the summary counts of what was checked.
234
235### 8. Provide Next Actions (Handoff)
236
237- On `tasks_appended`: state how many tasks were appended under which phase, and recommend
238 running `/speckit-implement` to complete them; note that a follow-up converge
239 run will find fewer or no remaining items.
240- On `converged`: recommend proceeding to review / opening a PR. No further implement pass
241 is needed for this feature's specified scope.
242
243### 9. Check for extension hooks
244
245After producing the result, check if `.specify/extensions.yml` exists in the project root.
246
247- If it exists, read it and look for entries under the `hooks.after_converge` key
248- If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
249- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
250- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
251 - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
252 - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
253- Report the convergence outcome (`converged` or `tasks_appended`) in-session before listing
254 any hooks, so users can decide whether to run optional follow-up commands.
255- When constructing command invocations from hook command names, replace dots (`.`) with hyphens (`-`). For example, `speckit.git.commit` → `/speckit-git-commit`.
256- For each executable hook, output the following based on its `optional` flag:
257 - **Optional hook** (`optional: true`):
258
259 ```text
260 ## Extension Hooks
261
262 **Optional Hook**: {extension}
263 Command: `/{command}`
264 Description: {description}
265
266 Prompt: {prompt}
267 To execute: `/{command}`
268 ```
269
270 - **Mandatory hook** (`optional: false`):
271
272 ```text
273 ## Extension Hooks
274
275 **Automatic Hook**: {extension}
276 Executing: `/{command}`
277 EXECUTE_COMMAND: {command}
278 ```
279
280 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 `{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.
281
282- If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently