brainstorming

Iterative questioning guides you to clarify vague requirements by asking one focused question at a time, eliciting constraints and success criteria until the design intent is concrete. This process replaces ambiguous briefs with actionable specifications.

Design exploration presents 2-3 competing approaches with documented tradeoffs, letting you evaluate fit against project constraints before selecting a path. This validates decisions early and reduces rework.

Iterative questioning and validation produce a Design Summary with next steps that translates into proposal-ready OpenSpec format, bridging early-stage exploration to formal specification.

Use this approach for early-stage product or system design when requirements are complex or vague. One-question-at-a-time keeps exploration focused, prevents assumption-driven design, and builds shared understanding incrementally.

Design validation produces 200–300 word summaries that test each approach against project constraints and success criteria, surfacing fit issues or gaps before development starts.