# pm-workbench examples

These examples are not meant to be perfect final outputs.
They are meant to help a new reader understand:

- what kinds of PM situations `pm-workbench` handles well
- what output shape each workflow tends to produce
- what “good behavior” looks like from the skill

## Example index

### Clarification and decision quality

- [01 — Clarify a vague request](01-clarify-vague-request.md)
- [02 — Feature Evaluation Memo](02-feature-evaluation-memo.md)
- [06 — Decision Brief](06-decision-brief.md)
- [07 — Prioritization Stack](07-prioritization-stack.md)

### Artifact drafting and communication

- [03 — Executive Summary](03-exec-summary.md)
- [04 — PRD Lite](04-prd-lite.md)
- [08 — Roadmap One-Pager](08-roadmap-one-pager.md)
- [09 — Metrics Scorecard](09-metrics-scorecard.md)
- [20 — Launch readiness call](20-launch-readiness-call.md)
- [21 — Mixed signals operating review](21-mixed-signals-operating-review.md)

### Product-leader / founder scenarios

- [10 — Product leader quarterly priority call](10-product-leader-quarterly-priority-call.md)
- [11 — Founder strategy decision](11-founder-strategy-decision.md)
- [12 — Portfolio Review Summary](12-portfolio-review-summary.md)
- [13 — Head of Product Operating Review](13-head-of-product-operating-review.md)
- [14 — Founder Business Review](14-founder-business-review.md)

### High-tension case studies

- [15 — Boss says the product needs more wow factor](15-case-study-boss-wow-factor.md)
- [16 — Ops wants an AI gimmick feature](16-case-study-gimmick-feature.md)
- [17 — 8 requests, only 3 fit next quarter](17-case-study-quarterly-priority-conflict.md)

### Bad-input correction examples

- [18 — Bad input reframed into a better product question](18-bad-input-reframed.md)
- [19 — Bad priority request corrected into a defendable stack](19-bad-priority-input-corrected.md)

### Review and learning

- [05 — Postmortem Lite](05-postmortem-lite.md)

### Command-path examples

- [22 — Command path: clarify -> evaluate](22-command-clarify-then-evaluate.md)
- [23 — Command path: prioritize -> roadmap -> exec summary](23-command-prioritize-roadmap-exec.md)

## How to use these examples

Use them in three ways:

### 1. Quick repo evaluation

If you are deciding whether this project is worth trying, skim:

- 01
- 02
- 03
- 07
- 15
- 17
- 20
- 21
- 22
- 23

That is usually enough to understand both the core PM style and the higher-pressure product-leader angle.

### 2. Prompt inspiration

If you want to test the skill quickly in your own workspace, reuse the input examples and swap in your own real context.

### 3. Contribution alignment

If you add or materially change a workflow or template, update or add examples so the repo stays easy to understand from the outside.

## What these examples intentionally do not try to be

They are not:

- exhaustive workflow specs
- polished PRDs
- universal PM truth

They are simply the fastest path to understanding what the skill is trying to do well.

## Suggested reading paths

### If you are an IC PM

Start with:

- 01
- 02
- 04
- 09
- 16
- 18

### If you are a head of product / founder / product leader

Start with:

- 03
- 07
- 10
- 11
- 12
- 13
- 14
- 20
- 21
- 23
