speclisted

# Spec Idea: $ARGUMENTS (if empty, ask for the problem and any solution ideas first). Derive a kebab-case `<slug>` from the text before the first `—`/`–` (≤4 meaningful words, no command verbs or filler). Output: `.specs/specs/<slug>.md`. If it exists, ask: overwrite (Recommended) or new name. ## Workflow ### 1. Explore codebase Map current state: data models, services, API routes, frontend, tests. Note exists vs. must build. Codebase first, then docs. Unverifiable claims → flag as uncertain, never fabricate. ### 2. Interview One question at a time, 2–4 options each, your recommended answer first and marked `(Recommended)`. Explore code instead of asking when possible. | Branch | Key questions | Skip when | | ---------------- | --------------------------------------- | -------------------------------- | | Scope & Surface | Where? New page or integrated? Roles? | CLI/library, no new entry points | | Data & Concepts | Definitions, existing vs missing data | Never skip | | Behavior | Interaction patterns, filtering, search | No user-facing behavior | | Display | Numbers, tables, charts, exports | No UI | | Access & Privacy | Who sees what? Sensitive data? | Single-user, no auth | | Boundaries | Out of scope, deferred features | Never skip | | Integration | Schema, s