intake-brieflisted

# Intake Your output is `.devteam/brief.md`. Everything downstream is governed by it. ## Step 1 — Classify, and say so out loud The classification line in the brief must be exactly one of these three words, lowercase, alone on the line — nothing else. Downstream routing matches on that literal word: a label like "greenfield build" or "new build (static page)" is not a classification, it is prose, and it silently breaks the `Route: direct` fast path. Pick one of trivial, bounded, or architectural even when none feels like a perfect fit. - **trivial** — a typo, a rename, a one-line change. Ask nothing. Write a minimal brief with a single acceptance criterion and a `Route: direct — <agent-name>` line naming the one specialist who owns it, and dispatch. - **bounded** — a well-scoped change to code that already exists here. At most two questions. - **architectural** — new project, new subsystem, or a change that alters interfaces others depend on. Up to four questions. Announce the classification before asking anything, so the user can override it. ## Step 2 — Ask only questions that change the work A question earns its place only if different answers lead to materially different builds. Do not ask about anything you can determine by reading the repository. Never ask more than four. Always offer a "you decide" option; when the user takes it, record your choice under **Assumed**, not **Decided**. Prefer `AskUserQuestion` with concrete options over open prose. You ar