Slash Command

/objective-planning

Write OKRs (Objectives and Key Results) for a team or product area. Use at the start of a planning cycle to set ambitious, measurable goals that connect to company strategy.

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/pm-planning:objective-planning [team or product area] [quarter or timeframe]

Model invocable

No pre-commands

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

Writes OKRs for a team or product area. Connects ambition to measurable outcomes.

## Routing

- **Argument provided**: use as the team/area and timeframe. Write OKRs directly.
- **No argument**: ask questions below first.

## Questions (no argument)



## Output

**OKRs: [Team Name] — [Quarter/Year]**

*Ladders to: [company objective or theme]*

---

**Objective 1: [Inspiring, qualitative goal]**

| Key Result | Baseline | Target | Owner |
|-----------|---------|--------|-------|
| KR1: [specific, measurable outcome] | [current] | [target by end of period] | |
| KR2: [specific, measurable ...

Command Content

61 lines · ~500 tokens

Stats

Parent stars0

MaintenanceGood

Last CommitMay 11, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Actions

Routing

Argument provided: use as the team/area and timeframe. Write OKRs directly.
No argument: ask questions below first.

Questions (no argument)

Before I write the OKRs, a few questions:

1. What team or product area are these OKRs for?
2. What's the timeframe? (quarterly / annual)
3. What's the company-level goal or theme this team's OKRs should ladder to?
4. What's the biggest priority for this team this cycle?
5. What metrics does this team already own or influence?

Answer as many as you can.

Output

OKRs: [Team Name] — [Quarter/Year]

Ladders to: [company objective or theme]

Objective 1: [Inspiring, qualitative goal]

Key Result	Baseline	Target
KR1: [specific, measurable outcome]	[current]	[target by end of period]
KR2: [specific, measurable outcome]
KR3: [specific, measurable outcome]

Objective 2: [Inspiring, qualitative goal]

Key Result	Baseline	Target	Owner
KR1:
KR2:

OKR health check

Are these OKRs outcome-focused (not output-focused)?
Does each KR have a clear owner and measurable signal?
Would scoring 0.7 on these feel like a meaningful win?
Do these create clarity on what's NOT prioritized this cycle?

Style

Objectives should be inspiring and directional — not "increase revenue by 10%." Key Results should be measurable and not fully within one person's control (pure output metrics can be gamed). A KR is not "ship feature X" — it's "X% of users complete first workflow within 7 days."