Determines the next best step for a project based on its current state.
Install
mkdir -p .claude/skills/nba && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17549" && unzip -o skill.zip -d .claude/skills/nba && rm skill.zipInstalls to .claude/skills/nba
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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, retro, hate, re0-work, or ship.Key capabilities
- →Read live project cycle state
- →Locate project in its development phase
- →Diagnose causes of project stalls
- →Return a single highest-use next best action
- →Frame the action with context and completion criteria
How it works
It analyzes the current project state, including plan gates, git changes, and workflow phase, to identify the binding constraint. It then provides one actionable step to clear that constraint, explaining why it's the best move and what 'done' looks like.
Inputs & outputs
When to use nba
- →Resolving project stalls
- →Finding the next task after a hiatus
- →Clarifying development direction
About this skill
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
- Read the live cycle state: plan gates, retro anti-patterns, priority notes, recent git/file changes, QA evidence, and the current workflow phase.
- Locate the project in the cycle: FRAME, BUILD, DRIVE, RETRO, HATE, RE0-WORK, BUILD AGAIN, or SHIP.
- 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.
- 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.
- 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.
nbarecommends; 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.
When not to use it
- →When the user wants a menu of options instead of a single action
- →When the user wants to execute the action directly
- →When the user wants to add another surface to a project where the gate is already met
Limitations
- →Returns only one action, not a checklist
- →Does not execute the recommended action
- →Recommendations are state-grounded, not generic
How it compares
This skill provides a single, prioritized next action based on project state, specifically intended to resolve task paralysis, rather than offering multiple options or executing tasks directly.
Compared to similar skills
nba side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| nba (this skill) | 0 | 21d | No flags | Intermediate |
| archon | 9 | 8mo | Review | Intermediate |
| linear | 10 | 1mo | No flags | Beginner |
| zapier-workflows | 11 | 8mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by LowyShin
View all by LowyShin →You might also like
archon
coleam00
Interactive Archon integration for knowledge base and project management via REST API. On first use, asks for Archon host URL. Use when searching documentation, managing projects/tasks, or querying indexed knowledge. Provides RAG-powered semantic search, website crawling, document upload, hierarchical project/task management, and document versioning. Always try Archon first for external documentation and knowledge retrieval before using other sources.
linear
lobehub
Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.
zapier-workflows
davila7
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
attio-skill-generator
kesslerio
Generate use-case-specific Attio workflow skills from templates. Use when creating new skills for lead qualification, deal management, customer onboarding, or custom Attio workflows.
github-manage
matteocervelli
Manage operations concerning GitHub on behalf of user
cto-engineering-metrics
rinaldofesta
Expert methodology for defining, tracking, and interpreting engineering performance metrics including DORA, team health, productivity, and executive reporting.