speckit-intake

Routing engineering requests before specification requires classifying the work as migration, bugfix, new-feature, or needs-routing. This process captures routing confidence, risk level, and delivery profile to prevent ambiguous requests from jumping straight into implementation.

Spec-kit intake is a pre-specification workflow that classifies CoreRuntime requests and records evidence like source paths and API boundaries. You need it when planning repository changes to ensure work is categorized safely and clarification gaps are explicitly handled before any specification begins.

Classifying a CoreRuntime request involves evidence-based assessment to determine if it is a migration, bugfix, or new-feature. The intake workflow preserves source paths and boundary records, applying explicit clarification handling when the request is ambiguous and needs routing.

Spec-kit intake works for bugfixes by capturing routing confidence, risk level, delivery profile, and human gates. It ensures that even corrective work undergoes structured intake to identify scope boundaries and clarification gaps before specification.

Handling ambiguous product requests requires structured intake that applies explicit clarification handling and routes them to a needs-routing category. This prevents premature implementation by forcing teams to capture missing evidence and identify exact scope boundaries first.

You should not skip request routing when a request touches complex runtime or frontend areas, involves UI splits, or crosses identity and API boundaries. Skipping intake risks losing source paths and boundary records needed to plan repository changes safely.