status-update

Quick Start

Tell me:

1. Who is this update for? (your team, your manager, execs, cross-functional stakeholders)
2. What time period? (daily, weekly, monthly, project milestone)
3. Any specific topics to highlight? (launches, blockers, metrics, decisions)

I'll pull context from your PRDs, meetings, and metrics automatically.

You can also just say "pull from my recent work" and I'll scan your workspace for everything that happened.

Shortcut: /status-update weekly for my manager -- and I'll handle the rest.

/status-update - Weekly Updates That Actually Get Read

When the PM types /status-update, create status updates that communicate progress, surface blockers, and keep stakeholders aligned.

Context Routing Logic (Internal - for Claude)

Automatic Context Checks: When this skill is invoked, immediately check:

| Source | Files/Folders | Search Terms | What to Extract | | -------------------- | ---------------------------------- | --------------------------------- | --------------------------------- | | Recent PRDs | thoughts/shared/pm/prds/.md | feature being updated | Feature status and changes | | Meeting Notes | thoughts/shared/product/meeting-notes/.md | this week's meetings | Decisions, action items, blockers | | Action Items | thoughts/shared/product/meeting-notes/ | completed / in progress / blocked | Track completion of commitments | | Strategy | thoughts/shared/pm/frameworks/.md | strategic pillars | Tie accomplishments to strategy | | Metrics | thoughts/shared/pm/metrics/.md | baseline, trends | Metric movement and progress | | Stakeholder Profiles | Stakeholder templates | your audience | Communication style for audience |

Context Priority:

1. Your recent work (PRDs, meetings) FIRST
2. Completed action items SECOND
3. Strategic context (pillars, goals) THIRD
4. Metrics and progress FOURTH

Cross-Skill Links:

• If action items from meetings → Reference /meeting-notes
• If progress on features → Reference /prd-draft or /feature-results
• If metric updates → Reference /metrics-framework and North Star
• If blockers → Link to relevant skill for resolution (e.g., /prd-draft if scope unclear)

Step 0: Understanding Your Update Context

Before drafting, let me gather what happened...

Checking:

• thoughts/shared/product/meeting-notes/ for recent meetings this week/period
• thoughts/shared/pm/prds/ for features you're working on
• thoughts/shared/pm/metrics/ for recent metric changes
• thoughts/shared/pm/frameworks/ for strategic context
• Stakeholder profiles for communication style of audience

Based on what I find, I'll show you:

Your Recent Work

Completed This Week:

• [Shipped features / completed action items]
• [Decisions made]
• [Blockers resolved]

In Progress:

• [Features in development]
• [Research underway]
• [Outstanding action items]

Blockers:

• [What's blocking progress]
• [Who needs to help]
• [When you need resolution by]

PM-Specific Diagnosis Questions

1. Accomplishment Type: What's worth highlighting? (Shipped / learned / decided / shipped)
2. Metric Movement: Did metrics move? In expected direction?
3. Blocker Severity: Are blockers getting in the way? Need escalation?
4. Strategic Tie: How do accomplishments connect to Q# strategy?
5. Stakeholder Expectations: What does your audience care about most?

When to Use

• Weekly team updates
• Monthly progress reports to leadership
• Daily standups (async)
• Project milestone updates
• Quarterly business reviews
• Manager 1:1 prep
• Stakeholder check-ins

How It Works

Step 1: Tell Me What's Happened

Step 2: Get a Structured Update

Step 1: Tell Me What's Happened

When the PM types /status-update, I'll ask:

Let's create your status update.

**What period is this covering?**
- Daily (standup)
- Weekly (team update)
- Monthly (leadership update)
- Project milestone
- Other: [specify]

**Who's the audience?**
- Your team
- Your manager
- Cross-functional stakeholders
- Executive leadership
- All of the above

**Update format?**
- Quick (3 bullets max)
- Standard (progress + blockers + next steps)
- Detailed (full context for executives)

Now, just tell me what happened this week. Don't structure it -
just brain dump and I'll organize it.

You can also say "pull from my recent work" and I'll scan:
- Meeting notes from this week
- PRDs you've updated
- Action items you've completed
- Conversations in this chat

Step 2: Get Your Structured Update

Once I understand what happened:

Got it. Creating your [weekly] status update for [audience].

I'm pulling from:
- Meeting notes: [X meetings this week]
- Completed action items: [Y items]
- PRD updates: [Z documents]
- Recent decisions: [Context from this chat]

Here's your update:

Standard Weekly Update Format

# Weekly Update: [Your Name] - [Date Range]

## 🎯 Key Accomplishments

**Shipped / Completed:**

- [Specific outcome with impact] - [Link]
- [Specific outcome with impact] - [Link]

**Progress Made:**

- [Initiative name]: [What moved forward and why it matters]
- [Initiative name]: [What moved forward and why it matters]

**Decisions Made:**

- [Decision]: [Impact and who was involved]

## 📊 Metrics & Impact

| Metric             | Last Week | This Week | Target | Status      |
| ------------------ | --------- | --------- | ------ | ----------- |
| [Primary metric]   | [#]       | [#]       | [#]    | 🟢 On track |
| [Guardrail metric] | [#]       | [#]       | [#]    | 🟡 Watching |

**What this means:**
[One sentence on trajectory toward goals]

## 🚧 Blockers & Risks

**Blocking me:**

1. [Specific blocker] - **Need:** [Specific help] from @[Person] by [Date]
2. [Specific blocker] - **Need:** [Specific help] from @[Person] by [Date]

**Risks I'm watching:**

- [Risk description] - **Mitigation:** [What you're doing about it]

**Nothing blocking?** → ✅ No blockers this week

## 🔜 Next Week

**Top Priorities:**

1. [Specific deliverable] - Due [Date]
2. [Specific deliverable] - Due [Date]
3. [Specific deliverable] - Due [Date]

**Meetings/Milestones:**

- [Important meeting] on [Date] - [Purpose]
- [Milestone] target for [Date]

## 💬 Discussion

**Questions for the team:**

- [Question where you need input]
- [Question where you need input]

**Where I could use help:**

- [Specific area] - If you have experience with [X], would love to chat

---

**Full context:** [Link to detailed project board / PRD / doc]

Format Variations by Audience

For Your Manager (1:1 Prep)

# 1:1 Prep: [Date]

## ✅ Since Last Time

- [Thing you committed to] - Done
- [Thing you committed to] - In progress (70%)
- [Thing you committed to] - Blocked by [X]

## 🎯 This Week's Wins

[1-2 things that went really well]

## 🤔 Where I'm Stuck

1. **[Problem]**
   - What I've tried: [A, B, C]
   - What I need: [Your advice on X]

## 💭 Topics for Discussion

- [Topic 1]: [Why it's important]
- [Topic 2]: [Why it's important]
- [Topic 3]: [Why it's important]

## 📈 Career Development

[Any progress on goals you've set together]

## 🔜 My Commitments for Next Week

1. [Commitment]
2. [Commitment]
3. [Commitment]

Why this works:

• Shows you're on top of commitments
• Highlights wins (self-advocacy matters)
• Makes it easy for manager to help you
• Drives the agenda (you're not passive)
• Tracks career growth
• Clear commitments (accountability)

For Executive Leadership

# Product Update: [Initiative Name] - [Date]

## Executive Summary

**Status:** 🟢 On Track / 🟡 At Risk / 🔴 Off Track

**This week in one senten