speckit-converge

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

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/lluisfont/clickup-reporting --skill speckit-converge-lluisfont
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/lluisfont/clickup-reporting/tree/main/.agents/skills/speckit-converge
Command: npx skills add https://github.com/lluisfont/clickup-reporting --skill speckit-converge-lluisfont

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After an implementation pass, teams often cannot tell whether the code actually satisfies the feature's spec, plan, and tasks. This Skill closes that gap by auditing the current codebase against the Spec Kit 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. - Severity Grading: Ranks findings CRITICAL through LOW, treating constitution MUST violations 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. - Use Case: After running speckit-implement on a feature, run this Skill to verify the implementation covers every functional requirement and acceptance criterion, then hand the appended tasks back to speckit-implement. ## Quick Start Ask the agent to run the speckit-converge skill to check the current feature implementation against its spec 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 verify my code matches a Spec Kit feature spec?

Run the speckit-converge skill after speckit-implement has completed. It reads spec.md, plan.md, and tasks.md, inspects the code in scope, and appends any remaining work as new tasks to tasks.md.

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 is a post-implementation audit step, not a planning or generation step.

Does speckit-converge modify my existing tasks or code?

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

What happens if the implementation already satisfies the spec?

The skill leaves tasks.md byte-for-byte unchanged and reports a converged result with summary counts of the requirements, plan decisions, and constitution principles checked.

What are the limitations of the convergence assessment?

It is not a diff tool and does not use git history or branch comparison; it only assesses the present state of code against the artifacts. It also bounds its scope to files and concepts named in the spec, plan, and tasks.