yolo-queue: escalation policy — debate-team-fast on every item, not just blockers

2bde4b70b702c65ed3fac40fb58874f0ccd7db27 · 2026-05-25 20:27:00 -0700 · Steve Abrams

Files touched

M .yolo-queue.md

Diff

commit 2bde4b70b702c65ed3fac40fb58874f0ccd7db27
Author: Steve Abrams <steve@designerwallcoverings.com>
Date:   Mon May 25 20:27:00 2026 -0700

    yolo-queue: escalation policy — debate-team-fast on every item, not just blockers
---
 .yolo-queue.md | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/.yolo-queue.md b/.yolo-queue.md
index eaedb2d..3bdbe18 100644
--- a/.yolo-queue.md
+++ b/.yolo-queue.md
@@ -140,15 +140,15 @@ never silently pause overnight.
 
 ## Escalation policy
 
-If any single item takes >10 min OR returns a real surprise (unexpected
-schema, missing file, ambiguous spec), DO NOT silently pause.
-
-Spawn debate-team-fast agent via the Agent tool with `subagent_type:
-"debate-team-fast"` and a prompt summarizing (1) what the task asked,
-(2) what's blocking, (3) two candidate paths forward. Paste the
-verdict as a `> NOTE` blockquote in this file under the item, then
-move to the NEXT unblocked item. Steve reviews escalations in the
-morning.
+**UPDATED 2026-05-25 (Steve directive)**: ALWAYS spawn debate-team-fast
+on every remaining item BEFORE editing, not just on blockers. Pass the
+item text + 2 candidate implementations + the relevant file paths/line
+numbers. Apply the consensus verdict, paste the synthesized digest as
+a `> NOTE` blockquote under the item, then commit + move on.
+
+If any single item still takes >10 min after the debate verdict OR the
+panel splits irreconcilably, paste the dissent into the NOTE and skip
+to the next item. Steve reviews splits in the morning.
 
 ## Cadence

← 26ab5d3 yolo-queue: SG-1..SG-4 ✓ attorney narrowings (moth/bird/scat · back to Wallco Ai · yolo-queue: SG-5 ✓ settlement-gate.test.js — 14 cases all PA 0f99287 →