scopelisted

# Scope Diagnose why work isn't buildable yet, route to exactly one specialist skill, and open a ledger the moment routing happens. Never do the specialist's work yourself — a correct route with no other output is a complete session. For an epic child, every specialist instead uses untracked session scratch outside the child branch, discarded after the final order; it creates no scope ledger or docs/scope ledger. `/epic` alone owns proposal/design and its ledger. ## Routing table Classify the **dominant** uncertainty — the one that, if resolved, makes the others tractable — and route to exactly one of: - **Big and foggy, many interlocking decisions that block each other** → `epic`. Mechanical bulk without an unsettled decision is not an epic route; hand-split it into serial build tickets. - **A concrete plan or design exists in someone's head, untested** → interview mode ([references/interview.md](references/interview.md), in this skill). - **A written plan, work order, spec, or brief exists and needs stress-testing before anything is built** → `plan-review`. - **Missing facts answerable from docs or sources** → `research`. - **Only answerable by feeling it out in running code** → `prototype`. - **The dominant uncertainty is what a user-facing surface should look like** → `ui-craft`, lock phase. - **Mixed or unclear** → ask the user **one** framing question, then route. One question at a time, always — never a menu of questions. - **Nothing genuinely uncertain