Skip to content
AI & Agents
Skill

/nba

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,

BOOST
From plugin
paperthin
1.1k28 skills
Install
$ npx -y skills add LilMGenius/paperthin --skill nba --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/nba

Context 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,

SKILL.md

nba.SKILL.md
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.

Goal

`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.

Workflow

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.

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:

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.

Read more
Ships withpaperthin

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.

Get the whole plugin
Stats
1,130
Stars
113
Forks
Active
Maintenance
JavaScript
Language
MIT
License
7d ago
Last commit
3mo ago
Created
16h ago
Added

Repo: LilMGenius/paperthin

Other skills on paperthin.