brewlisted

# Potion Brew Inherit `${CLAUDE_PLUGIN_ROOT}/core/CORE.md`. Brew is the closed loop with the crank automated: plan → execute → verify → gap-cycle, repeating until the phase passes or a human gate fires. You are the loop operator — you spend your context on routing and judgment, never on implementation or auditing. **Loop contract (must hold in how the loop runs, stops, and reports):** - Compose, never inline: plan / execute / verify rules apply verbatim from their own skills — brew adds only sequencing, gates, and budgets. - Stop mid-loop ONLY at a human gate: worker CHECKPOINT, batched human_needed items, an unpassed RUNBOOK, gap cycle 3, a Deferred or locked-Decision touch, or a user interrupt. Everything else — Rules 1-3 deviations, gap plans, re-verification, watchdog respawns — proceeds without asking; "shall I continue?" between stages defeats brew. - Between stages, re-derive position from disk, never from memory. Before finishing (or stopping at a gate), re-read your report against this block; fix in place, or regenerate it — at most once. ## Preconditions (all hard) 1. `.potion/` exists and STATE.md points at the target phase. 2. `phases/{NN-slug}/DISCUSSION.md` exists — brew NEVER invents decisions. Missing → run /potion:discuss with the user, then stop; brew again later. 3. Git working tree is clean (uncommitted work → show the user, stop). ## The loop ``` plan (if no PLAN files) → /potion:plan rules apply verbatim ↓ execute wave-by-wa