fix: strengthen answer analysis in nfr-design and infrastructure-design

aidlc-rules/aws-aidlc-rule-details/construction/infrastructure-design.md

@@ -47,8 +47,11 @@ Map logical software components to actual infrastructure choices for deployment
 
 ### Step 5: Collect and Analyze Answers
 - Wait for user to complete all [Answer]: tags
-- Review for vague or ambiguous responses
-- Add follow-up questions if needed
+- **MANDATORY**: Carefully review ALL responses for vague or ambiguous answers
+- **CRITICAL**: Add follow-up questions for ANY unclear responses - do not proceed with ambiguity
+- Look for responses like "depends", "maybe", "not sure", "mix of", "somewhere between"
+- Create clarification questions file if ANY ambiguities are detected
+- **Do not proceed until ALL ambiguities are resolved**
 
 ### Step 6: Generate Infrastructure Design Artifacts
 - Create `aidlc-docs/construction/{unit-name}/infrastructure-design/infrastructure-design.md`

aidlc-rules/aws-aidlc-rule-details/construction/nfr-design.md

@@ -44,8 +44,11 @@ Incorporate NFR requirements into unit design using patterns and logical compone
 
 ### Step 5: Collect and Analyze Answers
 - Wait for user to complete all [Answer]: tags
-- Review for vague or ambiguous responses
-- Add follow-up questions if needed
+- **MANDATORY**: Carefully review ALL responses for vague or ambiguous answers
+- **CRITICAL**: Add follow-up questions for ANY unclear responses - do not proceed with ambiguity
+- Look for responses like "depends", "maybe", "not sure", "mix of", "somewhere between"
+- Create clarification questions file if ANY ambiguities are detected
+- **Do not proceed until ALL ambiguities are resolved**
 
 ### Step 6: Generate NFR Design Artifacts
 - Create `aidlc-docs/construction/{unit-name}/nfr-design/nfr-design-patterns.md`