---
name: weekly-business-review-generator
description: Generate a weekly business review or operations report that surfaces what changed, what is at risk, and what to do. Use this skill whenever a user needs a weekly business review, an ops report, a team status update, a WBR, or says 'write our weekly update', 'summarize the week for leadership', or 'build our WBR'. Trigger whenever recurring performance and status information needs to become a crisp, decision-oriented report.
---

# Weekly Business Review Generator

## What this does and why it matters
Weekly reports usually become a data dump no one reads or a vague "things are going well". This skill turns the week's metrics and activity into a crisp review that leads with what changed and what needs a decision, so leadership spends its attention on the few things that matter rather than scrolling numbers.

## Inputs to gather
1. The metrics or KPIs tracked and this week's values (and prior period for comparison).
2. Key activity, wins, and issues from the week.
3. What is at risk or blocked and needs a decision.
4. The audience and what they care about.

## Method

### 1. Lead with the headline
Open with the two or three things leadership must know this week: a metric that moved meaningfully, a risk, a decision needed. Bury nothing important below the fold.

### 2. Report metrics with context
Every number gets a comparison (versus last period or target) and a one-line "why". A number with no context is noise; a number with a trend and a reason is information.

### 3. Separate signal from status
Distinguish what changed and matters from routine status. Flat metrics need a line; moving metrics need explanation.

### 4. Surface risks and asks clearly
What is at risk, what is blocked, and specifically what is needed from the reader, so the report drives action rather than just informing.

### 5. Keep wins honest and brief
Note real wins without inflating them, and keep the whole thing skimmable.

## Output format
ALWAYS use:

# Weekly Business Review | [Week of]
## Headline (2 to 3 must-knows)
## Metrics (metric | this week | vs prior/target | why it moved)
## Wins
## Risks and blockers (and the decision or help needed)
## Priorities for next week

## Anti-patterns to avoid
- A wall of numbers with no context or "why".
- "Everything is fine" with no substance.
- Burying a real risk under routine status.
- No clear asks, so leadership cannot help.

## Example
A WBR opens with three must-knows including a dip in reply rates, reports each KPI against target with a one-line cause, flags a hiring blocker with the specific approval needed, and lists next week's three priorities.