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/kickoff_agenda_template.md
View on GitHub# Quarterly Kickoff Meeting Agenda
**Quarter:** Q[X] [Year]
**Date:** [YYYY-MM-DD]
**Time:** [start - end, timezone]
**Length:** [2 / 3] hours (or 2 x 90 min split)
**Location:** [Room / Link]
**Facilitator:** [PM name]
**Note-taker:** [Name]
**Participants:** [PM, EM, Design Lead, Exec Sponsor, key cross-functional partners]
---
## Pre-Read
Sent 48 hours in advance:
- [ ] Kickoff brief (1 page summarizing strategy review, candidate outcomes, capacity)
- [ ] Last quarter's close retro notes
- [ ] Top 3 customer signals from `discovery/customer-interview-script/` recent sessions
- [ ] Updated `execution/dependency-map/` output
---
## Agenda
### 0:00 - 0:15 | Reflect: Last Quarter (15 min)
- Average OKR score from last quarter: [X.X]
- Top 2 learnings from last quarter's retro
- Carry-overs proposed (decision in this meeting):
- [Item 1]
- [Item 2]
- [Item 3]
**Decisions captured:**
- [ ] Carry-over decisions: [list]
---
### 0:15 - 0:45 | Align: Strategy Context (30 min)
- **Vision status:** [Unchanged / Updated / Reset] -- link to `execution/product-vision/`
- **NSM status:** Current [X], target [Y], trend [up/down/flat]
- **Customer signal (top 3 themes from recent interviews):**
- [Theme 1]
- [Theme 2]
- [Theme 3]
- **Competitive signal (top moves to respond to):**
- [Move 1]
- [Move 2]
- **Operational signal (org, budget, exec mandates):**
- [...]
**Strategy choices to make explicit this quarter:**
| Choice | Last quarter | This quarter |
|--------|--------------|---------------|
| Build / Buy / Partner | [...] | [...] |
| Grow / Retain emphasis | [...] | [...] |
| Primary segment focus | [...] | [...] |
| Risk posture | Aggressive / Balanced / Safe | [...] |
---
### 0:45 - 1:15 | Reflect: Candidate Outcomes (30 min)
PM walks through the 5-10 candidate outcomes from pre-work:
| # | Outcome | Hypothesis | Confidence | Effort | Owner candidate |
|---|---------|-----------|------------|--------|------------------|
| 1 | [...] | [...] | 7 | M | [...] |
| 2 | [...] | [...] | 6 | L | [...] |
| 3 | [...] | [...] | 8 | S | [...] |
| 4 | [...] | [...] | 5 | XL | [...] |
| 5 | [...] | [...] | 7 | M | [...] |
**Discussion focus:**
- Which candidates align with the strategy choices above?
- Which have customer evidence (`discovery/customer-interview-script/` traceable)?
- Which dependencies are critical?
---
### 1:15 - 1:30 | Break (15 min)
---
### 1:30 - 2:15 | Decide: Commit to OKRs (45 min)
**Vote on 1-3 Objectives:**
- Each participant gets 1 vote (3 if multiple Os allowed)
- Discuss top-voted Objectives; final commit per Objective requires team consensus
**For each committed Objective, define 3-5 Key Results:**
```markdown
## Objective: [...]
> Why this Objective serves the vision: [...]
### KR1: [Metric] from [baseline] to [target] by [date]
- Owner: [...]
- Confidence at commit: [1-10]
- Validation source: [...]
### KR2: [...]
### KR3: [...]
```
**Apply SMART check (from `execution/brainstorm-okrs/`):**
- [ ] Specific
- [ ] Measurable (baseline + target + deadline)
- [ ] Achievable (~70% confidence at commit per Wodtke)
- [ ] Relevant (traces to Objective and vision)
- [ ] Time-bound
---
### 2:15 - 2:45 | Decide: Roadmap and Capacity (30 min)
- Map committed OKRs to roadmap horizons:
| KR | Roadmap horizon (Now/Next/Later) | Roadmap items |
|----|-----------------------------------|---------------|
| KR1 | Now | [...] |
| KR2 | Now/Next | [...] |
| KR3 | Next | [...] |
- **Capacity check:**
- Total person-weeks available: [X]
- Committed person-weeks (this OKR set): [Y]
- Reserve (15-20%): [Z]
- Headroom: [X - Y - Z]
- Decision: Y <= X - Z? If not, cut.
- **Cross-team dependencies:** Confirm with named owners
- [Dependency 1 -- partner team, ETA]
- [Dependency 2 -- partner team, ETA]
---
### 2:45 - 3:00 | Decide: Tracking Cadence + Closeout (15 min)
**Calendar locks (set during the meeting):**
- [ ] Monday Commit: every Mon [time] for the quarter
- [ ] Friday Celebrate: every Fri [time] for the quarter
- [ ] Biweekly KR confidence review: every other Friday [time]
- [ ] Mid-quarter check-in: [date, week 6]
- [ ] Close-of-quarter retro: [date, week 13]
- [ ] Quarterly review presentation (to exec/all-hands): [date, week 13 or 14]
**Artifact owners:**
- OKR doc: [Name]
- Roadmap: [Name]
- Capacity plan: [Name]
- Risk register: [Name]
- Status updates (weekly/biweekly): [Name]
**Communication:**
- [ ] OKRs published in [team wiki / OKR tool]
- [ ] Summary email sent to [stakeholders]
- [ ] Kickoff notes posted to [location]
---
## Outputs
By end of meeting:
- [ ] 1-3 Objectives committed
- [ ] 3-5 KRs per Objective with baseline, target, deadline, owner
- [ ] Roadmap mapped (Now / Next / Later)
- [ ] Capacity plan reconciled
- [ ] Cross-team dependencies named with partner-team owners
- [ ] Cadence meetings on calendar
- [ ] Artifact owners assigned
- [ ] Mid-quarter check-in date confirmed
- [ ] Close retro date confirmed
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 |