planning-preflightlisted

# Planning Preflight (internal) The single owner of the planning-side repository gates. `plan-feature` and `plan-fix` consume this one contract instead of each internal repeating its own normalized-state read and architectural classification. This skill uses a **two-stage contract** to resolve the tension between: (1) the need for planners to read the NRS early (architecture discovery is read-only and required to inform the plan), and (2) the requirement that the final architectural classification only happens after the complete engineering plan exists. ## When to use Any planner route that can write planning artifacts: - `plan-feature` — every route that will scaffold (scoped, issue, `--next`). - `plan-fix` — every fix-SPEC draft. Composed internals (`plan-feature-from-issue`, `plan-feature-scaffold`) consume the same result via the in-turn planning context the router creates; they never re-run discovery or classification. ## Two-Stage Contract ### Stage 1 — NRS read during planning (lightweight) While the plan is still being built, routers may perform a read-only consumption of the normalized repository state (NRS) for architectural context. At this stage only the NRS port is classified; the architectural classification is deferred. Record the Stage 1 result using the following format: ```text Preflight: Stage 1 — NRS <consumed|n/a> · arch: deferred ``` This result informs the plan but does not block emission. ### Stage 2 — Full classification after pla