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/mid_quarter_check_in_template.md

View on GitHub
# Mid-Quarter Check-in Agenda

**Quarter:** Q[X] [Year]
**Date:** [YYYY-MM-DD] (week 6 of 13)
**Length:** 90 minutes
**Facilitator:** [PM name]
**Participants:** Same as kickoff

---

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

- [ ] KR confidence trend (per biweekly review)
- [ ] Current data for each KR (baseline vs. current vs. target)
- [ ] Open blockers and dependencies
- [ ] Carry-over decision proposals from PM

---

## Agenda

### 0:00 - 0:15 | Reflect: Where Are We? (15 min)

Quick visual walk-through of each KR:

| KR | Baseline | Target | Current | % to target | Confidence (1-10) |
|----|----------|--------|---------|--------------|---------------------|
| KR1 | [...] | [...] | [...] | [...]% | [...] |
| KR2 | [...] | [...] | [...] | [...]% | [...] |
| KR3 | [...] | [...] | [...] | [...]% | [...] |

**Visual:** Burn-up chart of actual vs. target line.

---

### 0:15 - 0:45 | Reflect: What Is Working? (30 min)

For each KR with confidence >= 6:

- **What is driving progress?**
- **Can we double down?**
- **Are there learnings to share across other KRs?**

Capture wins to scale:

| Win | Why it worked | Where else to apply |
|------|---------------|----------------------|
| [...] | [...] | [...] |
| [...] | [...] | [...] |

---

### 0:45 - 1:15 | Align + Decide: What Is Not Working? (30 min)

For each KR with confidence <= 5, run the carry/kill/pivot/escalate decision:

#### KR [#]: [name] -- Confidence [X]

**The bottleneck:**
- [...]

**Options:**
- **Carry:** Continue as planned; add [resource/dependency]
- **Kill:** Drop the KR. Redirect capacity to [...]
- **Pivot:** Reframe to [new KR statement] based on learning [...]
- **Escalate:** Decision needs [exec / cross-team owner]

**Decision:** [Carry / Kill / Pivot / Escalate]

**Owner of next step:** [Name]

**By when:** [Date]

---

#### Repeat for each at-risk KR

(One sub-section per at-risk KR)

---

### 1:15 - 1:30 | Decide: Adjust Roadmap and Capacity (15 min)

- **Killed KRs:** [list]
  - Capacity freed: [X person-weeks]
  - Redirect to: [...]

- **Pivoted KRs:** [list]
  - Roadmap items removed: [...]
  - Roadmap items added: [...]
  - Capacity impact: [...]

- **Carried KRs:** [list]
  - Additional resources needed: [...]
  - Unblocking actions: [...]

- **Updated OKR doc:** versioned, not overwritten (preserve history)

---

## Outputs

By end of meeting:

- [ ] Confidence updated on every KR
- [ ] Explicit decision (Carry/Kill/Pivot/Escalate) for every KR with confidence <= 5
- [ ] Updated OKR doc circulated to stakeholders
- [ ] Capacity reconciled
- [ ] New blockers logged with owners
- [ ] Escalations communicated to relevant execs / partner teams
- [ ] All decisions added to the team's decision log
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