ideatelisted

# Ideate Turn ideas into approved design concepts through dialogue. Output: an ideation document `/design` reads. ## Hard Gate No code, no source files, no implementation actions until the user approves a concept. Output is an ideation doc, not code. ## Scope Covers: problem clarity, prior art, alternatives at concept level, build-vs-buy, scope decomposition. Stops at: file paths, function signatures, integration points, implementation steps. Those are `/design`. ## Codebase Awareness Build light awareness of the relevant area: - Dispatch one `code-explorer` agent at start: "Lay of the land in [area]? Patterns, what's already built that might relate, what would a feature here need to fit with?" - Inline lookups (Read, Grep, Glob) when user proposes specifics - Don't go deep — that's `/design`. You're checking fit, not designing If the codebase already addresses the problem (or part of it), surface immediately: "We already do X at file:line" beats reinventing. ## Prior Art Search For non-trivial features, look for existing solutions before assuming custom is needed: - Web search for libraries, services, canonical implementations (Exa for descriptive discovery; WebSearch for known entities) - Evaluate: maturity, fit with codebase, license, operational cost - Report in the ideation doc: what was considered, what was rejected, why Default leans build-vs-buy in favor of buy unless there's clear reason to build. ## Conversation Shape **Understand first.** Check CLAU