Preflight
Use before editing code or configuration for non-trivial work.
Required checks
- Restate the requested outcome and boundaries.
- Identify affected files, data, APIs, users, and external systems.
- Record the clean baseline: build, lint, typecheck, and tests when available.
- List assumptions and failure modes.
- Define file/module ownership for parallel agents.
- Define the smallest meaningful verification plan.
- Flag destructive, production, secret, auth, payment, migration, or customer-data operations for explicit confirmation.
Finish with a go/no-go decision and the next safe action.