soleri-discovery-phaselisted

# Discovery Phase Structured exploration before committing to a plan. Define the question, research prior art, explore the codebase, identify constraints, draft options with tradeoffs, and recommend a path forward. <HARD-GATE> Do NOT create a plan, write code, or take any implementation action until the discovery document is complete and the user has reviewed it. Discovery produces knowledge, not artifacts. </HARD-GATE> ## Checklist 1. **Define the question** — restate what we're exploring as one specific, answerable sentence 2. **Search vault for prior art** — `YOUR_AGENT_core op:search_intelligent params: { query: "<question>", mode: "scan" }`. Also `op:memory_search` with `crossProject: true`. 3. **Get brain recommendations** — `YOUR_AGENT_core op:brain_recommend params: { query: "<discovery topic>" }`. Get brain recommendations for similar past explorations. 4. **Explore codebase** — read relevant files, configs, architecture, recent commits 5. **Identify constraints** — hard (must-haves) vs soft (nice-to-haves), unknowns that block a decision 6. **Draft 2-4 options** — each with pros, cons, risk, and effort (S/M/L) 7. **Recommend** — pick one, state the primary reason, note what would change the answer 8. **Capture to vault** — persist the discovery finding 9. **Transition** — hand off to brainstorming or writing-plans skill ## Option Format For each option: | Field | Content | | ------------ | -------------------- | | **Approach** | One-senten