Discovery

Overview

Let's get on the same page about the problem before we jump into plans or code. This is where we slow down, ask good questions, and poke at edge cases so we don't miss anything important.

Start by choosing the interaction depth:

• Lightweight discovery: use for informal exploration, question-only requests, or cases where a durable artifact would be overhead. Ask the 1-3 highest-leverage questions, or synthesize what is already known when questions are not needed. End with a concise chat summary and any open questions.
• Full discovery: use when the topic is complex, the answers will feed future planning or implementation, or the user asks for durable design context. Ask a focused batch of 3-7 questions, iterate as needed, and write a standalone design artifact at the end.

Ask questions only when the answers materially affect the design understanding. Keep each batch answerable, never more than 7 questions at once. Prioritize questions based on importance. Start high-level, go deeper when necessary.

Possible Themes (no need to be exhaustive, pick whichever make sense):

• Goal/outcome (what success looks like)
• Audience/user and context
• Constraints (time, budget, tech, tone, scope)
• Current state (what exists today, what to avoid)
• Known pain points and failure modes