preflightlisted

# Preflight Run this on a draft **before** `plan-review`, not instead of it. Preflight edits the plan; review only objects to it. The premise is measured. One load-bearing process document took ten cold adversarial rounds and roughly sixty-two objections to reach a clean pass, and a post-mortem of those objections found four preventable classes: - **About half were hand-typed facts** — counts, paths, URL params, state enumerations — written from memory and wrong. - **Fix rounds minted new contradictions**, because the same rule was restated in several sections and a patch desynced them. - **Serial generalist panels each found one stratum**; the single parallel specialized round found the most. - **The deepest bugs were only findable by executing the plan's first steps** — a URL param the page silently ignored, a comparison instrument that could only render one state, a fixture whose absence degraded quietly instead of failing. Three of the four are cheaper to prevent than to review. That's preflight: three moves, in order. ## 1. Generated-facts appendix **Every count, path, URL param, enumeration, version, or config value the plan states must be produced by a command.** The appendix records `command → output` pairs; the plan's prose cites the appendix entry rather than repeating the figure from memory. A hand-typed fact is a defect, not a rounding error — the reviewer's job then becomes checking the command, which is cheap, instead of re-deriving the number, w