drillnowlisted

# /drillnow — clear the top blocker, now Where `/roundnext` sweeps the whole queue (breadth), `/drillnow` picks the **single highest-priority blocked item** and spends the turn actually trying to clear it (depth). A drill ends in exactly one of two states: the blocker is gone and the work has started, or the blocker is *proven* uncllearable right now and the queue is re-prioritized around that proof. "Still blocked, unchanged" is not a valid exit. ## Procedure **1. Target selection** — load board truth (`board_state_get` or `state.json`) and pick the highest-priority `blocked: true` planned item. Priority = board order unless a rationale says otherwise; skip items whose blocker is a *user decision gate* (those belong to the decisions panel, not to drilling — verify the panel entry exists, then take the next candidate). Announce the target in one line. **2. Blocker decomposition** — restate the blocker as a concrete condition ("what exactly must become true?"), then split it into parts by who/what can move each: this-side-doable / other-party / environment / time. Recorded `blockReason`s are often coarser than reality — decomposition routinely reveals a this-side-doable part nobody registered. **3. Active clearing attempts** (in escalating order of cost; stop at first success): - **Re-verify** — is the blocker already gone? (The dependency may have shipped, the precondition met by unrelated work.) - **This-side prerequisite work** — execute the doable parts now (col