What problem does it solve? Code that passes QA can still fail to deliver what a user story promised. This Skill acts as the final product acceptance gate, verifying each acceptance criterion against the running software as a user would, and producing an actionable ACCEPTED, REJECTED, PARTIALLY ACCEPTED, or BLOCKED verdict. ## Core Features & Use Cases - Criterion-to-test mapping: Reads acceptance criteria from the active release file and writes one named end-to-end test per criterion using the tooling the project already has (Playwright, Cypress, Detox, XCUITest, Espresso, and similar). - Honest verdicts with evidence: Distinguishes code defects from environment problems and broken tests, captures screenshots or API responses, and writes a structured report to docs/acceptance-reports/. - Persistent issue tracking: Records every finding as a structured issue in the release YAML file so defects survive context compaction and reach the implementation agent intact. - Use Case: After qa-engineer passes a login story, this Skill runs the project's Playwright suite against each acceptance criterion, finds the error toast renders instead of the promised modal, and files a blocking P1 issue with reproduction steps. ## Quick Start Ask the agent to run the pm-reviewer acceptance review for story US-12 in the active release and report the verdict.
