speckit-converge

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

32|9|Updated Feb 2, 2024
One-click install
npx skills add https://github.com/Esri/arcgis-gitops --skill speckit-converge-esri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/Esri/arcgis-gitops/tree/main/.github/skills/speckit-converge
Command: npx skills add https://github.com/Esri/arcgis-gitops --skill speckit-converge-esri

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 unfinished 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 and classifies findings as missing, partial, contradicts, or unrequested, with severity levels from CRITICAL to LOW. - Append-Only Task Generation: Adds a new "Phase N: Convergence" section to tasks.md with zero-padded task IDs traceable to requirements (e.g., FR-003, US1/AC2), never modifying existing tasks or code. - Constitution Enforcement: Treats violations of MUST principles in .specify/memory/constitution.md as the highest-severity findings. - Use Case: After running /speckit-implement on a feature, run this Skill to verify nothing was missed; it either reports "Converged" or appends the remaining tasks so /speckit-implement can finish them. ## 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 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 appends a new "Phase N: Convergence" section at the end of tasks.md with zero-padded IDs continuing from the highest existing task ID. 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. It requires a spec-kit project structure with a .specify/ directory and will stop with a clear message if spec.md, plan.md, or tasks.md is missing.

Does speckit-converge modify my application code or spec files?

No. Its only write operation 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 if the codebase already satisfies the spec?

The skill leaves tasks.md byte-for-byte unchanged and reports "Converged — the implementation satisfies the spec, plan, and tasks," along with counts of requirements, plan decisions, and constitution principles checked.