---
name: progress-reporting
description: Structure project, sprint, or initiative progress reports. Use when writing progress reports that pull from work, comms, data, and research — what to include (shipped, in progress, blocked, risks, team), format by audience.
---

> 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, departure), handoffs, cross-team dependencies.
- **Source**: ~~chat~~, ~~meeting transcription~~, ~~project tracker~~ (assignments).

### Next Milestones
- **What**: What is coming next and when. Concrete and time-bound.
- **Source**: ~~project tracker~~ (upcoming milestones), ~~knowledge base~~ (roadmap or plan).

## Format by Audience

### Exec / Leadership
- **Length**: One page. Summary + status (G/Y/R) + shipped + key risks/decisions + next milestones.
- **Tone**: Outcomes and decisions; no task-level detail.
- **Pull**: ~~project tracker~~ (high-level status), ~~chat~~ (decisions), ~~product analytics~~ (if launch metrics matter).

### Product / Eng
- **Length**: 2–3 pages. Full shipped list, in-progress with owners, blocked/at risk, risks/decisions, next milestones.
- **Tone**: Enough detail to know what is done and what is blocked. Links to ~~project tracker~~.
- **Pull**: ~~project tracker~~, ~~chat~~, ~~meeting transcription~~, ~~knowledge base~~.

### Cross-Functional
- **Length**: 1–2 pages. What shipped that affects them; what is coming; what you need from them; decisions that impact them.
- **Tone**: Context-appropriate; focus on dependencies and handoffs.
- **Pull**: ~~project tracker~~, ~~chat~~, ~~knowledge base~~.

## Pulling from All Inputs

- **~~project tracker~~**: Completed items, in-progress items, assignees, blocked/at-risk status, milestones, dependencies
- **~~chat~~**: Team discussions, decisions, blockers, capacity notes
- **~~meeting transcription~~**: Meeting notes, decisions, action items
- **~~knowledge base~~**: Past progress reports, specs, goals, decision docs
- **~~product analytics~~** (optional): Key metrics for launched features or the initiative (usage, adoption) when the report is launch- or metrics-focused

Use comms, data, research, and teams together so the report is complete and authoritative for the period.

## Inputs from Tools

When writing a progress report:

- **~~project tracker~~**: Completed items, in-progress items, assignees, blocked/at-risk items, milestones, dependencies
- **~~chat~~**: Team discussions, decisions, blockers, capacity or handoff context
- **~~meeting transcription~~**: Meeting notes, discussion summaries, decisions and action items
- **~~knowledge base~~**: Past progress reports, specs, goals, decision documents
- **~~product analytics~~** (if connected and relevant): Key metrics for launched work or the initiative

If a tool is not connected, ask the user for that dimension (what shipped, what is blocked, key decisions, etc.). Use only available data; note when additional tools would improve the report.