re0-upgrade
Bring your installed paperthin skills up to the full current catalog in one step: retire…
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,
$ npx -y skills add LilMGenius/paperthin --skill nba --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/nbaContext preview
The summary Claude sees to decide when to auto-load this skill.
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,
name: nba description: "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 state, not from vibes.
`nba` is the manual re-entry point for a stalled cycle. It reads the current state and returns one action: the cheapest move that clears the binding constraint. It does not execute the action and it does not offer a menu, because a menu recreates the paralysis it exists to resolve.
1. Read the live cycle state: plan gates, re0-memo anti-patterns, priority notes, recent git/file changes, QA evidence, and the current workflow phase. 2. Locate the project in the cycle: FRAME, BUILD, DRIVE, RE0-MEMO, HATE, RE0-WORK, BUILD AGAIN, or SHIP. 3. Diagnose the blank-out cause: too many open threads, lost thread, unnamed blocker, closed-loop fatigue, avoidance of the hard step, or a phase that is already done. 4. Return one action: the cheapest move that clears the most. It may name the right skill for the human to fire, the external input needed, the first nail to test, or the phase transition that is already due. 5. Frame it as: where you are, next best action, why now, and done when.
Before finishing:
1. The recommendation cites the state it read. 2. There is exactly one next action. 3. The action has a clear "done when" observable. 4. A reader can tell why this action beats the other visible options.
Turning old engineering wisdom into reflexes your agent reaches for on its own. On any agent | Claude Code, Codex, OpenCode, Antigravity, Copilot, Cursor, Grok-Build, Pi, Hermes, OpenClaw, etc.
Repo: LilMGenius/paperthin
Bring your installed paperthin skills up to the full current catalog in one step: retire…
Audit and consolidate a fact that's scattered across places into one canonical source, after…
Rebuild the human's lost context on a project from live state, in plain language: what needs…
Run repeated build -> QA -> re0-memo -> re0-work cycles while preserving learning and letting…
Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns,…
Open a paperthin iteration's casebook before re0-loop's first turn — seeded with real content…