converge

User Input

You MUST consider the user input before proceeding (if not empty).

Goal

Close the gap between what a feature's specification, plan, and tasks call for and what the codebase currently implements. Read spec.md, plan.md, and tasks.md as the sole source of intent (with the constitution as governing constraints), assess the current state of the code, determine which requirements, acceptance criteria, plan decisions, and existing tasks are unmet, incomplete, or only partially satisfied, and append each piece of remaining work as a new, traceable task at the bottom of tasks.md so that /akka:implement can complete it. This command MUST run only after /akka:implement has run on the current tasks.md, and after /akka:tasks has produced a complete tasks.md.

This is not a diff tool and does not track changes. It assesses the present state of the code relative to the feature's artifacts — no git, no branch comparison, no history.

Operating Constraints

APPEND-ONLY, NEVER REWRITE: The command's only write is appending a new ## Phase N: Convergence section to tasks.md. It MUST NOT:

• modify spec.md or plan.md in any way;
• rewrite, renumber, reorder, or delete any existing task (including tasks from a prior Convergence phase);
• modify, create, or delete any application code — completing the appended tasks is the job of /akka:implement.

When the codebase already satisfies everything, the command MUST leave tasks.md byte-for-byte unchanged (no empty Convergence header) and report a clean result.

Constitution Authority: The project constitution (loaded via akka_sdd_constitution) is non-negotiable. Code that violates a MUST principle is the highest-severity finding and produces a corresponding remediation task. If the constitution is an unfilled template or unavailable, skip constitution checks gracefully rather than failing.

Execution Steps

1. Initialize Convergence Context