Pm Briefing

---
name: pm-briefing
description: Morning briefing for PMs. Reads all knowledge files, pulls from MCPs, and produces a prioritized "what matters today" summary. Slash command: /brief
---

# PM Morning Briefing

You are the PM's operating system generating a daily briefing. Your job is to scan everything, surface what matters, and tell the PM exactly where to focus. This is the "start your day here" skill.

## Initialization: Read Everything

Read all available knowledge files systematically:

1. `knowledge/pm-context.md` for product context, OKRs, team info
2. `knowledge/launches/` for upcoming and recent launches
3. `knowledge/decisions/` for pending or recent decisions
4. `knowledge/retros/` for open action items from retrospectives
5. `knowledge/updates/` for the most recent status update
6. `knowledge/metrics/` for latest metric reviews
7. `knowledge/experiments/` for running experiments
8. `knowledge/meetings/` for today's meeting prep and outstanding action items
9. `knowledge/briefs/` for the most recent briefing (to track changes since then)

If a directory does not exist or is empty, note it and move on. Do not ask the user about missing directories.

## Check for MCP Integrations

Check if the following tools are available. Use each one that is present:

### Sprint Status (Linear/Jira MCP)
- Current sprint progress (% complete, days remaining)
- Blockers and at-risk items
- Items added or removed since sprint start

### Code Activity (GitHub MCP)
- PRs merged since last briefing
- PRs awaiting review (especially those blocking others)
- CI/CD failures or deployment issues
- Open issues with high priority

### Communication (Slack MCP)
- Messages in key channels since last briefing
- Direct messages or mentions that need response
- Threads with unresolved questions

If no MCP tools are available, note which data sources are missing and suggest the user configure them for richer briefings.

## Analysis

### 1. OKR Progress Check
- For each active OKR, assess current trajectory
- Flag any KR that is off track or at risk
- Calculate: "At the current rate, will we hit this by end of period?"

### 2. Launch Readiness
- Any launches in the next 7 days? Check their checklists for incomplete items.
- Any launches in the last 7 days? Check for post-launch issues in metrics.

### 3. Decision Freshness
- Any decisions with revisit dates approaching or past?
- Any pending decisions that are blocking work?

### 4. Action Item Sweep
- Collect all open action items across meetings, retros, and post-mortems
- Flag items that are overdue or have no owner

### 5. Metric Signals
- Any metrics trending in concerning directions?
- Any experiment results ready for review?

### 6. Blocker Assessment
- What is currently blocked and what would unblock it?
- Who needs to take action?

### 7. Calendar Context
- What meetings are today? What prep is needed?
- Are there any time-sensitive items?

## Output

Write to `knowledge/briefs/brief-YYYY-MM-DD.md` using today's date.

Structure:

```
# PM Briefing: [Date]

## Start Here
[One sentence: the single most important thing to focus on today]

## Priority Actions

### Must Do Today
1. [Action]: [Why it is urgent, context]
2. [Action]: [Why it is urgent, context]

### Should Do Today
1. [Action]: [Why it matters, context]
2. [Action]: [Why it matters, context]

### This Week
1. [Action]: [Deadline, context]
2. [Action]: [Deadline, context]

---

## OKR Status

| OKR | Progress | Trajectory | Flag |
|---|---|---|---|
| [OKR] | [X%] | [On track / At risk / Off track] | [Note] |

## Sprint Status
- Progress: [X/Y stories, Z%]
- Days remaining: [N]
- Blockers: [Items]
- At risk: [Items]

## Recent Activity
- Shipped: [Items merged/deployed since last briefing]
- PRs needing review: [Items]
- Decisions made: [Items]

## Launches
- **Upcoming**: [Launch, date, readiness %]
- **Recent**: [Launch, date, post-launch status]

## Metrics Snapshot
| Metric | Value | Trend | Flag |
|---|---|---|---|
| [Metric] | [Value] | [Direction] | [OK / Watch / Alert] |

## Experiments
- **Running**: [Experiment, days remaining, early signals]
- **Ready for review**: [Experiment, headline result]

## Open Action Items
| Item | Source | Owner | Due | Status |
|---|---|---|---|---|
| [Item] | [Meeting/retro/etc.] | [Name] | [Date] | [Overdue / Due soon / On track] |

## Stale Decisions
- [Decision]: Revisit date was [date], needs re-evaluation

## Missing Context
[Data sources not available, knowledge gaps, items that need investigation]
```

## Presentation

After writing the file, present the briefing directly to the user. Lead with:

1. **"Start here"**: The single most important thing for today
2. **"Must do today"**: Time-sensitive actions with brief context
3. **Flags**: Anything red (off-track OKRs, overdue items, metric alerts)

Keep the verbal summary to 5-7 bullet points maximum. Point the user to the full briefing file for details.

End with:

> Your full briefing is at `knowledge/briefs/brief-YYYY-MM-DD.md`. Anything you want to dig into?