What problem does it solve? Ad-hoc notes about future work get lost or resurface without context, and most backlog tools present an ordering they cannot justify. This Skill records what, where, and why for each item, then answers "what's next" while naming exactly which criteria separated the list and which separated nothing. ## Core Features & Use Cases - Bidirectional backlog: Push an item with its repo, branch, and an explicit --why, or pull an ordered list of what to pick up next. - Honest ordering: Ranks by recorded blockers, unblock counts, branch match, then age, and states outright when age alone determined the order. - Local and shared scopes: Keeps a per-project local file or pushes to a shared team queue, falling back to local with exit code 2 when the shared backend is unreachable. - Use Case: A developer finishes a session, files "the picker stub has drifted from the real stream" with a reason, and weeks later asks what to work on next, receiving a ranked list with its ordering basis printed. ## Quick Start Ask the assistant to run /qbl with a note about something to remember, or run /qbl with no argument to see what to work on next.