speckit-converge

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

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/acarmonag/fullstack-devops-agent-aws-terraform --skill speckit-converge-acarmonag
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/acarmonag/fullstack-devops-agent-aws-terraform/tree/main/codebase/rdicidr-0.1.0/.claude/skills/speckit-converge
Command: npx skills add https://github.com/acarmonag/fullstack-devops-agent-aws-terraform --skill speckit-converge-acarmonag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running an implementation pass, teams often cannot tell whether the code actually satisfies everything the spec, plan, and tasks promised. 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 Detection and Classification: Finds missing, partial, contradicting, or unrequested work by comparing the intent inventory (requirements, acceptance criteria, plan decisions, constitution principles) against the actual code. - Append-Only Task Generation: Adds 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 everything is already satisfied. - Severity-Graded Findings Report: Presents an in-session table of findings graded CRITICAL through LOW, with constitution violations surfaced first. - Use Case: After running /speckit-implement on a feature, run this Skill to verify nothing from the spec was missed; it appends tasks like "T042 Add append-only guard per FR-008 (missing)" so the next implement pass completes the remaining work. ## Quick Start Ask the assistant to run the speckit-converge skill to check the current feature's 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 as the source of intent, inspects the current code, and appends any remaining work as new tasks to tasks.md.

How does speckit-converge handle gaps it finds in the code?▼

Each gap is classified as missing, partial, contradicts, or unrequested, assigned a severity from CRITICAL to LOW, and appended as a new checklist task under a numbered Convergence phase in tasks.md. Existing tasks are never rewritten or renumbered.

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 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 spec, plan, or application code?▼

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

What happens when the codebase already satisfies the spec?▼

The skill leaves tasks.md byte-for-byte unchanged and reports a converged result with counts of what was checked. It then recommends proceeding to review or opening a pull request instead of another implement pass.