---
name: intake-router
description: >
  Use when a user gives any new request to determine the working mode, estimate ambiguity and scope,
  infer the likely business domain, and decide which follow-on skills to load. Triggers on nearly every
  new request routed through @sarp-builder.
---

# Intake Router

Bu skill front-door triage yapar. Amaç kullanıcıyı gereksiz sürece sokmadan doğru moda yönlendirmektir.

## Çıktı

Her istek için şu kısa karar setini üret:

- `mode`: analyze | plan | build | full | heal
- `domain`: offer | order | booking | payment | delivery | unknown
- `ambiguity`: low | medium | high
- `next_skills`: yüklenecek minimum skill listesi

## Heuristics

- Kısa, net, küçük teknik istek → `build`
- Freeformat business ihtiyacı veya analyst metni → `analyze`
- "story", "PBI", "AC", "test case" → `plan`
- "analiz ve story", "analiz et story çıkar", "teknik story oluştur" → `plan`
- "end-to-end", "tamamını yap", "full" → `full`
- "fix", "heal", "review", "test fail" → `heal`

## Domain Tespiti

- shopping, fare, pricing, bundle, ancillary, repricing, ttl → `airline-offer`
- cart, checkout, upsell, promotion, loyalty, personalization → `airline-retail`
- order, cancel, change, refund, state → `order`
- transition, saga, event, workflow, compensation, state machine → `transition`
- ml, ai, prediction, model, recommendation, forecasting → `ai`
- ticket, boarding pass, schedule, disruption, void, reissue → `delivery`
- concept, entity, invariant, aggregate, domain model → `concept`
- product, inventory, availability, catalog, sku, bundle → `product`

## Kural

- Mode seçimini kullanıcıya uzun açıklama yapmadan bildir
- Belirsizlik düşükse sorusuz ilerle
- Belirsizlik yüksekse `requirement-clarifier` yükle
- Analyst intent'i geldiyse varsayılan `analyze`, açıkça story isterse `plan`, geliştirme isterse `full`