nextlisted

Outcome to produce: one recommended next action, stated first, with a short reason and a realistic time range. Alternatives only when they are materially useful. Enter the next-step flow of the brotherme skill. Run the mechanical command `python3 "${CLAUDE_PLUGIN_ROOT}/tools/brothermode_cli.py" next --project-id <id>` (the packaged console script is `brothermode next`) and read its `next:` line and the `WHY:` reason beside it: the single ready task (dependency-satisfied per the protocol's own definition of that state), picked by highest priority and then whichever was added first as the tie break. Never answer from memory of this conversation, and never read CANVAS.md by hand, since CANVAS.md is a generated view, not the source of truth. A plugin install exports `${CLAUDE_PLUGIN_ROOT}` for skill and command content, so that path resolves on its own; on a clone install, where the variable is unset, run `python3 tools/brothermode_cli.py next --project-id <id>` instead, from the BrotherMode root (`~/.claude/skills/brothermode`). Either way, run it from the user's project folder so it reads that project's own records. Present that recommendation as exactly one next step, with its reason. Estimates follow the rules in references/forecasting.md: always ranges with a confidence level, never single numbers. When a decision from the user is what blocks progress, `/brothermode:status`'s Next step field says so before this skill would find any ready task at all; present that decision