speckit-converge

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

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/MagnoAlves1993/handy --skill speckit-converge-magnoalves1993
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/MagnoAlves1993/handy/tree/main/.github/skills/speckit-converge
Command: npx skills add https://github.com/MagnoAlves1993/handy --skill speckit-converge-magnoalves1993

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running an implementation pass, teams often cannot tell whether the code actually satisfies everything the specification, plan, and task list promised. This Skill closes that gap by auditing the current codebase against the spec-kit artifacts and appending any unfinished 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, with constitution MUST-principle violations treated as highest severity. - Append-Only Task Generation: Adds a new Convergence phase to tasks.md with zero-padded task IDs, never rewriting or renumbering existing tasks. - 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 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 reports findings graded by gap type and severity before appending remaining work to tasks.md.

When should I run speckit-converge in the SDD 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 diffing tool.

Does speckit-converge modify my existing tasks or code?

No. It is strictly append-only: it adds a new Convergence phase with new task IDs 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 code already satisfies the entire spec?

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

How does speckit-converge handle constitution violations?

Code violating a MUST principle in .specify/memory/constitution.md is treated as the highest-severity finding and produces a CRITICAL remediation task listed first. If the constitution is an unfilled template, those checks are skipped gracefully.