← ClaudeAtlas

prioritiselisted

Use when the user asks what to do next or how the queue is prioritised — "what's next", "what should I work on", "what's the priority", "what's blocked", "what's the most important thing", "what can you pick up". Ranks the ready/ briefs (dependency-aware: a brief stays blocked until its dependencies are done; briefs that unblock others rank higher) and shows the top of the queue with blocked / needs-you / unlock flags.
kmmwren/claude-tasks · ★ 0 · AI & Automation · score 70
Install: claude install-skill kmmwren/claude-tasks
# prioritise — rank the queue, dependency-aware Answer "what should I do next?" by ranking the `ready/` briefs. The score is transparent and generic: due urgency + importance + quick-win (low effort) + lead-time + a bonus for briefs that **unblock others**, plus any priority tag weights defined in `tasks.toml`. Dependencies are real: a brief lists `blockers:` (brief ids or external text) and/or `depends:<id>` tags. A dependency counts as met only once its target brief is `done`, so the queue self-unblocks as work completes. ```bash python3 "${CLAUDE_PLUGIN_ROOT}/scripts/prioritise.py" # ranked, all of ready/ python3 "${CLAUDE_PLUGIN_ROOT}/scripts/prioritise.py" --top 5 # top 5 python3 "${CLAUDE_PLUGIN_ROOT}/scripts/prioritise.py" --actionable # only what Claude can run now python3 "${CLAUDE_PLUGIN_ROOT}/scripts/prioritise.py" --json # machine-readable python3 "${CLAUDE_PLUGIN_ROOT}/scripts/prioritise.py" --context cloud # skip requires-local / requires-repo ``` The script resolves the queue via `$CLAUDE_TASKS_DIR` → nearest `.tasks/` → `~/tasks`. ## How to use it - **"What should I do next?"** → run it (optionally `--top 5`), then state the top few back in your own words: id, title, why it's ranked there (due / importance / unblocks N), and whether it's actionable now or blocked / needs them. - **"What can you pick up?"** → `--actionable` (only `autonomy: full`, unblocked, runnable). This is also what an autonomous loop would call (`--