speclisted

## Triage: bugs route to /diagnose Before speccing, detect bug-shaped inputs: crashes, error stacks, regression reports ("worked yesterday", "used to work"), platform-specific failures ("broken on X", "doesn't work when…"), or user-report framing that implies root-cause-first (not design-first). If detected, stop and redirect: *"This is a debugging task, not a spec task. Route to /diagnose instead — it will isolate the root cause, then /spec can scope the fix."* Do not emit a spec. --- Dispatch two sub-agents in parallel. One researches the web for prior art, comparable approaches, and patterns relevant to $ARGUMENT. The other inspects the local working directory for conventions, existing artifacts, and integration points relevant to the domain. When both return, synthesize a concise spec using the domain-appropriate schema below. Present to the user for confirmation before proceeding. **Output schema by domain:** | Domain | Spec fields | |--------|-------------| | `software` | problem, goals, non-goals, approach, key decisions, interface, file plan, test plan, open questions | | `research` | problem, hypothesis, methodology, prior art positioning, expected results, publication plan, open questions | | `design` | problem, user needs, constraints, solution space, prototype plan, success metrics, open questions | | `business` | opportunity, risk analysis, competitive landscape, go/no-go criteria, resource plan, open questions | | *(other)* | problem, goals, non-goals, appr