my-distilled-skilllisted

# my-distilled-skill # Weekly Capacity Review ## When to use - Running, preparing, or auditing the team's weekly capacity review. - Calculating engineer utilization from a capacity sheet. - Prioritizing and bucketing a queue backlog into committed, candidate, or parked work. - Resolving missing-input or priority-dispute situations during a review. - Not for incident response (covered by a separate runbook) or sprint planning. ## Inputs (collect by Thursday 12:00) 1. Team capacity sheet: booked slots per engineer per week. 2. Queue backlog report: items with age, size estimate, and priority. 3. Previous week's review notes. If any input is missing, do not invent numbers. Mark the review partial and proceed with what exists. ## Procedure 1. Collect the three inputs above by Thursday 12:00. 2. Compute utilization per engineer: `booked slots / total slots`. Flag an engineer when utilization is above 90% or below 40% for three consecutive weeks (a single week above/below threshold is not a flag). 3. Rank backlog items by priority, then by age (oldest first within equal priority). 4. Bucket each item: - Committed: scheduled for next week. - Candidate: possible within the next two weeks. - Parked: no owner assigned. 5. Decide with the team. Move a candidate to committed only if both hold: - a slot is free for the owner, and - the owner agrees to take it. 6. Record all decisions in the review notes. 7. Open follow-ups for any parked item that has no owner. ##