aibdd-composition-analysis

To break down a software idea into testable requirements, you need to systematically decompose the concept into explicit components, separating user-provided content from missing information and ambiguities to prepare precise inputs for downstream specification skills.

Identifying ambiguities in software specifications involves applying non-fabrication principles to mark missing details and unknowns explicitly, avoiding assumptions by distinguishing what the user actually provided from what requires further clarification.

You can analyze changes to an existing software specification using the CHANGE mode, which supports iterative refinement and scoped discovery to modify an existing idea by separating provided content from new gaps that need clarification.

Yes, composition analysis supports both KICKOFF mode for new ideas and CHANGE mode for modifications, allowing you to decompose initial concepts or iteratively refine existing specifications while marking missing items for user confirmation.

Requirements analysis contains explicitly marked gaps instead of assumptions because the non-fabrication principle enforces avoiding guesses, clearly labeling missing items and ambiguities as unknowns to ensure users confirm details before downstream processing.