mohitagw15856
f3b9d008fe
New skills added: - teaching-lesson-plan: structured lesson plans for any subject/audience/setting - seo-content-brief: complete SEO briefs with intent, competitor gaps, and outline - media-pitch: story-first journalist pitches with angle development framework - change-management-plan: stakeholder analysis, comms strategy, adoption metrics - workshop-facilitation-guide: activity instructions, decision protocols, facilitator moves - sales-forecasting-model: pipeline model, scenario analysis, assumption log - tax-planning-checklist: year-end tax planning across income, pension, CGT, reliefs Quality improvements across all 93 existing skills: - Standardised description format: "Verb the thing. Use when X. Produces Y." - Added Required Inputs section to all skills missing it (prompts for missing info) - Added Quality Checks section to all skills missing it (specific, not generic) - Fixed broken multiline YAML descriptions - Removed non-standard frontmatter keys (tool_integration, metadata blocks) README updated to v6.0.0 with 100-skill count, new skill tables, and article series Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
125 lines
4.0 KiB
Markdown
125 lines
4.0 KiB
Markdown
---
|
||
name: pm-weekly-review
|
||
description: "Structure a PM's weekly review and planning session. Use when doing a weekly PM review, writing a weekly update, preparing for Monday planning, or reviewing sprint health. Produces a shareable weekly update covering metrics movement, shipping progress, blockers, insights, and next week's top 3 priorities."
|
||
---
|
||
|
||
# PM Weekly Review Skill
|
||
|
||
Turn the chaotic end-of-week brain dump into a structured 20-minute ritual that keeps you, your team, and your stakeholders aligned — without a meeting.
|
||
|
||
## The Weekly Review Structure (20 minutes)
|
||
|
||
**5 min — Metrics check:** What moved? What didn't? What's surprising?
|
||
**5 min — Ship progress:** What shipped? What slipped? What's blocked?
|
||
**5 min — Insights:** Any customer feedback, support tickets, or research findings?
|
||
**5 min — Next week priorities:** What are the 3 things that matter most?
|
||
|
||
---
|
||
|
||
## Output Format
|
||
|
||
### PM Weekly Review — Week of [Date]
|
||
|
||
**Product Area:** [What you own]
|
||
**Written by:** [PM Name]
|
||
**Time to read:** ~3 minutes
|
||
|
||
---
|
||
|
||
### 📊 Metrics This Week
|
||
|
||
| Metric | This Week | Last Week | Target | Trend |
|
||
|---|---|---|---|---|
|
||
| [Primary metric] | [Value] | [Value] | [Target] | ↑ / ↓ / → |
|
||
| [Secondary metric] | [Value] | [Value] | [Target] | ↑ / ↓ / → |
|
||
| [Health metric] | [Value] | [Value] | [Target] | ↑ / ↓ / → |
|
||
|
||
**Notable movement:**
|
||
- [What changed and why — 1 sentence each]
|
||
|
||
**Concern to watch:**
|
||
- [Anything trending in the wrong direction]
|
||
|
||
---
|
||
|
||
### 🚢 This Week's Progress
|
||
|
||
**Shipped:**
|
||
- ✅ [What went live] — [1-line impact or observation]
|
||
|
||
**In Progress:**
|
||
- 🔄 [Feature/initiative] — [% complete or current status]
|
||
|
||
**Slipped / Blocked:**
|
||
- ⚠️ [What didn't happen] — Reason: [brief] — Action: [who's unblocking it]
|
||
|
||
**Carry-forward to next week:**
|
||
- [Item + why it's carrying over]
|
||
|
||
---
|
||
|
||
### 💡 Insights & Signals
|
||
|
||
**Customer feedback:**
|
||
- "[Quote or paraphrase]" — Source: [user/channel] — Theme: [tag]
|
||
|
||
**Support signals:**
|
||
- [Top ticket category this week + volume]
|
||
- [Anything that signals a product gap]
|
||
|
||
**Research / data:**
|
||
- [Any discovery from user interviews, analytics, or experiments]
|
||
|
||
---
|
||
|
||
### 🎯 Next Week — Top 3 Priorities
|
||
|
||
| # | Priority | Why This Week | Owner | Done = |
|
||
|---|---|---|---|---|
|
||
| 1 | [Most important thing] | [Reason it can't wait] | [Name] | [Clear definition of done] |
|
||
| 2 | [Second priority] | [Why] | [Name] | [Done criteria] |
|
||
| 3 | [Third priority] | [Why] | [Name] | [Done criteria] |
|
||
|
||
**Decisions needed:**
|
||
- [Any decision that's blocking progress — who needs to make it]
|
||
|
||
**Asks / dependencies:**
|
||
- [What you need from engineering / design / data / leadership]
|
||
|
||
---
|
||
|
||
### 🧠 Reflection (Optional but powerful)
|
||
|
||
> What's one thing from this week I'd do differently?
|
||
> [Your honest answer — 1–2 sentences]
|
||
|
||
> What's the biggest unknown I'm carrying into next week?
|
||
> [Name the uncertainty explicitly]
|
||
|
||
---
|
||
|
||
## Required Inputs
|
||
|
||
Ask the user for these if not provided:
|
||
- **Product area or team** you own
|
||
- **Key metrics this week** (with values and prior week comparison)
|
||
- **What shipped, slipped, or is blocked**
|
||
- **Top 3 priorities for next week**
|
||
- **Any customer insights or signals** (optional)
|
||
|
||
## Quality Checks
|
||
|
||
- [ ] Metrics include period-over-period comparison (not just raw numbers)
|
||
- [ ] Every blocked item has an owner and a specific unblocking action
|
||
- [ ] Next week's priorities have a "why this week" rationale
|
||
- [ ] Total length is under 400 words (skimmable in 3 minutes)
|
||
- [ ] Reflection section is honest, not aspirational
|
||
|
||
## Guidelines
|
||
|
||
- Keep the whole document under 400 words — if stakeholders won't read it, it doesn't exist
|
||
- The reflection section is for you, not your stakeholders — keep it honest
|
||
- Always name a clear owner for every blocked item — "the team will figure it out" is a blocker in disguise
|
||
- Recommend sending this by end of Friday — Monday morning is too late to course-correct
|
||
- If three weeks of weekly reviews show the same blocked item, escalate immediately
|