speckit-converge

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

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Powerworks/Underwriting --skill speckit-converge-powerworks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/Powerworks/Underwriting/tree/main/.claude/skills/speckit-converge
Command: npx skills add https://github.com/Powerworks/Underwriting --skill speckit-converge-powerworks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After an implementation pass, it is hard to know whether the code actually satisfies everything the feature's spec, plan, and tasks promised. This Skill closes that gap by auditing the current codebase against those artifacts and appending any unbuilt or incomplete 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 with severity levels. - 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. - Constitution Enforcement: Treats violations of MUST principles in .specify/memory/constitution.md as CRITICAL findings requiring remediation tasks. - Use Case: After running /speckit-implement on a feature, run this Skill to discover that FR-008's append-only guard was never built; it appends a HIGH-severity task so /speckit-implement can finish the work. ## 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 as the source of intent, inspects the code in scope, and reports findings classified as missing, partial, contradicts, or unrequested.

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

The converge command is append-only: it adds a new "Phase N: Convergence" section at the end of tasks.md with zero-padded IDs continuing from the highest existing task number. It never rewrites, renumbers, 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 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 application code or spec files?▼

No. Its only write is appending a Convergence phase to tasks.md. It never modifies spec.md, plan.md, or any application code; completing the 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 phase header and reports a converged result with summary counts of requirements, plan decisions, and constitution principles checked.