speckit-converge

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

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/guihocosta/getsemani-app --skill speckit-converge-guihocosta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/guihocosta/getsemani-app/tree/main/.claude/skills/speckit-converge
Command: npx skills add https://github.com/guihocosta/getsemani-app --skill speckit-converge-guihocosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running an implementation pass, teams often cannot tell whether the code actually satisfies everything the feature's spec, plan, and tasks demanded. This Skill closes that gap by auditing the current codebase against those artifacts and appending any unbuilt or incomplete work as new traceable tasks so the implement step can finish it. ## 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 grading from CRITICAL to LOW. - Append-Only Task Generation: Appends a new numbered Convergence phase to tasks.md with zero-padded task IDs, never rewriting or renumbering existing tasks, and leaves the file untouched when fully converged. - Constitution Enforcement: Treats violations of MUST principles in .specify/memory/constitution.md as the highest-severity findings and emits remediation tasks first. - Use Case: After /speckit-implement finishes, run this Skill to discover that FR-008's append-only guard was never built; it appends a HIGH-severity task to tasks.md so the next implement pass completes it. ## Quick Start Run the speckit-converge skill to check my current feature implementation against its spec, plan, and tasks 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.

How to add remaining work to tasks.md without rewriting existing tasks?▼

The converge command is append-only: it computes the next task IDs and phase number, then appends a new Convergence phase section at the end of tasks.md. It never renumbers, reorders, or deletes existing tasks.

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. If spec.md, plan.md, or tasks.md is missing, the command stops and names the prerequisite command to run first.

Does speckit-converge modify spec.md, plan.md, or application code?▼

No. Its only write is appending a Convergence phase to tasks.md. It never modifies spec.md or plan.md and never changes application code; completing appended tasks is the job of /speckit-implement.

What happens when the codebase already satisfies the spec?▼

The command leaves tasks.md byte-for-byte unchanged, with no empty Convergence header, and reports a converged result with summary counts of requirements, plan decisions, and constitution principles checked.

Why does converge report constitution violations as critical findings?▼

The project constitution at .specify/memory/constitution.md is treated as non-negotiable, so code violating a MUST principle is the highest-severity finding. If the constitution is an unfilled template, those checks are skipped gracefully.