preflightlisted

# Preflight `/route` routes into `/preflight`; it does not replace `/route`. Use this only after routing has established that the immediate need is bounded up-front research. If you have not chosen the governing skill path yet, stop — use `/route` first. You're about to begin work on something: $ARGUMENTS First: you need to understand what it entails. Your immediate task is to correctly decide how much effort to spend on this preliminary research. Too little is as bad as too much. You must estimate where the goldilocks zone is, and arrive with maximum tokens intact. You may be expected to: - clarify a vague task - methodically diagnose a fault - write or critique a thorough and considered design doc which fits the implementation surface - execute a thoroughly prepared plan with efficiency - preserve your own context by delegating to sub-agents Do not use this skill to decide whether the task belongs to `/slice`, `/design`, `/execute`, or another governing skill. That decision must already be made. If you can't tell whether `/preflight` is appropriate, you probably need `/route`, not this skill. Learn **just enough to ask the user the right clarifying questions**. These might include: how deeply should you research? what remains ambiguous? which assumptions are safe enough to carry forward? If you chase the questions which arise as you go, you'll disappear like a helium balloon into the open sky. Instead: 1. Read the material in front of you 2. Take stock of rele