speckit-converge

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

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/speeddesigns/cvusd-calendars --skill speckit-converge-speeddesigns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/speeddesigns/cvusd-calendars/tree/main/.agents/skills/speckit-converge
Command: npx skills add https://github.com/speeddesigns/cvusd-calendars --skill speckit-converge-speeddesigns

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 those artifacts and appending any unfinished work as new, traceable tasks so the implement step can finish the job. ## Core Features & Use Cases - Gap Assessment: Reads spec.md, plan.md, and tasks.md as the source of intent, inspects the in-scope code, and classifies findings as missing, partial, contradicts, or unrequested. - Severity Grading: Ranks findings CRITICAL through LOW, treating constitution MUST violations as the highest severity. - Append-Only Task Generation: Appends a new numbered Convergence phase to tasks.md with zero-padded task IDs, never rewriting or renumbering existing tasks. - Use Case: After running the implement command on a feature, run converge to discover that an acceptance criterion (e.g., an append-only guard) was never built; it appends a task like "T042 Add append-only enforcement per FR-008 (missing)" for the next implement pass. ## 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 command after the implement step. It reads spec.md, plan.md, and tasks.md, inspects the in-scope code, and reports findings classified as missing, partial, contradicts, or unrequested, then appends remaining work as new tasks.

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

Run it only after speckit-tasks has produced a complete tasks.md and speckit-implement has executed on it. Converge assesses the present state of the code against the artifacts; it is not a diff tool and does not use git history.

Does speckit-converge modify my existing tasks or code?

No. It is strictly append-only: its only write is a new Convergence phase section at the end of tasks.md. It never rewrites, renumbers, or deletes existing tasks, never touches spec.md or plan.md, and never modifies application code.

What happens if converge finds no remaining work?

It leaves tasks.md byte-for-byte unchanged and reports a converged result with summary counts of what was checked. The recommended next step is code review or opening a pull request rather than another implement pass.

What project structure does speckit-converge require?

It requires a spec-kit project with a .specify directory containing the feature's spec.md, plan.md, and tasks.md, plus optionally .specify/memory/constitution.md and .specify/extensions.yml for hooks. Missing artifacts stop execution with a message naming the prerequisite command.