bts-discoverlisted

# Intent Discovery Explore the intent behind: $ARGUMENTS ## Resume Check Check for an existing recipe with phase `discovery`: ```bash bts recipe status ``` If found, read `.bts/specs/recipes/{id}/intent.md`: - Status EXPLORING → continue the conversation from where it left off - Status CONFIRMED → skip discovery, proceed to blueprint If no active recipe, create one: ```bash bts recipe create --type blueprint --topic "$ARGUMENTS" ``` Capture the output — this is the recipe ID (e.g., `r-001-mcp-server`). Use this ID for all subsequent `bts recipe log` calls. ## Discovery Conversation Your goal is to understand **why** this needs to exist, **who** it serves, and **what problem** it solves — through natural conversation with the user. **How to conduct the conversation:** Do NOT use a fixed questionnaire. Instead, reason about what you need to understand based on what the user has told you so far. Ask one or two questions at a time as text output. Adapt your questions based on each response. **Areas to explore** (not a checklist — pursue what matters for this request): - What problem does this solve? What's painful about the current state? - Who will use this? What's their context and expertise? - Why now? What triggered this request? - What does success look like? How will you know it worked? - Are there existing solutions? Why not use them? - What constraints exist? (budget, timeline, compliance, tech) **When to research:** If the user mentions a domain, technology, or