From qe-framework
Guides OKR creation from objective brainstorming through SMART validation to initiative mapping. Use for quarterly goals, key results, and connecting objectives to roadmap execution.
How this skill is triggered — by the user, by Claude, or both
Slash command
/qe-framework:Qpm-okrThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Distinct from:** Qpm-roadmap (work sequence), Qpm-strategy (market analysis). This skill defines measurable objectives and key results (OKRs) that answer "where do we want to go?" and validates they are SMART. It does not sequence execution into quarters (see /Qpm-roadmap) or perform market/competitive analysis (see /Qpm-strategy). OKRs set *direction*; roadmaps execute it.
Distinct from: Qpm-roadmap (work sequence), Qpm-strategy (market analysis). This skill defines measurable objectives and key results (OKRs) that answer "where do we want to go?" and validates they are SMART. It does not sequence execution into quarters (see /Qpm-roadmap) or perform market/competitive analysis (see /Qpm-strategy). OKRs set direction; roadmaps execute it.
Guide OKR creation from objective brainstorming through key result validation to initiative mapping. Ensures OKRs are aspirational yet measurable, connected to roadmap execution, and free of common anti-patterns.
An Objective answers: "Where do we want to go?"
Rules:
Prompt questions:
A Key Result answers: "How do we know we got there?"
Rules:
Formula:
[Verb] [metric] from [current baseline] to [target] by [date]
An Initiative answers: "What will we do to move the needle?"
Rules:
Run this check for every Key Result before finalizing:
| Criterion | Question | Pass? |
|---|---|---|
| Specific | Is it clear what is being measured? No ambiguity? | |
| Measurable | Is there a number with a current baseline and target? | |
| Achievable | Is 70% completion realistic with available resources? | |
| Relevant | Does achieving this KR meaningfully advance the Objective? | |
| Time-bound | Is there a clear deadline (quarter end or specific date)? |
If any criterion fails, rewrite the KR before proceeding.
OKRs set direction; roadmaps define execution. Connect them explicitly:
Objective (quarterly goal)
└─ Key Result (measurable outcome)
└─ Initiative (project/epic on roadmap)
└─ Sprint Goals (2-week milestones)
└─ User Stories (development tasks)
Connection rules:
Alignment check questions:
## Objective: [qualitative goal]
**Owner:** [team or person]
**Quarter:** [Q1/Q2/Q3/Q4 YYYY]
### Key Results
- KR1: [metric] from [current] to [target] by [date]
- KR2: [metric] from [current] to [target] by [date]
- KR3: [metric] from [current] to [target] by [date]
### Initiatives
- [ ] Initiative A → drives KR1
- [ ] Initiative B → drives KR1, KR2
- [ ] Initiative C → drives KR3
### Mid-Quarter Check-in
| KR | Baseline | Current | Target | Confidence |
|----|----------|---------|--------|------------|
| KR1 | | | | |
| KR2 | | | | |
| KR3 | | | | |
## Objective: Make onboarding so smooth that new users succeed on their own
**Owner:** Growth Team
**Quarter:** Q2 2025
### Key Results
- KR1: Increase Day-7 activation rate from 34% to 50% by Jun 30
- KR2: Reduce median time-to-first-value from 12 min to 5 min by Jun 30
- KR3: Decrease onboarding support tickets from 180/week to 80/week by Jun 30
### Initiatives
- [ ] Redesign onboarding wizard with progressive disclosure → drives KR1, KR2
- [ ] Add interactive product tour for top 3 use cases → drives KR1, KR2
- [ ] Build self-service knowledge base with video walkthroughs → drives KR3
- [ ] Implement onboarding health score email triggers → drives KR1
User: Help me write OKRs for next quarter
User: Help me brainstorm OKRs
User: Set quarterly goals and write key results
User: Review my OKRs and check if they're SMART
Credits: Frameworks adapted from phuryn/pm-skills (MIT)
npx claudepluginhub inho-team/qe-framework --plugin qe-frameworkCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.