Menu

Individual skill

pm-product-review

0upvotes

Orchestrated review of a PM artifact (spec, PRD, OKRs, roadmap, prioritization, strategy). Routes by artifact type to the right audits, auto-runs the always-relevant assumption check, and returns one prioritized report. Trigger when the user asks for a full review of a PM document, "review my spec/roadmap/OKRs", "is this PRD solid", or general PM feedback — but NOT when they name a single specific audit.

pm/workflows/product-review/SKILL.md

Read pinned source

Source commit 5007cd0241ccaa51ae2e4681f9618912dc10e239

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
40
Repository last updated
Jul 2, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Product Review (PM Orchestrator) Skill

## How this skill behaves (read first)

This is the **front door for holistic PM-artifact review**. It is the executable form of
`docs/orchestration-policy.md` applied to PM work: it routes by **artifact type** to the
relevant audits rather than firing all of them, auto-runs the one always-relevant lens
(assumption rigor), and returns **one** prioritized report.

PM work has no "design system" suppression case, but it has the same two failures to avoid:
a vague "looks good" review, and forcing every PM audit onto a document that only needs one.

**When NOT to use this skill:** if the user named a specific audit ("run spec-quality",
"check my OKR metric validity"), skip this orchestrator and invoke that one directly.
Back to top