spec-kit-converge

Check finished work against what its change asked for, and turn every gap into a task.

Input: Optionally specify a change name. If omitted, infer from context or ask.

This skill changes no code, no spec.md and no plan.md. Its only write is appending a ## Phase N: Convergence section to tasks.md. When nothing remains, tasks.md stays byte for byte unchanged.

It judges the code as it stands against the artefacts, which are the sole source of intent, with FRAMEWORK.md as governing constraints. Ticked boxes, commit messages and the implementer's notes are claims, not evidence.

Why a fresh view

The session that implemented the work knows what it meant, so its own work reads as done. Where the agent can start a sub-agent with a fresh context (not a fork of the current session), have it make the assessment (steps 2 to 4), giving it only the change's directory, this skill's instructions and the project root. Do not explain the work to it, summarise the change, or tell it what you expect it to find: anything you add is the implementer's view. Where no fresh agent is available, make the assessment yourself and say so in the report.

Steps