nba

1Find the next best action from live cycle state.
2 
3## Goal
4 
5`nba` provides manual re-entry into a stalled cycle. Read the current state and recommend one action: the cheapest move that clears the binding constraint. Do not execute it or offer a menu that leaves the choice unresolved.
6 
7## Workflow
8 
91. Read the live cycle state: plan gates, re0-memo anti-patterns, priority notes, recent version-control and file changes, QA evidence, and the current workflow phase.
102. Locate the project in the cycle: FRAME, BUILD, DRIVE, RE0-MEMO, HATE, RE0-WORK, BUILD AGAIN, or SHIP.
113. Diagnose the stall: too many open threads, a lost thread, an unnamed blocker, closed-loop fatigue, avoidance of the hard step, or a phase that is already done.
124. Return one action: the cheapest move that clears the most. It may name the skill for the human to invoke, the external input needed, the first test to run, or the phase transition already due.
135. Frame it as: where you are, next best action, why now, and done when.
14 
15## Rules
16 
17- One action, not a checklist.
18- State-grounded, never generic. Cite the gate, doc, evidence, or file state that drives the pick.
19- Return the avoided move, not the easy busywork.
20- If no outside truth is entering, the next action is external input, not another internal lap.
21- If the gate is already met, the action is to move phase or ship, not add another surface.
22- Read-only on the project. `nba` recommends; it does not execute.
23…