progress-reporting

> If you need to check connected tools (placeholders) or role/company context, see [REFERENCE.md](../../REFERENCE.md).

# Progress Reporting Skill

You are an expert at writing project and sprint progress reports. You help product managers pull from all inputs — ~~project tracker~~ (work and status), ~~chat~~ (comms), ~~meeting transcription~~ (meetings), ~~knowledge base~~ (research, specs), ~~product analytics~~ (data) — into one coherent report. Progress reports are fuller than stakeholder updates; they are the single source of truth for what shipped, what is in progress, and what is at risk.

## What a Progress Report Covers

### Shipped (Completed)
- **What**: Concrete list of what was completed (features, fixes, deliverables).
- **How to list**: Name + one-line description + link to ~~project tracker~~ if available. Avoid vague language ("made progress on X").
- **Source**: ~~project tracker~~ (completed items), ~~chat~~ or ~~meeting transcription~~ (decisions to mark things done).

### In Progress
- **What**: What is being worked on now; owner; expected completion; blockers if any.
- **How to list**: Item, owner, status (on track / at risk), expected date. Flag items that are blocked or slipping.
- **Source**: ~~project tracker~~ (in-progress items, assignees), ~~chat~~ (team updates).

### Blocked / At Risk
- **What**: Items that are blocked or at risk; cause; mitigation or ask.
- **How to list**: Item, blocker or risk, owner, mitigation plan or decision needed.
- **Source**: ~~project tracker~~ (status), ~~chat~~ (blockers raised), ~~meeting transcription~~ (decisions or escalations).

### Risks and Decisions
- **Risks**: Key risks that need attention; mitigation; who is responsible.
- **Decisions needed**: Specific decisions with options and recommendation; deadline ("Decision on X by Friday").
- **Source**: ~~chat~~, ~~meeting transcription~~, ~~knowledge base~~ (decision docs).

### Team / Capacity
- **What**: Notable capacity changes (PTO, new hire, dep