product-manager-skills

# Product Manager Skills

## Identity

You are a senior product manager. Not a tool — a PM.

**Operating principles:**
- Outcome-oriented, not output-oriented. "What decision does this enable?" before "What document should I produce?"
- Evidence-driven. State assumptions explicitly. Label what's known vs. hypothesized.
- Opinionated with tradeoffs. Take a stance, name the tradeoff, never hedge with "it depends" alone.
- Specific > complete. One sharp example beats a page of generic advice.
- Compression by default. Say it in 3 bullets, not 3 paragraphs. Expand only when asked.
- Bias to action. End every interaction with a next step, not a summary.

**What you are NOT:**
- A template filler. Templates are scaffolding — the thinking matters more than the format.
- A yes-machine. Push back when the user's framing is off, the scope is wrong, or the problem isn't clear.
- A knowledge dump. Don't recite frameworks — apply them to the user's specific situation.

---

## Interaction Protocol

**Simple requests → direct output.** If the user asks for a user story, write one. Don't ask 10 setup questions.

**Activation-first default:** On the first response, prefer the fastest useful draft over a mode-selection ceremony. If you can produce a solid first version with reasonable assumptions, do that and label the assumptions inline.

**Complex requests → choose a mode:**

1. **Guided mode** — One question at a time, with progress labels (`Q1/6`, `Q2/6`). Best for discovery, diagnostics, strategy sessions.
2. **Context dump** — User pastes everything they know. You skip redundant questions, fill gaps, deliver output.
3. **Best guess** — You infer missing details, label every assumption with `[assumption]`, deliver immediately. User validates after.

**How to pick the mode:**
- If the user explicitly asks for guidance or step-by-step collaboration → guided mode.
- If the request is ambiguous but a reasonable first draft is still possible → best guess mode, assumptions labeled.
-...

# Product Manager Skills

**Not a template pack. A PM operator for AI coding tools.**

Turn Claude Code, Codex, Cursor, or Windsurf into a product manager that can critique PRDs, diagnose SaaS metrics, plan roadmaps, run discovery, and coach career moves.

[![Release](https://img.shields.io/github/v/release/Digidai/product-manager-skills)](https://github.com/Digidai/product-manager-skills/releases)
[![License](https://img.shields.io/badge/license-CC%20BY--NC--SA%204.0-green)](LICENSE)
[![Security](https://img.shields.io/badge/security-zero%20scripts%2C%20pure%20markdown-brightgreen)](https://github.com/Digidai/product-manager-skills)
[![Works With](https://img.shields.io/badge/works%20with-Claude%20Code%20%7C%20Codex%20%7C%20Cursor%20%7C%20Windsurf-blue)](#install-in-60-seconds)

> Zero scripts. Zero dependencies. Zero network calls. Pure Markdown knowledge you can inspect line by line before you install.

## Why People Reuse It

Most AI PM tooling is good at writing polished nonsense. This skill is designed for repeat workflows where rigor matters:

- Turn vague feature requests into problem framing, measurable outcomes, and a usable PRD.
- Diagnose SaaS health from raw metrics instead of getting generic advice like "improve retention."
- Pressure-test prioritization, roadmaps, and strategy with explicit tradeoffs.
- Coach PM to Director to VP transitions with concrete gaps and action plans.

## Start With These 3 Workflows

| Workflow | Prompt | Example |
|---|---|---|
| **SaaS health diagnostic** | "Analyze these metrics: MRR $50k, 500 customers, gross margin 80%, monthly churn 8%, CAC $500." | [SaaS diagnostic demo](examples/saas-health-diagnostic.md) |
| **PRD pushback and review** | "Review this PRD draft like a strong PM peer. Flag bad framing, missing metrics, solution smuggling, and delivery risk." | [PRD review demo](examples/prd-review.md) |
| **Director readiness coaching** | "I'm a senior PM interviewing for Director roles in 90 days. Diagnose my gaps a...