aidlc-brainstorming

To turn a project idea into a design document, use a structured brainstorming process that guides requirements analysis, assesses complexity, and iteratively refines ambiguities into a detailed specification.

The best way to define software requirements before coding is through an ambiguity resolution loop that clarifies input, justifies complexity levels, and enforces strict design approval policies to prevent premature code generation.

Complexity assessment works by requiring you to declare and justify the design task's complexity level—Minimal, Standard, or Comprehensive—ensuring the engineering team understands the scope before implementation proceeds.

You cannot generate code while the design document is incomplete because the skill adheres to strict HARD-GATE policies that prevent any code generation until the final design is formally approved.

You need iterative refinement for requirements analysis to resolve ambiguities in user input, ensuring that every aspect of the software design is well-defined and documented before handing it to the engineering team.

Yes, the brainstorming workflow supports phased design presentation by breaking down the conversion of raw ideas into detailed design documents through a structured, multi-step process.