Reconcile Plan

Make the thread's plan a faithful, executable expression of the spec that governs it. You read the spec and the thread's settled decisions, read the plan, repair the plan wherever the fix follows from those authorities, recheck what you changed, and hand any discrepancy that needs a fresh human decision to /emit-pending-decisions. You edit only the plan — its index and its task briefs; you never touch the spec or the decisions, you produce no separate report, and you offer no report-only, check-only, or approval variant selectable at invocation. Writing the corrected plan is where you stop — do not stage, commit, or push.

The one question you answer throughout: executed end to end, does this plan deliver what the spec's acceptance criteria promise, within the degrees of freedom the spec grants? A faithful plan covers every fixed point of the spec, invents no commitment the spec did not authorize, and is internally consistent enough to execute in order.

The plan artifact

The plan is a multi-file artifact: the index plan.md at the thread root plus one brief per task at plan-tasks/NN-<kebab-slug>.md (two-digit zero-padded ordinal, one file per task). The index carries the plan-level objective and context, a Source: line naming the artifact the plan was compiled from, a Global Constraints block copied verbatim from that source, and an ordered task list — and the index is authoritative for task count and order. Each brief carries its objective, input/context, steps, files modified, verification, acceptance criteria, and the Consumes: / Produces: hand-off lines.

Procedure

1. Resolve the thread. Work inside one thread root at docs/threads/<YYMMDDHHMMSSZ-slug>/. If cwd already sits inside a thread root, that is the thread. Two situations make a pending bundle physically impossible — .pending-decisions/ would live inside the very thread that failed to resolve — so in both, refuse in chat, write nothing, and end with Outcome: REFUSED — <reason>: no thread exists yet, or several thread roots exist and which is active is ambiguous (never silently pick the most recent stamp).

2. Load the authority and the target. Read the thread-root spec.md (the contract the plan must satisfy) and decisions.md (the settled decisions), plus any artifact the invocation explicitly points you at. Then read the plan end to end — the index first, then each brief in index order — your one editable target. Also resolve and read the artifact named by the index's Source: line; you need it to check the Global Constraints block. If no plan exists at the thread root, tell the user there is nothing to reconcile, write nothing, and end with Outcome: REFUSED — no plan to reconcile.

3. Check adherence. Run the check in ## The adherence check to locate every discrepancy between the plan and its authority, and to decide, for each, whether the fault lies in the plan or in the source.

4. Repair what the authority settles. Edit the index and/or briefs in place for every discrepancy whose fix follows directly from the spec and the decisions (see ## Repairing plan faults).