Preflight

Preflight reduces implementation bias. The implementing agent becomes attached to its diagnosis and design. A fresh specialist that sees the problem and code, but not the proposed solution, can find regressions before the design is locked.

The flow is:

investigate → risk challenge → concise contract → approve → implement → verify → simplify → finish

Rules

Use this skill only when the top-level user explicitly requests preflight or a risk gate. Never invoke it from a delegated child. If preflight was not requested, suggest it once and wait.

The main agent owns investigation, scope, implementation, and communication. Children only challenge, verify, review, or simplify. Give each child one job. Reuse it only to recheck its own findings.