pm-pmm

What this skill does

# PM/PMM Skill

> **Version:** 1.0.0
> **Framework:** Jerry PM/PMM Decision Framework
> **Constitutional Compliance:** Jerry Constitution v1.0
> **SSOT Reference:** `.context/rules/quality-enforcement.md`
> **Architecture Reference:** PROJ-018 Issue #123

## Document Audience (Triple-Lens)

| Level | Audience | Sections to Focus On |
|-------|----------|---------------------|
| **L0 (ELI5)** | New users, stakeholders | [Purpose](#purpose), [When to Use](#when-to-use-this-skill), [Quick Reference](#quick-reference) |
| **L1 (Engineer)** | Developers invoking agents | [Available Agents](#available-agents), [Invoking an Agent](#invoking-an-agent), [Discovery vs Delivery Mode](#discovery-vs-delivery-mode), [Framework Catalog](#framework-catalog) |
| **L2 (Architect)** | Workflow designers | [P-003 Compliance](#p-003-compliance), [Cross-Agent Data Flow](#cross-agent-data-flow), [Integration Points](#integration-points-with-other-skills), [Artifact Ownership Matrix](#artifact-ownership-matrix) |

---

## Purpose

The PM/PMM skill provides a **decision-focused product management and product marketing capability** for the Jerry Framework. It helps PMs and PMMs make better product decisions by ensuring every decision is grounded in evidence, structured by proven frameworks, and documented as a living artifact.

### What It Does

- **Product Strategy:** Creates PRDs, product vision documents, roadmaps, and use case specifications grounded in JTBD, RICE, Kano, Playing to Win, and Opportunity Solution Tree frameworks
- **Customer Insight:** Builds JTBD-oriented personas, customer journey maps with Moments of Truth, and VOC research reports synthesized from interview data
- **Business Analysis:** Produces business cases, TAM/SAM/SOM market sizing, and pricing strategy analysis using Van Westendorp, Lean Canvas, and SaaS financial metrics
- **Competitive Intelligence:** Delivers competitive analysis with Porter's Five Forces, Blue Ocean value curves, battle cards with talk tracks, and win/loss pattern analysis
- **Go-to-Market:** Creates GTM plans with Dunford positioning, MRDs, and buying-committee buyer personas

### Core Design Principles

1. **Cagan's Two Risks:** Organized around Value Risk ("Will they buy/use it?") and Business Viability Risk ("Does it work for the business?"). Usability Risk and Feasibility Risk are out of scope.
2. **Discovery Before Delivery:** Every agent defaults to discovery mode. Validates assumptions cheaply before committing to polished artifacts.
3. **18 Validated Frameworks:** Not name-drops -- each framework is operationalized with methodology steps that produce canonical output structures.
4. **Evidence, Not Intuition:** All claims require evidence citations or explicit hypothesis marking with confidence levels.

---

## When to Use This Skill

**Activate when:**

- Building a new product or feature and need to define what to build and why
- Creating or updating product requirements (PRDs) with prioritization frameworks
- Understanding customers through personas, journey maps, or VOC research
- Assessing business viability through business cases, market sizing, or pricing analysis
- Analyzing the competitive landscape or creating battle cards
- Planning go-to-market strategy, positioning, messaging, or launch execution
- Needing structured product/market frameworks rather than ad-hoc analysis

**Do NOT use when:**

- Writing code, designing architecture, or making technical implementation decisions (use `/architecture` or `/eng-team`)
- Running adversarial quality reviews on deliverables (use `/adversary`)
- Performing root cause analysis on bugs or failures (use `/problem-solving`)
- Creating UX wireframes or design specifications (out of scope -- Usability Risk)
- Managing work items or tracking project status (use `/worktracker`)
- Parsing transcripts or meeting notes (use `/transcript`)
- Deploying, testing, or managing CI/CD (use `/eng-team`)

### Negative Keywords (Prevent False Routing)

These keywords in a request should suppress `/pm-pmm` routing:

| Keyword | Routes To Instead |
|---------|-------------------|
| code review | `/problem-solving` or `/eng-team` |
| architecture, ADR | `/architecture` |
| engineering, implementation | `/eng-team` |
| deployment, CI/CD | `/eng-team` |
| testing, test coverage | `/eng-team` |
| infrastructure pricing, cloud pricing | `/eng-team` (not product pricing) |
| adversarial, tournament | `/adversary` |
| transcript, VTT, SRT | `/transcript` |
| penetration test, exploit | `/red-team` |

---

## Available Agents

| Agent | Decision Question | Risk Domain | Model | Status |
|-------|------------------|-------------|-------|--------|
| `pm-product-strategist` | "What should we build, and why?" | Value + Viability (strategy) | opus | **Tier 1 -- Active** |
| `pm-customer-insight` | "Who are our customers, and what do they need?" | Value Risk | opus | **Tier 1 -- Active** |
| `pm-market-strategist` | "How do we bring this to market?" | Viability Risk (GTM) | opus | **Tier 1 -- Active** |
| `pm-business-analyst` | "Is this worth investing in?" | Viability Risk (financial) | sonnet | **Tier 2 -- Active** |
| `pm-competitive-analyst` | "Who are we up against?" | Viability Risk (market) | sonnet | **Tier 2 -- Active** |

### Agent-to-Artifact Ownership

| Agent | Primary Artifacts | Count |
|-------|-------------------|-------|
| pm-product-strategist | PRD, Product Vision, Roadmap, Use Cases | 4 |
| pm-customer-insight | User Personas, Customer Journey Maps, VOC Research Reports | 3 |
| pm-market-strategist | GTM Plan, MRD, Buyer Personas | 3 |
| pm-business-analyst | Business Case, Market Sizing (TAM/SAM/SOM) | 2 |
| pm-competitive-analyst | Competitive Analysis, Battle Cards, Win/Loss Analysis | 3 |
| **Total** | | **15** |

### Agent Selection Hints

| User Says | Route To | Rationale |
|-----------|----------|-----------|
| "Write a PRD" / "product requirements" / "roadmap" / "prioritize features" | pm-product-strategist | Owns all product requirements and prioritization artifacts |
| "Create personas" / "journey map" / "customer interviews" / "VOC" / "pain points" | pm-customer-insight | Owns user personas, journey maps, VOC research |
| "GTM plan" / "positioning" / "messaging" / "buyer persona" / "launch plan" | pm-market-strategist | Owns GTM, MRD, buyer personas |
| "Business case" / "TAM" / "market sizing" / "pricing model" / "unit economics" | pm-business-analyst | Owns business cases, market sizing, pricing analysis |
| "Competitive analysis" / "battle card" / "win/loss" / "Porter's" / "SWOT" | pm-competitive-analyst | Owns competitive analysis, battle cards, win/loss reports |

---

## P-003 Compliance

All PM/PMM agents are **workers**, NOT orchestrators. The MAIN CONTEXT (Claude session) orchestrates all workflows.

```
P-003 AGENT HIERARCHY:
======================

  +-------------------+
  | MAIN CONTEXT      |  <-- Orchestrator (Claude session)
  | (orchestrator)    |
  +-------------------+
     |        |        |
     v        v        v
  +------+ +------+ +------+
  | pm-  | | pm-  | | pm-  |   <-- Tier 1 Workers
  |prod- | |cust- | |mkt-  |
  |strat | |insght| |strat |
  +------+ +------+ +------+

  +------+ +------+
  | pm-  | | pm-  |   <-- Tier 2 Workers (Active)
  |biz-  | |comp- |
  |anlst | |anlst |
  +------+ +------+

  - Agents CANNOT invoke other agents.
  - Agents CANNOT spawn subagents.
  - Agents do NOT have the Task tool.
  - Only MAIN CONTEXT orchestrates the sequence.
  - All cross-agent data flows through file artifacts.
```

---

## Invoking an Agent

### Option 1: Natural Language Request

Simply describe what you need:

```
"Create a PRD for the self-service onboarding feature"
"Build personas for our platform engineering customers"
"Create a GTM plan with positioning for our developer platform"
"Help me prioritize these features using RICE"
"Map the customer journey for enterprise onboarding"
"Write an MRD for the APAC market expansion"
```