speckit-converge

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

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/tjsasakifln/extra-cli --skill speckit-converge-tjsasakifln
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/tjsasakifln/extra-cli/tree/main/.grok/skills/speckit-converge
Command: npx skills add https://github.com/tjsasakifln/extra-cli --skill speckit-converge-tjsasakifln

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 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 it. ## Core Features & Use Cases - Gap Assessment: Reads spec.md, plan.md, and tasks.md as the sole source of intent and classifies findings as missing, partial, contradicts, or unrequested work. - Severity Grading: Ranks findings CRITICAL through LOW, with constitution MUST violations treated as the highest severity. - Append-Only Task Generation: Appends a new numbered Convergence phase to tasks.md with zero-padded task IDs, never rewriting or renumbering existing tasks. - Extension Hooks: Supports optional and mandatory before/after converge hooks defined in .specify/extensions.yml. - Use Case: After /speckit-implement finishes, run converge to verify FR-008 is actually enforced in code; if not, a new task like "T042 Add append-only enforcement per FR-008 (missing)" is appended for the next implement pass. ## Quick Start Ask the agent to run the speckit-converge skill on the current feature to check whether the code satisfies the spec and append any remaining tasks.

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 code matches the spec after implementation?▼

Run the converge command after /speckit-implement. It reads spec.md, plan.md, and tasks.md as the source of intent, inspects the code in scope, and appends any remaining work as new tasks to tasks.md.

How to find missing requirements in a spec-kit feature?▼

Converge builds an intent inventory from functional requirements, success criteria, acceptance scenarios, and plan decisions, then inspects the code for gaps. Each gap becomes a finding classified as missing, partial, contradicts, or unrequested.

Does speckit-converge modify existing tasks or code?▼

No. It is strictly append-only: it adds a new Convergence phase to the end of tasks.md and never rewrites, renumbers, or deletes existing tasks, nor touches spec.md, plan.md, or application code.

What happens when the codebase already satisfies the spec?▼

Converge 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.

When should I run 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 clear message naming the prerequisite command if any is missing.