speckit-converge

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After an implementation pass, 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's spec.md, plan.md, and tasks.md, then appending any unbuilt or incomplete 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 sole source of intent and classifies every finding as missing, partial, contradicts, or unrequested, with severity levels from CRITICAL to LOW. - Append-Only Task Generation: Appends a new "Phase N: Convergence" section to tasks.md with zero-padded task IDs traced to their source (FR-###, SC-###, US1/AC2, plan decisions, constitution principles), never rewriting existing tasks or touching application code. - 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 running /speckit-implement on a feature, run this Skill to verify nothing was missed; if gaps exist it appends tasks like "T042 Add append-only enforcement per FR-008 (missing)" so a follow-up implement pass completes them. ## Quick Start Ask the agent to run the speckit-converge skill to check the current implementation 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 check if my implementation matches the spec in spec-kit?▼

Run the speckit-converge command after /speckit-implement has completed. It reads spec.md, plan.md, and tasks.md as the source of intent, inspects the code in scope, and reports findings classified as missing, partial, contradicts, or unrequested.

What does speckit-converge do when it finds gaps in the code?▼

It appends a new "Phase N: Convergence" section to the end of tasks.md with one checklist task per finding, ordered CRITICAL and HIGH first. Each task gets a new zero-padded ID and traces back to its source requirement, such as FR-003 or US1/AC2.

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 run on it. It requires spec.md, plan.md, and tasks.md to exist, and stops with a message naming the prerequisite command if any are missing.

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

No. It is strictly append-only: it never rewrites, renumbers, or deletes existing tasks, never modifies spec.md or plan.md, and never changes application code. If everything is already satisfied, it leaves tasks.md byte-for-byte unchanged.

How does speckit-converge handle constitution violations?▼

Violations of MUST principles in .specify/memory/constitution.md are treated as CRITICAL severity findings, the highest level. Remediation tasks for these violations are emitted first in the appended Convergence phase. If the constitution is an unfilled template, the check is skipped gracefully.