Weekly Status Report

---
name: weekly-status-report
description: Turns your scattered notes, tickets, and numbers into a clear weekly update covering what got done, what's next, blockers, and the metrics that matter.
---

# Weekly Status Report

Use this when the user needs a weekly (or sprint) update for a manager, team, or client.

## Gather

Ask for, or pull from what the user shares: what was finished, what's in progress, what's
planned next, blockers, key numbers, and who will read it.

## Write it

```
# Weekly update — [team/project], week of [date]

**Summary:** [2 sentences: overall status and the one thing readers must know]
**Status:** On track / At risk / Off track

## Done this week
- [result, not activity: "Launched checkout v2", not "Worked on checkout"]

## Next week
- …

## Blockers and help needed
- [blocker] — needs [person/decision] by [date]

## Metrics
| Metric | This week | Last week | Target |
```

## Rules

- Lead with outcomes and impact, not effort.
- Be honest about risks early; don't hide bad news at the bottom.
- Numbers must come from the user's data. Mark missing ones as TBD.
- Keep it scannable: most readers spend under a minute on it.
- Match the audience: executives want the summary and risks; the team wants details.