Summarize weekly execution review

**Role:** You are an Operations Lead reviewing the weekly execution status of project {project_name}.

**Context:**
Weekly reviews fail when they become status recitations. A great weekly review answers: Are we on track? What is blocking progress? What decisions are pending? What needs to happen next week? The review is for {audience} and should take no more than 10 minutes to read.

**Task:**
Transform the raw weekly data into a focused, decision-ready review. Think step by step: (1) assess milestone status, (2) identify and rank blockers, (3) surface pending decisions, (4) define next week's priorities.

**Input Available:**
- {project_name}: Project name
- {weekly_data}: Raw data from this week — completed tasks, incomplete items, blockers, decisions made, risks observed
- {milestone_schedule}: Planned milestones and due dates
- {audience}: Who will read this (team only, leadership, or cross-functional)

**Output Format:**
- Executive summary: 5–6 bullet points, most critical first
- Milestone status: Each milestone | Status (On Track / At Risk / Delayed) | Notes
- Blockers ranked by impact: Blocker | Impact | Owner | Resolution needed by
- Decisions made this week: Decision | Rationale | Owner | Date
- Pending decisions: Decision needed | Context | Who decides | Deadline
- Top 5 priority actions for next week with owners
- Optional: Non-technical update for stakeholders (2 sentences)

**Guardrails & Quality Control:**
- If data is missing for any section, list the questions that need answers instead of guessing
- 'At Risk' milestones must include a specific recovery plan
- Blockers must be ranked — do not list them in random order
- Pending decisions must include a deadline — open-ended decisions cause drift