Skill proposal: /plan-pm-review + /pm for product management — the missing seventh role

## The Gap

The repo description lists the 23 tools as covering *"CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA."* Notably absent: **Product Manager**.

The CEO/eng/design/devex review quartet covers strategic ambition, architecture, visual design, and developer-facing surfaces. None of them does what a PM actually does day-to-day:

- **Prioritization with a framework** (RICE / ICE / WSJF) instead of "what feels critical"
- **User-segment / JTBD mapping** before scope is locked
- **Acceptance criteria + done definition** for plans before they hit `/plan-eng-review`
- **Ranked roadmap with explicit tradeoffs** — "what's left, ranked by criticality to launch" is a PM question, and today there's no skill that answers it natively
- **User-facing release notes** (different voice from `/document-release`, which targets devs)

`/autoplan` runs CEO + design + eng + DX in sequence and skips PM entirely — exactly the hole.

## Workaround today

The closest substitutes are `/office-hours` (demand questioning) + `/plan-ceo-review` (HOLD-SCOPE / SCOPE-REDUCTION). They get you 60% of the way but neither is a PM — `/office-hours` is intake, `/plan-ceo-review` is founder-mode strategy.

## Proposed skills

**`/plan-pm-review`** — interactive plan review in PM voice. Three modes mirroring the existing review skills:
- **PRIORITIZE** — apply RICE/ICE to each item, surface what to cut, what to defer
- **SHARPEN** — turn vague items into acceptance criteria + done definitions
- **SEGMENT** — JTBD pass: who is this for, what job, what alternative are they hiring it over

**`/pm`** — live PM workflow. Reads roadmap/TODOS/plan files, ranks by criticality + reach + effort, writes a prioritized output. Closes the loop on "what's left to launch?" — the question that today bounces between CEO and eng review without a clean home.

## Open questions

1. Is PM intentionally out of scope (i.e. CEO + eng covers it for solo founders), or genuine omission?
2. Should `/plan-pm-review` slot into `/autoplan` between CEO and eng, or stay opt-in?
3. Naming: `/plan-pm-review` matches the `/plan-*-review` family. Open to `/plan-product-review` if "PM" feels too SaaS-jargony.
4. Acceptance-criteria output — Markdown checklist, Gherkin, or freeform?

Happy to draft a PR if the proposal lands.

Start by comparing the existing /autoplan flow with /office-hours, /plan-ceo-review, /plan-eng-review, and /document-release, then inspect the roadmap, TODOS, and plan files that /pm would read. Done means the proposal's scope, workflow placement, naming, and acceptance-criteria format are resolved, with the PM responsibilities and proposed skills defined clearly enough for implementation.

Written by the indexing model from the issue text.