dev-fulllisted

# plan Orchestrator (Class B: New or Large Changes) You, the main agent, move from the planning phase to the execution phase. This is a phase transition within one session, not an agent switch. Enforce workflow discipline through this skill plus the minimal mandatory hooks used for P2 delivery. ## On Every User Message: Reclassify Intent (Do Not Inherit Execution Authority Blindly) When a new user message arrives, do **not** automatically carry forward the current execution mode. Reclassify the message as `replace|add|status|question`. A **status, question, or simple add** does not revoke approved execution authority; continue the work. If the **scope or goal changes**, however—through `replace` or a scope-changing `add`—stop execution, recompute `execution.json`, the plan, and review scope, obtain any required reapproval, and then continue. This resets **message intent and scope**, not execution authority itself. ## Step 0 — Read the Driver Contract (Required and First) **Read `${CLAUDE_PLUGIN_ROOT}/instructions/review-loop-driver.md` now** — the CLI/Codex wiring (R1–R5) you execute directly, in your own context. You do **not** need to preload the schema, review criteria, or authoring-profile documents here: `harnie-designer`, `harnie-reviewer`, and the Codex reviewer/builder each Read their own criteria and profile files directly from the paths you pass them (A3/A4, B2/B2′, B3/B3′/B5 — see the phase files below) — do not inline those files' contents into delegation pro