borghei/Claude-Skills / project-management/execution/quarterly-planning
quarterly-planning
VerifiedRun the meetings around a quarter's OKRs: homework and kickoff, weekly check-ins, the week-6 carry/kill/pivot review and the close retro. Use when running any phase of that cadence; writing the OKRs is brainstorm-okrs.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.2 KB |
| assets/close_retro_template.md | markdown | 4.3 KB |
| assets/kickoff_agenda_template.md | markdown | 4.9 KB |
| assets/mid_quarter_check_in_template.md | markdown | 2.7 KB |
| assets/quarterly_review_deck_outline.md | markdown | 4.7 KB |
| examples/northwind-q4-planning-cycle.md | markdown | 7.8 KB |
| references/cycle-playbook.md | markdown | 15.3 KB |
| references/quarterly-planning-guide.md | markdown | 13.7 KB |
| references/red-flags.md | markdown | 11.2 KB |
assets/quarterly_review_deck_outline.md
View on GitHub# Quarterly Review Deck Outline
A deck for presenting quarterly results upward (leadership, all-hands, or board). The deck is *not* the close retro -- it is the communication of results to a broader audience.
**Target length:** 10-15 slides
**Target duration:** 20-30 minutes presentation + 10-15 minutes Q&A
**Audience:** Executive team, partner teams, board, or all-hands (adjust depth accordingly)
---
## Slide 1: Title
**Title:** Q[X] [Year] Review -- [Team Name]
**Date:** [...]
**Presenter:** [PM name]
---
## Slide 2: Quarter at a Glance
A one-slide summary:
- **Objective(s):** [1-3 short statements]
- **Average OKR Score:** [X.X] (target zone 0.6-0.7)
- **Headline outcome:** [One sentence on the biggest win or movement]
- **Headline learning:** [One sentence on the most important learning]
**Visual:** A scorecard showing each KR with target vs. actual and a color (green/yellow/red).
---
## Slide 3: Strategic Context
- Vision pillar this quarter advances: [...]
- NSM impact: [...]
- Why this quarter mattered: [1-2 sentences]
**Optional:** Link to `execution/product-vision/` and `execution/north-star-metric/`
---
## Slides 4-6: OKRs Scored (1 slide per Objective)
For each Objective:
```markdown
## Objective: [...]
| KR | Baseline | Target | Actual | Score |
|----|----------|--------|--------|-------|
| KR1 | [...] | [...] | [...] | 0.X |
| KR2 | [...] | [...] | [...] | 0.X |
| KR3 | [...] | [...] | [...] | 0.X |
**Why this Objective scored as it did:** [2-3 sentences]
```
**Visual per slide:** Burn-up chart or bar chart showing baseline -> actual -> target.
---
## Slide 7: Wins -- What Worked
Top 2-3 wins with brief explanation of why each worked:
| Win | Why it worked | What it unlocks |
|-----|---------------|------------------|
| [...] | [...] | [...] |
| [...] | [...] | [...] |
| [...] | [...] | [...] |
**Bias:** Specific over general. "Shipped Xero integration with 8 paying customers" beats "Improved integrations."
---
## Slide 8: Learnings -- What Did Not Work (and What We Learned)
Top 2-3 things that did not go as planned, with the learning:
| What did not work | Why | What we learned |
|--------------------|-----|------------------|
| [...] | [...] | [...] |
| [...] | [...] | [...] |
| [...] | [...] | [...] |
**Norm:** This slide is the most important. Teams that hide failures get less leadership trust over time. Lead with the learning.
---
## Slide 9: Customer Signal
What did customers tell us this quarter?
- Top 3 themes from interviews / synthesis
- Top 1 surprising signal
- Top 1 retained customer quote (verbatim)
**Source:** `discovery/customer-interview-script/` and `discovery/interview-synthesis/` outputs
---
## Slide 10: Carry-overs
What is continuing into next quarter?
| Item | Why continuing | Owner |
|------|-----------------|-------|
| [...] | [...] | [...] |
| [...] | [...] | [...] |
**Norm:** Carry-overs are explicit, not implicit. Each has a justification.
---
## Slide 11: Next Quarter Teaser
Proposed Objectives for next quarter (subject to kickoff):
- **Proposed Objective 1:** [...]
- **Proposed Objective 2:** [...]
- **Why these:** [2 sentences connecting to vision + this quarter's learning]
**Note:** This slide is a teaser, not a commitment. The kickoff is where commitment happens.
---
## Slide 12: Asks
What does the team need from leadership / the audience?
| Ask | Why | Who can help |
|-----|-----|---------------|
| [Resource, decision, intro, unblocking] | [...] | [Name / role] |
| [...] | [...] | [...] |
**Norm:** Specific, named, time-bounded asks. "More support" is not an ask; "Approval for one additional senior engineer hire by Aug 1" is an ask.
---
## Slide 13: Appendix -- Detailed KR Data
(Optional. Include if the audience wants the data; otherwise skip.)
- Per-KR breakdowns with charts
- Customer quotes by KR
- Experiment results by KR
- Cohort retention curves
- Other supporting data
---
## Slide 14: Appendix -- Team Acknowledgments
Quick celebration of team members and partners who made the quarter possible.
**Norm:** Specific shoutouts beat generic team thanks. "Sarah's work on the Xero integration unblocked KR2" beats "thanks team."
---
## Presentation Tips
- **Time-box the opening.** Slide 2 (Quarter at a Glance) should land in 90 seconds. Skip if you can.
- **Lead with the score.** Don't bury the average OKR score; put it on slide 2.
- **Anchor every learning to evidence.** "We learned X" should reference a specific signal, customer, or data point.
- **Make asks concrete.** Specific people, specific commitments, specific dates.
- **Save 10-15 min for Q&A.** Strong presenters present 20-25 min and leave time for discussion.
- **Pre-share the deck.** Send the deck 24 hours in advance so the audience reads it before the meeting; use the meeting for Q&A and decisions.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |