Brainstorm — Structured Requirements Interview

Reduce ambiguity to near-zero through targeted questions. Activated within plan mode after a quick Ariadne/Clio landscape scan — use that context to ask informed, codebase-grounded questions.

When to Use

• Request is vague ("make it faster", "improve the UX")
• Scope touches multiple systems with unclear boundaries
• Acceptance criteria are implied, not stated
• Multiple valid approaches exist and user preference matters
• User explicitly asks to brainstorm or think through a problem

When NOT to Use

• Request is clear and well-scoped ("add a logout button to the navbar")
• User already provided detailed requirements
• Trivial tasks (typo fixes, config changes)

Workflow