What Are the OKR and Roadmap Skills in PM Skills? A Technical Deep Dive

The PM Skills repository provides two core execution skills—brainstorm-okrs and outcome-roadmap—that encode proven product management frameworks into reusable AI prompts, accessible via the /plan-okrs and /transform-roadmap slash commands.

The phuryn/pm-skills repository ships a modular collection of AI-powered product management capabilities. Among its most powerful features are the OKR and roadmap skills in PM Skills, which automate the creation of outcome-focused OKRs and strategic roadmaps through structured prompt engineering.

The Brainstorm OKRs Skill

Skill Functionality and Purpose

Located at pm-execution/skills/brainstorm-okrs/SKILL.md, the brainstorm-okrs skill guides product managers through a structured framework for creating team-level Objectives and Key Results. The skill prompts users for qualitative objectives, measurable key results, and alignment with company goals, then formats the output into a concise, outcome-focused structure.

According to the source code, this skill is typically invoked by the /plan-okrs command, which serves as a thin wrapper handling input parsing and output presentation.

Invoking the OKR Skill

To trigger the OKR generation workflow, use the built-in slash command:

/plan-okrs

The skill executes a guided interview process that collects:

• Company-level objectives for alignment
• Team focus areas
• Quantifiable metrics for key results

The output follows a standardized format:

Objective: Increase user activation
  • KR1: Boost Day‑1 activation rate from 45 % to 60 %
  • KR2: Reduce onboarding friction score by 30 %
  • KR3: Launch two new activation‑driven features

The Outcome Roadmap Skill

Transforming Output-Focused Roadmaps

The outcome-roadmap skill, defined in pm-execution/skills/outcome-roadmap/SKILL.md, rewrites traditional feature-list roadmaps into outcome-focused strategic documents. Rather than listing deliverables ("Add tutorial page"), it articulates why each initiative matters by framing initiatives around user and business impact.

This skill is invoked through the /transform-roadmap command, which processes uploaded roadmap documents (plain text, CSV, or other formats) and applies the outcome transformation logic.

Invoking the Roadmap Transformation

Trigger the skill using the slash command:

/transform-roadmap

The skill accepts various input formats and produces an outcome-centric structure:

Outcome 1 – Accelerate customer onboarding
  • Deliver a self‑service tutorial (instead of “Add tutorial page”)
  • Implement auto‑email onboarding series
  • Reduce time‑to‑first‑value from 7 days to 3 days

Outcome 2 – Boost product adoption in the enterprise segment
  • Launch multi‑tenant reporting dashboard
  • Add role‑based access controls
  • Increase enterprise NPS by 12 pts

Architecture and File Locations

Both skills are implemented as standalone markdown specifications within the pm-execution plugin. The architecture separates the core skill logic from command wrappers:

• brainstorm-okrs skill: pm-execution/skills/brainstorm-okrs/SKILL.md
• outcome-roadmap skill: pm-execution/skills/outcome-roadmap/SKILL.md
• OKR command wrapper: pm-execution/commands/plan-okrs.md
• Roadmap command wrapper: pm-execution/commands/transform-roadmap.md

The command files are thin wrappers that call the underlying skills, handling input parsing (such as document uploads) and formatting the skill output for the user interface.

Summary

• The OKR and roadmap skills in PM Skills comprise two core capabilities: brainstorm-okrs and outcome-roadmap.
• The brainstorm-okrs skill in pm-execution/skills/brainstorm-okrs/SKILL.md generates team-level OKRs through guided prompts.
• The outcome-roadmap skill in pm-execution/skills/outcome-roadmap/SKILL.md transforms feature lists into outcome-focused roadmaps.
• Both skills are invoked via slash commands (/plan-okrs and /transform-roadmap) that wrap the underlying skill definitions.
• These skills are standalone and can be called directly by Claude models or automated systems.

Frequently Asked Questions

How do I invoke the OKR skill in PM Skills?

Use the /plan-okrs slash command, which wraps the brainstorm-okrs skill defined in pm-execution/skills/brainstorm-okrs/SKILL.md. The command handles input parsing and returns a formatted OKR list after guiding you through company objectives and measurable key results.

What is the difference between the skill file and the command file?

The skill file (e.g., SKILL.md) contains the core prompt engineering and framework logic that defines how the AI processes information. The command file (e.g., plan-okrs.md) is a thin wrapper that handles user interface concerns like input parsing and output formatting, then calls the underlying skill.

Can I use these skills without the slash commands?

Yes. Both brainstorm-okrs and outcome-roadmap are standalone skills that can be called directly by a Claude model or invoked programmatically. The slash commands are convenience wrappers that automate the invocation process for end users.

Where are the skill definitions stored in the repository?

The OKR skill definition lives at pm-execution/skills/brainstorm-okrs/SKILL.md, while the roadmap skill is located at pm-execution/skills/outcome-roadmap/SKILL.md. The corresponding command wrappers are in pm-execution/commands/plan-okrs.md and pm-execution/commands/transform-roadmap.md.

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