preflight

# Preflight Skill Pre-delivery validation checklist. Run before every implementation task. ## Checklist ### Constraints (ALWAYS FIRST) Before scoping any delivery work, establish constraints. Do not propose a plan before knowing the budget. - [ ] **Time budget**: "How much time do you have for this?" (hours, days, sprint length) - [ ] **Resource constraints**: Solo? Team? What skills are available? - [ ] **Fidelity**: Demo/prototype vs. production? Who is the audience? - [ ] **Dependencies**: Waiting on anything external? If time budget < 8 hours, scope aggressively — one vertical slice, no polish. If the initial plan exceeds the time budget, cut scope before presenting it to the user. **Re-forecast trigger (audit-triggered / emergent work).** Work that opens as "just address the recommendations", "quick fix", or any audit/assessment follow-up still gets a constraint pass — set an explicit estimate even when no one asked for one. Then, mid-session, **re-forecast when the work crosses ~2× the estimate or when no estimate was ever set**: stop, state actual-so-far vs estimate, and re-scope or re-confirm the budget before continuing. The failure this catches: emergent cycles that bypass preflight and balloon silently (dogfood `cycle-history.yml` — a "~2h" audit cycle ran ~9h; a "session-scope" one ran ~14h). The re-forecast becomes the `calibration.effort_accuracy` data point at `/retrospective`. *Source: Hoskins transcript (2026-04-25) — agent proposed 20-hour plan befor...