头脑风暴 - 需求发现（AI 编码增强版）

To turn a vague software idea into an MVP PRD, the workflow captures task intent first, gathers repository context, and uses gated single-question clarifications to converge multiple implementation paths into a structured prd.md.

The best way to clarify ambiguous requirements is to perform action before questioning by checking existing repository and documentation context, classifying complexity, and proposing 2-3 concrete options with explicit trade-offs.

A gated single-question workflow reduces back-and-forth by asking only one unblocking question per turn, researching technical choices independently, and recording decisions directly into the PRD.

Yes, you can use this workflow for iterative coding with multiple implementation options, as it conducts lightweight research to evaluate technical choices and generates a converged MVP PRD tailored to your specific trade-offs.

You need to classify complexity during requirement discovery to select the correct depth of brainstorming, ensuring technical choices receive appropriate research and the MVP PRD matches the project scale.