speckit-converge

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

1|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/IgorGanapolsky/Random-Timer --skill speckit-converge-igorganapolsky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/IgorGanapolsky/Random-Timer/tree/main/.cursor/skills/speckit-converge
Command: npx skills add https://github.com/IgorGanapolsky/Random-Timer --skill speckit-converge-igorganapolsky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running an implementation pass, teams often cannot tell 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. ## 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 work. - Severity Grading: Ranks findings CRITICAL through LOW, with constitution MUST-principle violations treated as highest severity. - Append-Only Task Generation: Appends a new Convergence phase with zero-padded task IDs to tasks.md without modifying existing tasks, spec, plan, or code. - Use Case: After running /speckit-implement on a feature, run this Skill to verify nothing was missed; it either reports a clean converged state or appends remediation tasks for the next implement pass. ## Quick Start Ask the agent to run the speckit-converge skill to check the current feature's implementation against its 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 verify my code matches the spec after implementation?▼

Run the speckit-converge skill after /speckit-implement. It reads spec.md, plan.md, and tasks.md, inspects the code in scope, and either reports a converged state or appends remaining work as new tasks to tasks.md.

What does speckit-converge require before it can run?▼

It requires a spec-kit project structure with a .specify directory and existing spec.md, plan.md, and tasks.md files. If any artifact is missing, it stops and names the prerequisite command such as /speckit-specify, /speckit-plan, or /speckit-tasks.

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

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

How are convergence findings classified and prioritized?▼

Findings are classified as missing, partial, contradicts, or unrequested, then graded CRITICAL, HIGH, MEDIUM, or LOW. Constitution MUST-principle violations and gaps blocking P1 user stories are CRITICAL and emitted first.

What happens when the implementation already satisfies the spec?▼

The skill leaves tasks.md byte-for-byte unchanged and reports a converged result with summary counts of requirements, plan decisions, and constitution principles checked, recommending you proceed to review or open a PR.