clarification

Iterative Q&A resolves ambiguity in vague requirements by enforcing one-question-per-message discipline and orchestrating parallel subagent exploration to produce a concrete context brief. This narrows underspecified user requests into well-defined work scopes.

Resolving ambiguity during product discovery is handled by coordinating subagents to explore the codebase in parallel while asking iterative questions. This maps existing context and aligns goals with the current state before planning begins.

To generate a context brief for scoping, start the clarification workflow and answer focused questions one at a time. The process automatically outputs a saved brief that guides planning and drives downstream plan-crafting.

Yes, parallel codebase exploration is supported via subagents that map context while questions are asked. This allows simultaneous requirement gathering and code exploration to efficiently produce a context brief.

An iterative Q&A loop should be used for software requirements during initial scoping, product discovery, and codebase analysis when requests are vague or underspecified. It enforces structured questioning to align goals with existing state.