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
- Is PM intentionally out of scope (i.e. CEO + eng covers it for solo founders), or genuine omission?
- Should
/plan-pm-review slot into /autoplan between CEO and eng, or stay opt-in?
- Naming:
/plan-pm-review matches the /plan-*-review family. Open to /plan-product-review if "PM" feels too SaaS-jargony.
- Acceptance-criteria output — Markdown checklist, Gherkin, or freeform?
Happy to draft a PR if the proposal lands.
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:
/plan-eng-review/document-release, which targets devs)/autoplanruns 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-hoursis intake,/plan-ceo-reviewis founder-mode strategy.Proposed skills
/plan-pm-review— interactive plan review in PM voice. Three modes mirroring the existing review skills:/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
/plan-pm-reviewslot into/autoplanbetween CEO and eng, or stay opt-in?/plan-pm-reviewmatches the/plan-*-reviewfamily. Open to/plan-product-reviewif "PM" feels too SaaS-jargony.Happy to draft a PR if the proposal lands.