ia-brainstorming

To turn vague feature requests into an approved design doc, use structured pre-implementation exploration. This process applies interview-style questioning to clarify ambiguous requirements and explore trade-offs, ensuring design approval before any coding begins.

Scope decomposition in software design splits complex requests spanning independent subsystems into separate cycles. You need it when a vague feature request covers multiple subsystems, requiring decomposition into distinct brainstorm, plan, and implementation phases before proceeding.

Structure brainstorming and trade-off analysis by comparing 2-3 approaches during deep interview-style questioning. This captures explicit design gates and outputs a versioned artifact under docs/brainstorms, ensuring you address all trade-offs before implementation.

Yes, you can use design-first exploration for ambiguous requirements across multiple subsystems. It detects when requests span independent subsystems and splits the work into separate brainstorm and implementation cycles to handle the complexity systematically.

Yes, the design doc capture process includes an anti-TBD checklist for self-review. It outputs a versioned artifact saved under docs/brainstorms with required sections, ensuring no unresolved items remain before the design is explicitly approved.

Avoiding coding when requirements are unclear prevents building the wrong solution. Pre-implementation exploration resolves ambiguity and maps trade-offs first, producing an approved design document rather than premature code that might miss subsystem dependencies.