pre-execution-reviewlisted

# Pre-Execution Review Policy (internal) One owner for the rules that both pre-execution reviewers apply, so a Product review and a Plan review cannot drift into two different definitions of independence, union, or convergence. It states **policy**; it runs nothing, writes nothing, and emits no verdict of its own. ```text evidence-grounding = how an author prepares and self-checks an artifact. pre-execution-review = how any pre-execution reviewer judges it, and what the frozen ledgers look like. lane (design/plan/review steps) = the surviving pre-execution path; feature 61 P8b retired the standalone review-spec / review-plan verdict skills, so this pack now owns the ledger shapes the lane and execute-phase consume, not a verdict gate. ``` ## When to use - The lane's `plan`/`review` steps — when writing the ledgers and when a review comes back failed. - Nothing else. Candidate-source review (`review-change`), merge gating (`audit-pr`) and execution (`execute-phase`) keep their own contracts; this skill adds no authority over them. ## Hard rule — no verdicts, no edits This skill never prints `SPEC-REVIEW-PASS`, `PLAN-REVIEW-PASS`, `SPEC-REVIEW-FAIL`, `PLAN-REVIEW-FAIL` or `NEEDS-DESIGN` as a result of its own reading, and it never writes a unit artifact. Quoting a verdict shape here is a definition, not an issuance. A policy summary that reads like an approval is a contract