# Product Strategy

> Use when building product strategy, roadmaps, or strategic plans — vision articulation, strategic bet definition, roadmap sequencing, resource allocation, portfolio planning, or quarterly/annual planning. Encodes bet-sizing, option-value sequencing, strategic tension surfacing, and explicit deprioritization. Produces a strategy document, not a feature backlog.

- **Type:** Skill
- **Install:** `agentstack add skill-avyayalaya-pm-skills-arsenal-product-strategy`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Avyayalaya](https://agentstack.voostack.com/s/avyayalaya)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Avyayalaya](https://github.com/Avyayalaya)
- **Source:** https://github.com/Avyayalaya/pm-skills-arsenal/tree/main/skills/product-strategy
- **Website:** https://avyayalaya.github.io/pm-skills-arsenal/

## Install

```sh
agentstack add skill-avyayalaya-pm-skills-arsenal-product-strategy
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

## Purpose

Produce an elite-tier strategic product roadmap that articulates a falsifiable vision, sizes and sequences strategic bets with explicit confidence levels, surfaces tensions between competing priorities, names what you are NOT doing and what that costs, allocates resources against capacity constraints, and sets quarterly gates with kill criteria. The output is a Strategy Document — not a feature backlog, not a Gantt chart, but a decision architecture that tells a team what to build, in what order, why, and what to stop doing.

## When to Use / When NOT to Use

**Use this skill when:**
- Building or revising a product roadmap for a quarter, half, or year
- Articulating product vision and translating it to executable strategy
- Running annual or quarterly planning exercises
- Making portfolio allocation decisions across multiple investment areas
- A leadership review requires a strategy document with clear bets and sequencing rationale
- You need to explicitly communicate what you are NOT doing and why

**Do NOT use this skill when:**
- You need competitive intelligence to inform the strategy (use Competitive Market Analysis skill first — its output feeds this skill)
- You need to write a specification for a specific feature (use Specification Writing skill — this skill's output feeds that one)
- You need to define metrics for measuring success of shipped features (use Metric Design & Experimentation skill)
- You need to understand a problem before deciding what to build (use Problem Framing skill — that comes upstream)
- You need a project plan with task-level assignments and sprint breakdowns (this is strategy, not project management)

**Anti-inputs (what this skill does NOT handle):**
- Feature specifications or PRDs (downstream: Specification Writing skill)
- Sprint planning or task decomposition (execution layer, not strategy layer)
- Competitive analysis (upstream: Competitive Market Analysis skill)
- User research synthesis (upstream: Discovery Research skill)
- OKR writing (adjacent but distinct — this skill produces the strategy that OKRs measure)

## Example

**Prompt:** We have a $12M ARR async video platform with 2M users. Board wants 40% growth. We can improve our video editor (churn), build AI meeting summaries (growth), or launch a team knowledge base (moat). We have 12 engineers, 3 PMs, 2 designers — no new hires this half. Build a 6-month strategy with explicit bets, sequencing, and resource allocation.

**Output excerpt** (full output is 2,000-5,000 words):

> **Executive Summary:** Current usage pattern: 68% of recordings watched once, 23% never watched, only 9% watched 3+ times (T1). The product is a "record and forget" tool. **AI meeting summaries is the highest-conviction bet because it converts users from a recording tool (used once) to an intelligence layer (used daily).**
>
> | Bet | Hypothesis | Confidence | Investment | Kill Criteria |
> |---|---|---|---|---|
> | AI Meeting Intelligence | AI summaries increase engagement from 1.8x/week to 4.5x/week | H | 55% (6 eng, 2 PMs) | AI summary open rate  | Editor Hardening | Reduce churn from 5.2% to 3.8% monthly | H | 30% (4 eng) | N/A — core reliability not optional |
> | Knowledge Base MVP | Searchable meeting artifacts enable new $25/user tier | L | 15% (2 eng) | AI summary adoption =3 named exclusions, the Resource Plan sums to 70%), M (40-70%), L (6 months old — verify before presenting |
| `[RESOURCE-UNCONSTRAINED]` | Strategy was built without confirmed resource constraints |
| Core / Adjacent / Transformational | Bet categories: Core protects base (H confidence), Adjacent expands (M), Transformational creates new (L) |
| **Deferred / Declined / Deprecated** | NOT-Doing taxonomy: doing later / decided against / actively stopping |

---

## Format Rules (Read First)

These rules govern every output produced by this codex. They are quality enforcement mechanisms, not style preferences.

1. **Take positions. Never hedge with weasel words.** "Likely," "may," "could," and "seems" are banned from strategic conclusions. Flag uncertainty with explicit confidence levels: **H (>70% confident)**, **M (40-70%)**, **L ( **Date:** [YYYY-MM-DD] | **Time horizon:** [quarterly/half/annual/multi-year] | **Confidence band:** [Overall H/M/L] | **Next review:** [Date]

---

## Executive Summary

[≤300 words. Zero jargon. A VP reads only this and makes a resource allocation decision. Final sentence = the recommended strategic direction in bold. Written LAST, appears FIRST.]

---

## Step 0: Framework Selection

| Strategy question type | Primary frameworks (apply in full) | Supporting frameworks (scan only) | Skipped (why) |
|---|---|---|---|
| [e.g., "Annual roadmap for established product"] | [e.g., Vision-to-Roadmap Cascade, Strategic Bet-Sizing, Option-Value Sequencing] | [e.g., Resource Allocation, Roadmap Communication] | [e.g., "N/A — all frameworks load-bearing for annual planning"] |

---

## 1. Vision Statement

[1-2 sentences. Aspirational but falsifiable. Not "be the best" but "become the default X for Y in Z timeframe."]

**Falsification test:** [What observable outcome in what timeframe would prove this vision wrong?]

---

## 2. Strategy Pillars

| # | Pillar | Strategic intent | Maps to vision how |
|---|--------|-----------------|-------------------|
| P1 | [Theme name — not a feature, not an initiative] | [What this pillar achieves strategically] | [How it advances the vision] |
| P2 | | | |
| P3 | | | |

---

## 3. Strategic Bets

### Bet 1: [Name]
- **Pillar:** [Which pillar this serves]
- **Category:** Core / Adjacent / Transformational
- **Hypothesis:** If we [specific investment], then [measurable outcome] because [mechanism]
- **Confidence:** [H/M/L] — based on [evidence summary with tier]
- **Investment:** [X engineers, Y designers, Z months] = [% of total capacity]
- **Success criteria:** [Specific, measurable, time-bound]
- **Kill criteria:** [What observable outcome at what checkpoint tells us to stop]
- **Key assumption:** [The one thing that must be true for this bet to pay off]

### Bet 2: [Name]
[Same structure]

### Bet 3: [Name]
[Same structure]

**Portfolio Balance Check:**

| Category | Count | % of investment | Target range | Assessment |
|----------|:-----:|:---------------:|:------------:|:----------:|
| Core | | | 50-70% | |
| Adjacent | | | 20-30% | |
| Transformational | | | 5-15% | |

---

## 4. Sequencing Rationale

| Sequence | Bet | Rationale type | Counterfactual |
|:--------:|-----|---------------|----------------|
| 1st | [Bet name] | [Dependency / Information / Option-value / Risk / Revenue] | If we did [other bet] first, [specific consequence] |
| 2nd | | | |
| 3rd | | | |

**Critical path:** [Which bet, if delayed, delays everything else]

**Information gates:** [Which bets reveal information that changes other bets' value]

---

## 5. Strategic Tensions

| Tension | Bet A | Bet B | Type | Resolution | What we lose |
|---------|-------|-------|------|------------|--------------|
| [Name] | [Bet] | [Bet] | Resource / Strategic / Timing | [How resolved + rationale] | [Cost of this resolution] |

**Strategic debt created:** [What speed/quality/scope tradeoff creates debt that must be repaid, and when]

---

## 6. What We Are NOT Doing

| # | Item | Category | Why not | What we lose | Reconsider if |
|---|------|----------|---------|-------------|---------------|
| 1 | [Specific initiative/feature/market] | Deferred / Declined / Deprecated | [Reasoning] | [Opportunity cost — not zero] | [Observable condition] |
| 2 | | | | | |
| 3 | | | | | |

**Stakeholder communication:** [How to explain the NOT-doing decisions to affected teams/customers without demoralizing or angering]

---

## 7. Resource Plan

**Capacity model:**

| Team/Function | Total headcount | Planned (70%) | Reactive (20%) | Exploration (10%) | Override? |
|--------------|:---------------:|:-------------:|:---------------:|:-----------------:|:---------:|
| Engineering | | | | | |
| Design | | | | | |
| PM | | | | | |

**Per-bet allocation:**

| Bet | Eng | Design | PM | Duration | Monthly burn | Dependencies on other teams |
|-----|:---:|:------:|:--:|:--------:|:------------:|:-------------------------:|
| [Bet 1] | | | | | | |
| [Bet 2] | | | | | | |

**Hiring implications:** [Which bets require hiring? Lead time? What happens if hiring is delayed?]

**Capacity check:** [Does the sum of all allocations exceed 70% planned capacity? If yes, something must be cut or deferred.]

---

## 8. Quarterly Gates

| Quarter | Primary bet focus | Gate criteria (pass/fail) | Adaptation triggers | Kill criteria |
|---------|------------------|--------------------------|--------------------|--------------|
| Q1 | [Bet name] | [Specific, measurable criteria] | [What signal tells us to adjust scope/direction] | [What tells us to stop entirely] |
| Q2 | | | | |
| Q3 | | | | |
| Q4 | | | | |

**Replanning protocol:** [How and when the strategy gets revised — monthly check-ins, quarterly deep-dives, trigger-based emergency reviews]

---

## 9. Roadmap Communication Views

| Audience | View | Emphasis | Omit |
|----------|------|----------|------|
| Executive | Bets + business outcomes + confidence | Investment sizing, portfolio balance | Technical details, sprint-level scope |
| Engineering | Dependencies + technical architecture + sequencing | Build sequence, integration points | Business rationale beyond what's needed for decisions |
| Design | User outcomes per bet + experience evolution | Success criteria from user perspective | Resource math, financial projections |
| Sales/GTM | Customer-facing capabilities + competitive positioning | Timeline for customer-visible features | Internal bets, platform investments |

---

## 10. Strategic Recommendations (O→I→R→C→W Cascade)

**Recommendation 1: [Title]**
- **Observation** [TX]: [What we see]
- **Implication**: [Why it matters — the mechanism]
- **Response**: [Specific action + owner + timeline]
- **Confidence**: [H/M/L] — assumes [key assumption]
- **Watch**: [Observable signal]; if [threshold], re-assess

**Recommendation 2: [Title]**
[Same structure]

**Recommendation 3: [Title]**
[Same structure]

---

## Assumption Registry

| # | Assumption | Bets it underpins | Confidence | Evidence | What would invalidate this |
|---|-----------|-------------------|:----------:|----------|----------------------------|
| 1 | | | H/M/L | (TX) | |
| 2 | | | H/M/L | (TX) | |
| 3 | | | H/M/L | (TX) | |

---

## Adversarial Self-Critique

**Weakness 1: [Title]**
[What assumption is being made? What evidence would disprove it? Scenario where this strategy is catastrophically wrong.]

**Weakness 2: [Title]**
[Same depth]

**Weakness 3: [Title]**
[Same depth]

---

## Revision Triggers

| Trigger | What to re-assess | Timeline |
|---------|-------------------|----------|
| [Observable event] | [Which bets/sections break] | [When to check] |

---

## Sources

[All sources cited in the analysis, with evidence tier and date.]
```

**Rules for using this template:**
1. **Do not skip sections.** If a section isn't applicable, write "Skipped — [reason]" and move on.
2. **Every strategic bet must have a hypothesis, confidence level, AND investment size** — no exceptions.
3. **Section headers are conclusions, not labels.** Replace generic headers (e.g., "Q2 Gate") with insight headers (e.g., "Q2: Kill or Double Down on Enterprise Expansion") after completing the section.
4. **The Executive Summary is written last** but appears first. Do not write it until all sections are complete.
5. **The NOT-Doing section must contain ≥3 items.** An empty NOT-Doing section means no hard decisions were made.

---

## Domain Frameworks

> This section IS the knowledge weapon. Each framework is encoded with its scoring rubrics, decision tables, and application methodology — not merely referenced. A PM using this skill produces a strategy document that requires these frameworks; without them, the output degrades to a feature backlog with dates.

### Framework 1: Vision-to-Roadmap Cascade

The structural bridge from aspiration to execution. Most strategies fail at one of two gaps: (1) vision that never translates to bets, or (2) bets that don't trace back to a coherent vision. The cascade makes both gaps impossible to hide.

**The Five Levels:**

| Level | What it is | What it is NOT | Quality test |
|-------|-----------|---------------|-------------|
| **Vision** | 1-2 sentences. Aspirational but falsifiable. Defines what winning looks like in a specific timeframe. | A mission statement. "Be the best" is not a vision — it's a bumper sticker. | Can you name a specific observable outcome in a specific timeframe that would prove the vision wrong? If not, it's not falsifiable. |
| **Strategy Pillars** | 3-5 themes that bridge vision to execution. Each pillar is a strategic direction, not an initiative. | Feature areas. "AI-powered search" is a pillar. "Add vector search to API" is an initiative. | Remove one pillar. Does the vision become unreachable? If not, the pillar isn't load-bearing — cut it. |
| **Strategic Bets** | Specific investments under each pillar, each with a hypothesis, confidence level, and investment size. | Tasks. "Hire 3 engineers" is a resource action. "Win the mid-market analytics segment by building self-serve onboarding" is a bet. | Does each bet have a testable hypothesis? An explicit confidence level? A named investment? If any are missing, it's a wish, not a bet. |
| **Sequencing** | Which bets first, which later, and why. Dependency logic, information value, option preservation. | Gut priority. "We feel this is more important" is not sequencing. "A must come before B because A's outcome determines whether B is worth doing" is sequencing. | Every sequence decision states the counterfactual. "If we did B first, [consequence]." |
| **Quarterly Translation** | How the 12-month roadmap becomes this quarter's focus. What's in scope, what's deferred, what gates exist. | A sprint plan. Quarterly translation sets direction and success criteria. It does not assign story points. | At the end of the quarter, can you definitively say pass/fail against the gate criteria? If criteria are fuzzy, translation failed. |

**Vision Quality Rubric:**

| Rating | Criteria | Example |
|--------|----------|---------|
| 🟢 **Strong** | Falsifiable, time-bound, specific about the target state. A team member can explain what we're building toward without asking. | "Become the default analytics tool for mid-market SaaS companies (500-5000 employees) by FY28, measured by >25% market share in that segment." |
| 🟡 **Moderate** | Directional but not falsifiable. Points toward the right mountain but doesn't name the summit. | "Be the leading analytics platform for growing companies." |
| 🔴 **Weak** | Inspirational mush. Could apply to any company in any industry. No team member can derive what to build from it. | "Empower teams with data-driven insights to make better decisions." |

**Decision Table — Vision Clarity x Execution Certainty:**

| | Execution certainty HIGH | Execution certainty LOW |
|---|---|---|
| **Vision clarity HIGH** | **Execution Roadmap.** Clear bets, aggressive timelines, detailed resource plans. The strategy is a commitment. | **Exploration Roadmap.** Clear destination, uncertain path. Strategy emphasizes information-gathering bets and option preservation. Quarterly gates are adaptation points, not accountability checkpoints. |
| **Vision clarity LOW** | **Pivot Roadmap.** You can build but don't know what to build toward. Strategy is a series of validated experiments, each narrowing the vision. Time-boxed: 1-2 quarters max before vision must crystallize or the initiative gets killed. | **Discovery Mode.** Neither destination nor path is clear. This is not a strategy question — it's a Problem Framing question. Use Problem Framing skill instead. Do not build a roadmap on sand. |

---

### Framework 2: Strategic

…

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Avyayalaya](https://github.com/Avyayalaya)
- **Source:** [Avyayalaya/pm-skills-arsenal](https://github.com/Avyayalaya/pm-skills-arsenal)
- **License:** MIT
- **Homepage:** https://avyayalaya.github.io/pm-skills-arsenal/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-avyayalaya-pm-skills-arsenal-product-strategy
- Seller: https://agentstack.voostack.com/s/avyayalaya
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.