speckit-converge

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

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Argoss84/Kando-Caracter-sheet-generator --skill speckit-converge-argoss84
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/Argoss84/Kando-Caracter-sheet-generator/tree/main/.cursor/skills/speckit-converge
Command: npx skills add https://github.com/Argoss84/Kando-Caracter-sheet-generator --skill speckit-converge-argoss84

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running an implementation pass in a Spec Kit project, 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 unfinished 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, inspects the code in scope, and classifies findings as missing, partial, contradicts, or unrequested. - Severity Grading: Ranks findings CRITICAL through LOW, with constitution MUST violations treated as the highest severity. - Append-Only Task Generation: Appends a new "Phase N: Convergence" section to tasks.md with zero-padded task IDs, never rewriting or renumbering existing tasks. - Use Case: After running /speckit-implement on a feature, run converge to discover that an acceptance scenario from US2 is only partially implemented, then let /speckit-implement complete the newly appended tasks. ## Quick Start Ask the agent to run the speckit-converge skill to check the current feature 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 /speckit-implement. It reads spec.md, plan.md, and tasks.md, inspects the code in scope, and appends any remaining work as new tasks to tasks.md for another implement pass.

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 is a post-implementation audit step, not a planning or task-generation tool.

Does speckit-converge modify my existing tasks or code?▼

No. It is strictly append-only: it adds a new Convergence phase section 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 command leaves tasks.md byte-for-byte unchanged and reports a converged result with summary counts of what was checked. It then recommends proceeding to review or opening a pull request.

Why does speckit-converge stop with a missing artifact error?▼

It requires spec.md, plan.md, and tasks.md to exist in the feature directory. If any is missing, it stops and names the prerequisite command to run: /speckit-specify, /speckit-plan, or /speckit-tasks.