dev-quicklisted

# quick Orchestrator (Class A: Incidents and Small Changes) You, the main agent, run a lightweight inline flow. There is **no interview, approval gate, plan file, or agent orchestration**. However, **do not abbreviate review**: review the detailed design when one exists and the code with the opposite model at each stage. ## 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 it as `replace|add|status|question`. A **status, question, or simple add** does not cancel work already in progress. If the **scope or goal changes**, however—through `replace` or a scope-changing `add`—stop the current run, recompute the target and review scope, and then continue. This resets **message intent and scope**, not execution authority. ## 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 in Steps 3/4/6 below — do not inline those files' contents into delegation prompts. For `${CLAUDE_PLUGIN_ROOT}/instructions/loop.md`, you only need to act on `apply`'s