Skip to content

borghei/Claude-Skills / project-management/execution/quarterly-planning

quarterly-planning

Verified

Run 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.

assets/close_retro_template.md

View on GitHub
# Close-of-Quarter Retro Agenda

**Quarter:** Q[X] [Year]
**Date:** [YYYY-MM-DD] (week 13)
**Length:** 90 minutes
**Facilitator:** [PM name]
**Participants:** Same as kickoff (PM, EM, Design Lead, exec sponsor, key cross-functional)

---

## Pre-Read (sent 24 hours in advance)

- [ ] Final KR data (baseline, target, actual)
- [ ] Carry-over and pivot decisions from mid-quarter check-in
- [ ] Customer signal from quarter (themes from `discovery/customer-interview-script/` + `discovery/interview-synthesis/`)
- [ ] Suggested next-quarter outcome candidates from PM

---

## Agenda

### 0:00 - 0:30 | Reflect: Score the OKRs (30 min)

For each KR, score 0.0 to 1.0 using the table below:

| Score | Interpretation |
|-------|----------------|
| 0.0 - 0.3 | Failed to move; hypothesis or execution was wrong |
| 0.4 - 0.6 | Partial progress; mixed signal |
| 0.7 - 0.9 | Strong outcome (Wodtke's target zone) |
| 1.0 | Maximum success (warning: was the target sandbagged?) |

#### Scoring table

| Objective | KR | Baseline | Target | Actual | Score (0.0-1.0) | Commentary |
|-----------|----|----------|--------|--------|------------------|------------|
| O1 | KR1 | [...] | [...] | [...] | [...] | [why this score] |
| O1 | KR2 | [...] | [...] | [...] | [...] | [...] |
| O1 | KR3 | [...] | [...] | [...] | [...] | [...] |
| O2 | KR1 | [...] | [...] | [...] | [...] | [...] |

**Average team score:** [X.X]

**Wodtke heuristic check:**
- If average > 0.9: were the targets sandbagged?
- If average < 0.5: were the targets unrealistic, or was execution off?
- Target zone over multiple quarters: 0.6-0.7

---

### 0:30 - 1:00 | Reflect: What Did We Learn? (30 min)

Round-robin -- each participant shares:

#### About the customer

- One thing we learned about what the customer wants, needs, or struggles with
- Source: which interview, which data, which signal

#### About the product

- One thing we learned about what works (or does not) in the product
- Source: which experiment, which release, which data

#### About the team / process

- One thing we learned about how the team operates
- One thing we will start, stop, or continue

#### Capture into the learning log

| Type | Learning | Source | Implication for next quarter |
|------|----------|--------|-------------------------------|
| Customer | [...] | [...] | [...] |
| Customer | [...] | [...] | [...] |
| Product | [...] | [...] | [...] |
| Product | [...] | [...] | [...] |
| Team | [...] | [...] | [...] |
| Team | [...] | [...] | [...] |

---

### 1:00 - 1:30 | Decide: What Carries to Next Quarter? (30 min)

#### Incomplete KRs

| KR | Score | Recommendation |
|----|-------|-----------------|
| [...] | [...] | Carry / Kill / Pivot |
| [...] | [...] | Carry / Kill / Pivot |

For each "Carry" recommendation, justify: why is the hypothesis still right?

For each "Kill" recommendation, capture the learning that informs the kill.

#### New opportunities surfaced this quarter

| Opportunity | Source | Pre-work owner for next kickoff |
|-------------|--------|----------------------------------|
| [...] | [...] | [...] |
| [...] | [...] | [...] |

#### Pre-work assignments for next quarter

- [ ] Strategy review owner: [Name] -- due [date]
- [ ] Outcome candidate list owner: [Name] -- due [date]
- [ ] Capacity assessment owner: [Name] -- due [date]
- [ ] Kickoff brief owner: [Name] -- due [date]
- [ ] Next kickoff meeting date: [...]

---

## Outputs

By end of meeting:

- [ ] Every KR scored 0.0-1.0 with commentary
- [ ] Average team score recorded (for trend tracking)
- [ ] Learning log updated with customer, product, and team learnings
- [ ] Carry/Kill/Pivot decisions made on incomplete KRs
- [ ] New opportunities logged for next quarter's pre-work
- [ ] Next quarter's pre-work owners and dates assigned
- [ ] Retro notes published to team wiki
- [ ] Quarterly review deck input compiled (`assets/quarterly_review_deck_outline.md`)
- [ ] Wins celebrated, not just losses analyzed

---

## Optional: Anonymous "What did you not say?" round (10 min addition)

If team dynamics suggest unspoken concerns, run a short anonymous round:

- Each participant writes one thing they did not feel comfortable saying out loud
- Facilitator reads them aloud anonymously
- Team discusses themes

Use sparingly -- not every retro needs this, but it can surface issues that block honest scoring.
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall
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: 108kUpdated Claude CodeCodexVerifiedInstall
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: 108kUpdated Claude CodeCodexVerifiedInstall