analyze

Structured requirements analysis evaluates knowledge-base status, gathers project context, classifies requirement types, and assigns a 10-point score to verify completeness before proceeding to solution design.

When the requirements analysis score is below 7, the system outputs targeted follow-up questions to elicit missing details and enforces a strict loop where you must provide information before rescoring and continuing.

Code context extraction activates in Stage B when the score reaches 7 or above, surfacing technical context and quality concerns from the current codebase to inform the subsequent solution design.

Risk assessment and project context evaluation occur during Stage A, checking the knowledge-base status and classifying the requirement type to determine if sufficient information exists to proceed.

You cannot skip follow-up questions because the system enforces a strict rescore loop, ensuring all missing details are provided and the requirement score reaches 7 before Stage B code analysis preparation begins.

Preparing a decision tree for requirements scoring involves evaluating knowledge-base completeness, classifying the requirement type, and assigning a 10-point score to gate the transition from evaluation to code analysis.