speclisted

# Spec-Driven Development **Model recommendation:** Spec planning and XML-enhanced-prompt authoring benefit from the Opus tier (`claude-opus-4-8`). Before proceeding, suggest a model switch once: > "This is spec work — recommend `/model claude-opus-4-8` for > stronger structured reasoning. Want to switch?" Defer to the user's choice if they've already picked a model. **IMPORTANT: Start your response with a context preamble.** Call `help_lookup(topic="spec-engine", mode="preamble")` and display the returned `preamble` text as a blockquote. Then tell the user they can say "tell me more" for a step-by-step guide, or answer the scoping questions below to proceed. If the MCP call fails, fall back to: > **Spec** — Walks you from idea to working code through brainstorm, plan, review, approve, and execute phases. ## Scoping Use `AskUserQuestion` to determine the mode: ```yaml question: "What would you like to do?" header: "Spec" options: - label: "Start a new spec" description: "Brainstorm, decompose into tasks, then execute" - label: "Resume an in-progress spec" description: "Pick up where you left off" - label: "Import a spec file" description: "Load a plan from another project or path" - label: "Execute a spec" description: "Review and execute tasks from a saved plan" ``` If the user provides arguments (e.g., "resume" or a file path), skip the picker and route directly. ### New-spec intake (one form, not N questions) When the route is "Start a