ptp-review-prd

Run the review with a selector like epic:0001, story:NN, or a bare change id; omitting the argument reviews all active epics. The pass reads openspec/changes/<id>/prd.md, applies a 7-check rubric, and reports a PASS, WARN, or FAIL verdict with findings grouped by severity.

The rubric checks that the PRD file exists and is non-placeholder, all schema sections are present, requirements split into functional and non-functional and trace to goals, acceptance criteria are testable, scope matches non-goals, goals are measurable, and dependencies, risks, and open questions contain real content.

Yes. When roles.main resolves to codex, the review runs as a read-only codex exec -s read-only dispatch using the same rubric. The codex binary must be on PATH; if absent, the pass stops and tells you to install codex or set roles.main back to claude.

No. The review is strictly read-only: it edits nothing, runs no git, no branch guard, and no openspec validate. On WARN or FAIL it recommends re-running /ptp:prd to revise the document rather than hand-editing it.

A missing prd.md is reported as a Critical finding, which always produces a FAIL verdict regardless of the configured severity threshold. The recommended next step is to author the PRD first with /ptp:prd before planning.

The threshold, resolved from layered ptp config with default low, determines which findings block. Findings below the threshold are still listed but marked non-blocking; only actionable Critical findings cause FAIL and actionable High findings cause WARN.