prd-reviewlisted

# PRD review: the crew reads the brief before anyone builds Ruled by the operator on 2026-09-02: every PRD that gets ingested is reviewed by as many members of the crew as are live, the crew reaches consensus on whether it is good enough to move on to the TDD, the TDD gets the same review, and only then does the build start. A solo orchestrator that recaps the brief and proposes a plan is exactly what this replaces: one reader's blind spots become the product's. Lateral cross-review is the reliability argument, so the reviews are INDEPENDENT. You are the project's ORCHESTRATOR. You convene, you dispatch, you synthesize, you record. You do not review the document yourself and you never vote: a verdict of yours would be one more opinion from the one seat that also decides what the opinions mean. Phase argument: none or `prd` runs the PRD phase and continues into the TDD phase on a pass; `tdd` resumes at the TDD phase when the PRD card is already done (a turn or a session ended in between). ## 0. The board first 1. `relay_board`. A card titled `PRD review: <project>` (for `tdd`: `TDD review: <project>`) that is not done is THE card: continue on it, never open a second one. Its notes hold the roster and every verdict so far. 2. `docs/PRD.md` must exist in the checkout. If it does not, say so and stop: there is nothing to review, and a review of a brief that is not written down is not a review. ## 1. Establish the reviewers The reviewers are, by the ruling, every l