weekly-capacity-reviewlisted

# Weekly Capacity Review A repeatable procedure for the platform team's weekly capacity review meeting. A future agent can run this job from this file alone; the source runbook is not needed in context. ## When to use - The user asks to prepare, run, or record the weekly capacity review. - The user asks to update the capacity sheet, flag engineer utilization, or triage the queue backlog for the coming weeks. - The review meeting needs a prepared agenda, computed flags, or recorded decisions. Do not use for incident response (separate runbook) or ad-hoc backlog grooming outside the review cycle. ## Evidence boundary (summary) - Source: internal runbook `notes.md` (English, Markdown, 1.1 KB) covering only the weekly capacity review procedure: inputs, steps, output, failure modes. - Not covered by the source: the incident-response runbook, actual sheet/backlog data, definitions of priority or age, the product owner's identity, and any tooling or storage locations. - Sensitivity: internal. Do not publish this package or its output publicly without authority; it contains no secrets but describes internal process. - Full inventory: `references/evidence-boundary.md`. ## Inputs 1. Team capacity sheet — slots per engineer per week. 2. Queue backlog report — items with age, size estimate, priority. 3. Previous week's review notes. ## Decision rules - D1 Utilization flag: `booked slots / total slots` per engineer; flag only when above 90% or below 40% for **three consecutive weeks