Read the live cycle state and return the single highest-leverage next best action, not a menu. Use when a project is between phases, the author asks what to do next, too many valid threads are open, or the work needs re-entry into frame, build, drive, re0-memo, hate, re0-work, or ship.
Use nba to read this project's current state and recommend one next best action without executing it. Cite the evidence behind the choice and explain where we are, why this action matters now, and what observable result would mean it is done.
Required inputs
Provide access to the project's current plan, priority notes, recent changes, and available QA or workflow evidence.
Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗
SKILL.md
name: nbadescription: "Read the live cycle state and return the single highest-leverage next best action, not a menu. Use when a project is between phases, the author asks what to do next, too many valid threads are open, or the work needs re-entry into frame, build, drive, re0-memo, hate, re0-work, or ship."
Find the next best action from live cycle state.
Goal
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.
Workflow
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.
Locate the project in the cycle: FRAME, BUILD, DRIVE, RE0-MEMO, HATE, RE0-WORK, BUILD AGAIN, or SHIP.
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.
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.
Frame it as: where you are, next best action, why now, and done when.
Rules
One action, not a checklist.
State-grounded, never generic. Cite the gate, doc, evidence, or file state that drives the pick.
Return the avoided move, not the easy busywork.
If no outside truth is entering, the next action is external input, not another internal lap.
If the gate is already met, the action is to move phase or ship, not add another surface.
Read-only on the project. nba recommends; it does not execute.
Do not auto-invoke user-only skills. Tell the human when one is the next move.
Verification
Before finishing:
The recommendation cites the state it read.
There is exactly one next action.
The action has a clear "done when" observable.
A reader can tell why this action beats the other visible options.