From claude-reliability
Suggests the highest-priority unblocked task to work on next using P0-P4 order, checking blockers, questions, and dependencies first.
npx claudepluginhub drmaciver/claude-reliability --plugin claude-reliability# Figuring Out What to Work On ## Quick Start If you just need something to work on: This picks a random work item from the highest-priority unblocked items. ## Decision Framework ### 1. Check for Blockers First Before picking new work, check if anything is blocked on you: Look for items you previously started that might be waiting. ### 2. Priority Order Work in priority order: - **P0 (Critical)**: Stop everything else, fix this now - **P1 (High)**: Should be done soon, before starting new features - **P2 (Medium)**: Normal work, the bulk of items - **P3 (Low)**: Nice to have, do...
/pickupLists ready tasks by priority, recommends or accepts task-id, shows details/context/learnings, then starts the task.
/readyLists unblocked issues ready for work, showing ID, title, priority, and type. Prompts to claim one and start work atomically via claim tool.
/suggestProvides opinionated recommendations for what to work on next in the current project, suggesting prioritized tasks or improvements based on arguments.
/plan-weekGenerates a weekly plan with priorities, risks, and success criteria by analyzing workspace files, git history, and MCP sources like GitHub PRs/issues and Linear tasks, outputting structured Markdown.
Share bugs, ideas, or general feedback.
If you just need something to work on:
what_should_i_work_on
This picks a random work item from the highest-priority unblocked items.
Before picking new work, check if anything is blocked on you:
list_work_items(status="open", ready_only=true)
Look for items you previously started that might be waiting.
Work in priority order:
list_work_items(max_priority=1, ready_only=true) # Show P0 and P1 only
Items might be blocked on user questions:
get_question_blocked_work
If you can answer any of these yourself now (with context you've gained), do so with answer_question.
Some items unblock others. Prioritize items that are blocking other work:
get_work_item(id="...") # Check what items this one blocks
You do not need user guidance on priorities. The priority system (P0-P4) tells you what to work on. Use what_should_i_work_on and follow its suggestion.
Large backlogs are normal. Having many open tasks doesn't mean anything is wrong. Just work through them one at a time. Don't ask which subset to focus on - the priority system handles this.
Report genuine blockers. Use create_question only for things that actually block progress:
Don't use emergency_stop for "too much work". Emergency stop is for genuine blockers that prevent ANY progress. A large backlog is not a blocker.
list_work_items(status="open", ready_only=true) - See what's availablework_on(work_item_id="...") - Mark as in-progressget_work_item(id="...") - Read full description and notesadd_note(work_item_id="...", content="...") - Record progress/findingsupdate_work_item(id="...", status="complete") - Mark doneIf you're stuck on an item:
create_question(text="How should I handle X?")link_work_to_question(work_item_id, question_id)Don't spin on problems that need user input.
If list_work_items(ready_only=true) shows nothing:
get_question_blocked_work - maybe you can answer somelist_work_items(priority=4)