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-workbenchhandles well - what output shape each workflow tends to produce
- what “good behavior” looks like from the skill
- 01 — Clarify a vague request
- 02 — Feature Evaluation Memo
- 06 — Decision Brief
- 07 — Prioritization Stack
- 03 — Executive Summary
- 04 — PRD Lite
- 08 — Roadmap One-Pager
- 09 — Metrics Scorecard
- 20 — Launch readiness call
- 21 — Mixed signals operating review
- 10 — Product leader quarterly priority call
- 11 — Founder strategy decision
- 12 — Portfolio Review Summary
- 13 — Head of Product Operating Review
- 14 — Founder Business Review
- 15 — Boss says the product needs more wow factor
- 16 — Ops wants an AI gimmick feature
- 17 — 8 requests, only 3 fit next quarter
- 18 — Bad input reframed into a better product question
- 19 — Bad priority request corrected into a defendable stack
Use them in three ways:
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.
If you want to test the skill quickly in your own workspace, reuse the input examples and swap in your own real context.
If you add or materially change a workflow or template, update or add examples so the repo stays easy to understand from the outside.
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.
Start with:
- 01
- 02
- 04
- 09
- 16
- 18
Start with:
- 03
- 07
- 10
- 11
- 12
- 13
- 14
- 20
- 21
- 23