How the /plan-okrs Command Assists in Brainstorming Team-Level OKRs

The /plan-okrs command guides teams through a structured four-step workflow that transforms high-level company objectives into concrete, measurable team OKRs using the pm-skills toolkit.

The pm-skills repository by phuryn provides a declarative command framework for product management workflows. The /plan-okrs command, defined in pm-execution/commands/plan-okrs.md, orchestrates a complete OKR brainstorming session that ensures alignment between company strategy and team execution.

The Four-Step OKR Brainstorming Workflow

The command implements a tightly-coupled workflow that moves from context gathering to finalized output. According to the source code in pm-execution/commands/plan-okrs.md, the process follows four distinct phases.

Step 1: Context Gathering

The command initiates by collecting essential strategic context. It prompts users for the team or product area, time horizon, relevant company-level objectives, recent results, and any constraints. Users can also upload existing company OKR or strategy documents to provide additional context without manual entry.

Step 2: OKR Generation

The workflow invokes the brainstorm-okrs skill to produce three distinct OKR sets. Each set includes:

• One inspiring qualitative Objective
• 3-5 quantitative Key Results that are time-bound and measurable
• Direct alignment mapping to the company goal

This generation process ensures teams have multiple options to consider rather than a single forced choice.

Step 3: Quality Validation

Generated OKRs undergo automated validation against best-practice criteria. The command checks for inspiration, measurability, appropriate stretch, limited Key Results per Objective, and avoidance of gaming behaviors. When issues are detected, the system flags specific problems and offers concrete improvement suggestions.

Step 4: Presentation and Iteration

The final output renders in a ready-to-share table format complete with an alignment map, scoring guide, and check-in cadence. The command also proposes follow-up actions such as adjusting ambition levels, creating dashboards, or drafting stakeholder updates.

Command Syntax and Usage Examples

The /plan-okrs command accepts natural language input and supports document uploads for context-rich brainstorming sessions.

Basic Invocation

/plan-okrs Growth team Q2 — company goal is 50% ARR increase

Specify a Squad

/plan-okrs Onboarding squad aligned to "improve activation rate"

Upload a Strategy Document

/plan-okrs [upload company OKRs or strategy doc]

Typical Interaction Flow

User: /plan-okrs Growth team Q2 — 50% ARR increase
PM-Skills: What team or product area are these OKRs for?
User: Growth team
PM-Skills: What time period? (Quarterly standard)
User: Q2
PM-Skills: What are the company-level objectives to ladder up to?
User: Increase ARR by 50%
PM-Skills: (generates three OKR sets, validates them, and returns a formatted table)

Sample Output Format

The command produces structured markdown tables ready for immediate use:

## Team OKRs: Growth — Q2

**Aligned to**: Increase ARR by 50 %

### Objective 1: Expand high‑value customer acquisition

| # | Key Result                | Baseline | Target | Owner |

|---|---------------------------|----------|--------|-------|
| 1 | # of qualified leads      | 1 200    | 1 800  | Alice |

| 2 | Conversion rate (%)      | 12 %     | 18 %   | Bob   |
| 3 | New ARR ($M)              | 4.0      | 6.0    | Carol |

Architecture and Extensibility

Because the workflow is declarative (written entirely in markdown), the /plan-okrs command offers unique architectural advantages. The command definition in pm-execution/commands/plan-okrs.md specifies the description, expected arguments, and workflow orchestration without underlying code changes.

This design provides:

• Consistency – Every team uses the same OKR framework, ensuring alignment across the organization
• Guided Interaction – Step-by-step prompts eliminate ambiguity and surface context needed for high-quality OKRs
• Extensibility – New validation rules or additional prompts can be added by editing the markdown file directly

The pm-execution/README.md lists this command among other execution-level tools, while the main README.md provides the high-level toolkit overview showing /plan-okrs under "Available Commands".

Summary

• The /plan-okrs command in phuryn/pm-skills provides a structured four-step workflow for brainstorming team-level OKRs
• Context gathering captures team details, time horizons, and company objectives before generation begins
• The brainstorm-okrs skill produces three complete OKR sets with measurable Key Results aligned to company goals
• Automated quality validation checks against best practices including measurability and appropriate stretch
• Declarative markdown architecture allows workflow customization without code changes via pm-execution/commands/plan-okrs.md

Frequently Asked Questions

What inputs does the /plan-okrs command require?

The command requires the team or product area, time horizon (typically quarterly), and company-level objectives to align against. Users can also provide recent results, constraints, and upload strategy documents for additional context. All inputs are gathered through interactive prompts rather than complex syntax.

How does the command ensure OKR quality?

The validation step checks generated OKRs against five criteria: inspiration, measurability, appropriate stretch, limited Key Results per Objective (3-5 maximum), and avoidance of gaming behaviors. When checks fail, the system provides specific improvement suggestions rather than generic feedback.

Can the workflow be customized without coding?

Yes. Because the command logic lives in pm-execution/commands/plan-okrs.md as declarative markdown, you can modify prompts, add validation rules, or adjust the workflow steps by editing that file. No recompilation or code deployment is required, making it accessible to product managers who need to adapt the tool to their organization's specific OKR framework.

Where is the command logic defined?

The primary definition resides in pm-execution/commands/plan-okrs.md, which specifies the four-step workflow and orchestrates calls to the brainstorm-okrs skill. Supporting documentation appears in pm-execution/README.md and the root README.md, which categorize the command under execution-level tools in the pm-skills toolkit.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}