flow-preflightlisted

# flow-preflight Foundation sub-skill consumed by every FDA orchestrator. Verifies the environment, discovers FDA artifacts, classifies the run mode, confirms Linear scope, and emits a structured preamble for downstream sub-skills. This skill is **NOT user-invocable** (`disable-model-invocation: true`, per Q7). It runs as the first step inside `/flow:start-project`, `/flow:retrofit-project`, `/flow:add-domain`, `/flow:add-sub-flow`, and `/flow:audit`. Sub-skills downstream (`flow-inventory-codebase-scan`, `flow-linear-scaffold`, `flow-doc-author`, `flow-journey-author`, `flow-regen-index`, ...) read this skill's preamble output rather than re-running discovery. **Read-only contract** with two narrow exceptions, both governed by the same Q31.5 atomic-rename pattern (Section 4.4): (a) successful first-run bootstrap via Section 6 writes `.flow/config.json`; (b) stale-config detection in Path A (Section 4.1) re-enters the bootstrap and replaces `.flow/config.json` via the same atomic-rename. Nothing else mutates filesystem or Linear state. The full design rationale lives in `docs/design-rationale/fda-plugin-interview.md`. Specifically: Q12 (memory:70-78) locks the 5 responsibilities; Q31.5 (memory:310) locks the atomic-rename mechanism; Q32 (memory:344) amends Q12 with explicit dependency-version checks; Q36 (memory:346) locks the 7-step embedded bootstrap and its 6-refinement audit trail at memory:370. **DO NOT re-derive from these locks** — re-litigation already resolved at