home / skills / kriscard / kriscard-claude-plugins / product-strategist

product-strategist skill

/plugins/architecture/skills/product-strategist

This skill guides strategic product leadership from vision to OKR alignment, prioritization, and org design to accelerate outcomes.

npx playbooks add skill kriscard/kriscard-claude-plugins --skill product-strategist

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.6 KB
---
name: product-strategist
description: Strategic product leadership for vision setting, OKR alignment, market analysis, and product team scaling. Use PROACTIVELY for strategic planning, goal setting, competitive analysis, or product org design.
---

# Product Strategist

Strategic product leadership. Connect business outcomes to product initiatives.

## Core Frameworks

- **OKRs**: Objectives and Key Results for goal alignment
- **RICE**: Reach, Impact, Confidence, Effort for prioritization
- **Jobs-to-be-Done**: Customer motivation over feature requests
- **North Star Metric**: Single metric capturing core value delivery

## OKR Cascade

```
Company OKR
  └── Product OKR (contributes 30-50%)
        └── Team OKR (contributes 20-40%)
              └── Individual goals

Alignment check: Every team OKR should trace to company objectives.
```

## Strategy Types

| Strategy | Focus | Key Metrics |
|----------|-------|-------------|
| Growth | Acquisition, expansion | MAU, signups, activation |
| Retention | Engagement, loyalty | Churn, NPS, DAU/MAU |
| Revenue | Monetization | ARPU, LTV, conversion |
| Innovation | New markets | Experiments, time-to-market |

## RICE Prioritization

```
RICE Score = (Reach × Impact × Confidence) / Effort

Reach:      Users affected per quarter
Impact:     0.25 (minimal) → 3 (massive)
Confidence: 50% → 100%
Effort:     Person-weeks
```

## Team Structure

```
Product Org Ratios:
- PM:Engineers        = 1:8-10
- Designer:PM         = 1:2
- Researcher:PM       = 1:4-6

Squad composition:
- 1 PM + 1 Designer + 4-8 Engineers
```

## Avoid

- OKRs without measurable key results
- Roadmaps as feature lists (focus on outcomes)
- Shipping without success metrics defined
- Copying competitors without understanding why
- PM:Engineer ratio below 1:12

## OKR Template

```markdown
## Objective: [Qualitative, inspiring goal]

KR1: [Metric] from [baseline] to [target]
KR2: [Metric] from [baseline] to [target]
KR3: [Metric] from [baseline] to [target]

Confidence: [High/Medium/Low]
Dependencies: [Teams, resources needed]
```

## Product Vision (1-Pager)

```markdown
## For [target customer]
## Who [has this problem/need]
## Our product [solution category]
## That [key benefit]
## Unlike [alternatives]
## We [key differentiator]
```

## Competitive Analysis

```markdown
| Dimension | Us | Competitor A | Competitor B |
|-----------|-----|--------------|--------------|
| [Feature] | ✓/✗ | ✓/✗ | ✓/✗ |
| Pricing | $ | $$ | $$$ |
| Strength | | | |
| Weakness | | | |
```

Define outcomes, measure what matters, ship with conviction.

Overview

This skill delivers strategic product leadership to connect business outcomes with product initiatives. It guides vision setting, OKR alignment, market and competitive analysis, prioritization, and product org design. Use it to create measurable plans, align teams, and scale product delivery.

How this skill works

The skill applies proven frameworks—OKRs, RICE prioritization, Jobs-to-be-Done, and a North Star metric—to assess strategy and produce concrete artifacts. It generates OKR cascades, RICE-scored roadmaps, product vision one-pagers, and competitive matrices. It also recommends team structures and hiring ratios to support execution and scale.

When to use it

  • Setting or refreshing company and product vision
  • Creating or cascading OKRs across teams
  • Prioritizing initiatives with limited resources
  • Designing or scaling a product organization
  • Preparing competitive analysis for strategic decisions

Best practices

  • Frame objectives qualitatively and key results quantitatively to ensure measurability
  • Score initiatives using Reach, Impact, Confidence, and Effort for objective prioritization
  • Trace every team OKR back to company objectives to maintain alignment
  • Define success metrics and experiments before shipping features
  • Avoid roadmaps that are mere feature lists—focus on outcomes and customer jobs

Example use cases

  • Draft a company-to-team OKR cascade that shows contribution percentages
  • Prioritize a backlog using RICE to choose top bets for the quarter
  • Create a one-page product vision to align stakeholders and hiring decisions
  • Build a competitor comparison matrix for feature and pricing decisions
  • Recommend product org ratios and a squad template for a scaling startup

FAQ

How do I choose the North Star metric?

Select the single metric that best reflects core value delivered to customers and ties directly to long-term growth. Validate it with customer jobs and usage signals.

What’s an acceptable PM-to-engineer ratio?

Aim for roughly 1 PM per 8–10 engineers; avoid exceeding 1:12 to maintain product leadership quality.