speckit-converge

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

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/damian-garces/spec-driven-development --skill speckit-converge-damian-garces
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/damian-garces/spec-driven-development/tree/main/spec-driven-project/.claude/skills/speckit-converge
Command: npx skills add https://github.com/damian-garces/spec-driven-development --skill speckit-converge-damian-garces

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running an implementation pass in a Spec-Driven Development workflow, it is hard to know whether the code actually satisfies everything the spec, plan, and tasks demanded. This Skill closes that gap by auditing the current codebase against the feature artifacts and appending any unbuilt or incomplete work as new traceable tasks. ## 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 work. - Severity Grading: Ranks findings CRITICAL through LOW, treating constitution MUST-principle violations as the highest severity. - Append-Only Task Generation: Appends a new numbered Convergence phase to tasks.md without modifying existing tasks, spec, plan, or code. - Use Case: After running /speckit-implement on a feature, run this Skill to verify the implementation covers every functional requirement and acceptance criterion, then hand the appended tasks back to /speckit-implement. ## Quick Start Ask the agent to run the speckit-converge skill to check the current codebase against the feature 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 verify my code matches the spec in spec-kit?

Run the speckit-converge skill after /speckit-implement. It reads spec.md, plan.md, and tasks.md as the source of intent, inspects the code in scope, and appends any missing or partial work as new tasks to tasks.md.

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

Run it only after /speckit-tasks has produced a complete tasks.md and /speckit-implement has executed on it. It is a post-implementation audit, not a planning or diff tool.

Does speckit-converge modify my existing tasks or code?

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

What happens if the codebase already satisfies the spec?

The skill leaves tasks.md byte-for-byte unchanged and reports a converged result with counts of requirements, plan decisions, and constitution principles checked. It then recommends proceeding to review or opening a PR.

What are the prerequisites for running speckit-converge?

The project needs the spec-kit structure with a .specify directory, and the feature directory must contain spec.md, plan.md, and tasks.md. Missing artifacts cause the skill to stop and name the prerequisite command to run.