speckit-converge

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

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/Omkar-code-mur/Job-Radar --skill speckit-converge-omkar-code-mur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/Omkar-code-mur/Job-Radar/tree/main/Spec-it_job-Radar/.github/skills/speckit-converge
Command: npx skills add https://github.com/Omkar-code-mur/Job-Radar --skill speckit-converge-omkar-code-mur

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 so the implement step can finish the job. ## 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 discover that FR-008's append-only guard was never built; it appends a task like "T042 Add append-only enforcement per FR-008 (missing)" so the next implement pass completes it. ## Quick Start Ask the agent 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 graded by severity before appending remaining work to tasks.md.

How to add missing tasks to tasks.md after implementation?

The converge command appends a new "Phase N: Convergence" section to the end of tasks.md with one checklist item per finding, using zero-padded IDs continuing from the highest existing task number. It never rewrites or renumbers existing tasks.

Does speckit-converge modify spec.md or application code?

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 when the codebase 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. It then recommends proceeding to review or opening a PR.

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 the spec-kit project structure with a .specify directory and stops with a clear message if spec, plan, or tasks files are missing.