speckit-converge

Run the speckit-converge command after /speckit-implement completes. It reads spec.md, plan.md, and tasks.md, inspects the code in scope, and appends each remaining gap as a new task under a Convergence phase in tasks.md.

It appends a single new section titled '## Phase N: Convergence' containing one checklist item per finding, with zero-padded IDs continuing from the highest existing task number. It never modifies, reorders, or deletes existing tasks, and leaves the file untouched when nothing remains.

Run it only after /speckit-tasks has produced a complete tasks.md and /speckit-implement has executed against it. It requires spec.md, plan.md, and tasks.md to exist and stops with a message naming the prerequisite command if any are missing.

No. Its only write operation is appending a Convergence phase to tasks.md. It never edits spec.md or plan.md and never creates or deletes application code; completing the appended tasks is the job of /speckit-implement.

Code violating a MUST principle in .specify/memory/constitution.md is classified as CRITICAL severity, the highest level. Constitution-violation tasks are emitted first in the appended phase, and if the constitution is an unfilled template the check is skipped gracefully.

The command reports a converged outcome, leaves tasks.md byte-for-byte unchanged with no empty phase header, and recommends proceeding to review or opening a pull request instead of running another implement pass.