Skip to content

borghei/Claude-Skills / project-management/execution/brainstorm-okrs

brainstorm-okrs

Verified

Draft and score quarterly OKRs: a qualitative objective, measurable key results and a counter-metric. Use when setting or reviewing a team's OKRs before they are committed, or when KRs read like a task list.

assets/okr_template.md

View on GitHub
# OKR Document: [Team/Company Name]

**Quarter:** Q[X] [Year]
**Owner:** [Name]
**Status:** Draft | Active | Scored
**Last Updated:** [YYYY-MM-DD]

---

## Company Context

**Company Objective:** [What strategic direction are we supporting?]
**North Star Metric:** [The single metric that captures core value delivery]

---

## OKR Set 1

### Objective

[Qualitative, inspirational, time-bound statement -- no numbers]

### Key Results

| # | Key Result | Metric | Current | Target | Confidence | Score |
|---|-----------|--------|---------|--------|------------|-------|
| 1 | | | | | /10 | /1.0 |
| 2 | | | | | /10 | /1.0 |
| 3 | (counter-metric) | | | | /10 | /1.0 |

### Rationale

[2-3 sentences: Why this objective? How does it connect to the company objective?]

---

## OKR Set 2 (Optional)

### Objective

[Qualitative, inspirational, time-bound statement]

### Key Results

| # | Key Result | Metric | Current | Target | Confidence | Score |
|---|-----------|--------|---------|--------|------------|-------|
| 1 | | | | | /10 | /1.0 |
| 2 | | | | | /10 | /1.0 |
| 3 | (counter-metric) | | | | /10 | /1.0 |

### Rationale

[2-3 sentences]

---

## Weekly Check-In Log

### Week [N] - [Date]

| KR | Confidence | Status | This Week's Focus |
|----|------------|--------|-------------------|
| KR1 | Green/Yellow/Red | [Brief update] | [What will move this forward] |
| KR2 | Green/Yellow/Red | [Brief update] | [What will move this forward] |
| KR3 | Green/Yellow/Red | [Brief update] | [What will move this forward] |

**Blockers:** [Any impediments]

---

## Quarterly Review

### Scores

| OKR Set | KR1 | KR2 | KR3 | Average |
|---------|-----|-----|-----|---------|
| Set 1 | /1.0 | /1.0 | /1.0 | /1.0 |
| Set 2 | /1.0 | /1.0 | /1.0 | /1.0 |

### Retrospective

**What did we learn?**
- [Learning 1]
- [Learning 2]

**What would we do differently?**
- [Change 1]
- [Change 2]

**How should this inform next quarter?**
- [Recommendation 1]
- [Recommendation 2]
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall