Workflow Router

Use this as the entry point; downstream skills own their detailed instructions.

Route

Classify the request, choose only the matching sequence below, and state each transition rationale in one line. Do not add steps from another route unless its trigger is present. In an unfamiliar repository, perform repository reconnaissance first (inspect structure, README/CONTRIBUTING, build/test framework, CI, recent git log, and existing patterns per AI_ENGINEERING_WORKFLOW.md).

Idea to staging

Vague or multi-issue request

• Vague, broad, or decision-heavy request: clarify-work → define-done → decompose-to-issues only when it cannot fit one independently verifiable issue.
• Transition rationale: clarify creates a safe boundary; define-done makes success testable; decomposition protects independent delivery.

Concrete single behavior change

• Concrete single behavior change: define done → tdd test-first change → simplify the changed code → review-gate → staging PR.
• Transition rationale: the request is already bounded, so clarification and decomposition add no value; tests prove behavior before review.