review-queue

Use on every workspace.new_asks or review_item.added event, when writing the morning hit list, when Bryan asks what needs him or what his priorities are, and whenever he says the queue is wrong, stale

SKILL.md

GitHub

Review Queue

Bryan's Home review queue is the one place he looks to see what needs him. Team Lead owns it across every board (set 2026-10-05, restated 2026-10-16: "it's your responsibility to keep them that way").

The failure this skill exists to stop (2026-10-17): the queue showed school-tool asks at ranks 1–3 while goal #2 had two demo videos and a reply owed to a teammate filed nowhere, and the #1 goal's must-do (an email) sat only in the plan doc. Ranking what agents happen to file is not curation. Start from his goals, never from the queue.

1. Fill the queue from the goals down

This section is temporary. Remove it when leads file review items and keep them current without prompting. Until then, run this sweep every 2 hours, from the review-queue sweep row on the Team Lead board. For each of this week's top three goals, in plan order:

  • Ask its lead one question: "What is waiting on Bryan that is not filed as a review item?" Include things outside the board: a video to watch, a Slack or Gmail reply, a doc edit before it goes out, a PR only he can approve.
  • The lead files each one. If nobody owns it (a PR, an email he must send), file it on the Team Lead board yourself.
  • Anything in the hit list must also be a review item. Prose in the plan doc is invisible to him in the queue.
  • A top-three goal with nothing waiting gets that said in the hit list, so an empty section reads as checked, not skipped.

2. Rank strictly by goal order

  • Every item of goal N ranks above every item of goal N+1. Only a hard deadline inside 48 hours, or work stopped until he answers, moves an item up across goals. Say which.
  • Ranks 1–10 are only things that move this week's goals. Fleet tooling, design questions and nice-to-haves rank 20 and below, or not-this-week.
  • Re-rank the whole queue, not just the new item. A new ask can push everything below it.

3. Make each item readable on a phone

  • The headline is the ask in his words ("Watch the two demo videos"), not a task story ("Bryan can…"). If it isn't, ask the owner to revise_review_item.
  • Every item links the thing to look at. No link means he has to go find it.

4. Keep it current

  • Before each hit list, check every top-10 item is still open. He often does the thing outside the queue (an email sent, a call made). Close it or have the owner close it.
  • Ping the owner of any ask older than a day: drop it, update it, or keep it waiting.

Before you tell him the queue is right

Read ranks 1–10 against the goal list. Each of the top three goals has an item or a stated "nothing needed", and no item in the top 10 serves a goal below one that is missing.