speckit-converge

Assess codebase against spec, plan, and tasks, then append remaining work to tasks.md.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/eovipmak/unattended-iso --skill speckit-converge-eovipmak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/eovipmak/unattended-iso/tree/main/.commandcode/skills/speckit-converge
Command: npx skills add https://github.com/eovipmak/unattended-iso --skill speckit-converge-eovipmak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After an implementation pass, it is hard to know whether the code actually satisfies everything the feature's spec, plan, and tasks promised. This Skill closes that gap by auditing the current codebase against the spec-kit artifacts and appending any unbuilt or incomplete work as new, traceable tasks to tasks.md. ## Core Features & Use Cases - Gap Assessment: Reads spec.md, plan.md, and tasks.md as the source of intent and classifies findings as missing, partial, contradicts, or unrequested, with severity levels from CRITICAL to LOW. - Append-Only Task Generation: Appends a new Convergence phase to tasks.md with zero-padded task IDs traced to their source requirement, without modifying spec.md, plan.md, or existing tasks. - Constitution Enforcement: Treats violations of MUST principles in .specify/memory/constitution.md as the highest-severity findings. - Use Case: After running speckit-implement on a feature, run converge to verify nothing was missed; if gaps exist, new tasks are appended so a follow-up implement pass can finish them. ## Quick Start Ask the agent to run the speckit-converge skill to check the current feature's implementation against its spec and append any remaining work to tasks.md.

Frequently Asked Questions about speckit-converge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my implementation matches the spec in spec-kit?

Run the speckit-converge skill after speckit-implement. It reads spec.md, plan.md, and tasks.md, inspects the code in scope, and reports findings classified as missing, partial, contradicts, or unrequested with severity levels.

What does speckit-converge do when it finds gaps in the code?

It appends a new Convergence phase to the end of tasks.md with one checklist task per finding, ordered CRITICAL and HIGH first. Each task gets a new zero-padded ID and traces back to its source requirement such as FR-003 or US1/AC2.

Does speckit-converge modify spec.md or existing tasks?

No. It is strictly append-only: it never modifies spec.md or plan.md, never renumbers or deletes existing tasks, and never changes application code. If everything is satisfied, tasks.md is left byte-for-byte unchanged.

When should I run speckit-converge in the spec-kit workflow?

Run it only after speckit-tasks has produced a complete tasks.md and speckit-implement has executed on it. It requires a spec-kit project structure with a .specify directory and the feature's spec, plan, and tasks files present.

What happens if the code violates a constitution principle?

Constitution MUST violations are treated as CRITICAL findings, the highest severity. The corresponding remediation tasks are emitted first in the new Convergence phase. If the constitution file is an unfilled template, the check is skipped gracefully.