Cursor rule

1---
2alwaysApply: false
3---
4 
5# Overconfidence Prevention Guide
6 
7## Problem Statement
8 
9AI-DLC was exhibiting overconfidence by not asking enough clarifying questions, even for complex project intent statements. This led to assumptions being made instead of gathering proper requirements.
10 
11## Root Cause Analysis
12 
13The overconfidence issue was caused by directives in multiple stages that encouraged skipping questions:
14 
151. **Functional Design**: "Skip entire categories if not applicable"
162. **User Stories**: "Use categories as inspiration, NOT as mandatory checklist"
173. **Requirements Analysis**: Similar patterns encouraging minimal questioning
184. **NFR Requirements**: "Only if" conditions that discouraged thorough analysis
19 
20These directives were telling the AI to avoid asking questions rather than encouraging comprehensive requirements gathering.
21 
22## Solution Implemented
23 
24### Updated Question Generation Philosophy
25 
26**OLD APPROACH**: "Only ask questions if absolutely necessary"
27**NEW APPROACH**: "When in doubt, ask the question - overconfidence leads to poor outcomes"
28 
29### Key Changes Made
30 
31#### 1. Requirements Analysis Stage
32- Changed from "only if needed" to "ALWAYS create questions unless exceptionally clear"
33- Added comprehensive evaluation areas (functional, non-functional, business context, technical context)
34- Emphasized proactive questioning approach
35 
36#### 2. User Stories Stage
37- Removed "skip entire categories" directive
38- Added comprehensive question categories to evaluate
39- Enhanced answer analysis requirements
40- Strengthened follow-up question mandates
41 
42#### 3. Functional Design Stage
43- Replaced "only if" conditions with comprehensive evaluation
44- Added more question categories (data flow, integration points, error handling)
45- Strengthened ambiguity detection and resolution requirements
46 
47#### 4. NFR Requirements Stage
48- Expanded question categories beyond basic NFRs
49- Added reliability, maintainability, and usability considerations
50- Enhanced answer analysis for technical ambiguities
51 
52### New Guiding Principles
53 
541. **Default to Asking**: When there's any ambiguity, ask clarifying questions
552. **Comprehensive Coverage**: Evaluate ALL relevant categories, don't skip areas
563. **Thorough Analysis**: Carefully analyze ALL user responses for ambiguities
574. **Mandatory Follow-up**: Create follow-up questions for ANY unclear responses
585. **No Proceeding with Ambiguity**: Don't move forward until ALL ambiguities are resolved
59 
60## Implementation Guidelines
61 
62### For Question Generation
63- Evaluate ALL question categories, don't skip any
64- Ask questions wherever clarification would improve quality
65- Include comprehensive question categories in each stage
66- Default to inclusion rather than exclusion of questions
67 
68### For Answer Analysis
69- Look for vague responses: "depends", "maybe", "not sure", "mix of", "somewhere between"
70- Detect undefined terms and references to external concepts
71- Identify contradictory or incomplete answers
72- Create follow-up questions for ANY ambiguities
73 
74### For Follow-up Questions
75- Create separate clarification files when ambiguities are detected
76- Ask specific questions to resolve each ambiguity
77- Don't proceed until ALL unclear responses are clarified
78- Be thorough - better to over-clarify than under-clarify
79 
80## Quality Assurance
81 
82### Red Flags to Watch For
83- Stages completing without asking any questions on complex projects
84- Proceeding with vague or ambiguous user responses
85- Skipping entire question categories without justification
86- Making assumptions instead of asking for clarification
87 
88### Success Indicators
89- Appropriate number of clarifying questions for project complexity
90- Thorough analysis of user responses with follow-up when needed
91- Clear, unambiguous requirements before proceeding to implementation
92- Reduced need for changes during later stages due to better upfront clarification
93 
94## Maintenance
95 
96This guide should be referenced when:
97- Adding new stages to AI-DLC
98- Updating existing stage instructions
99- Reviewing AI-DLC performance for overconfidence issues
100- Training team members on AI-DLC question generation principles
101 
102## Key Takeaway
103 
104**It's better to ask too many questions than to make incorrect assumptions.** The cost of asking clarifying questions upfront is far less than the cost of implementing the wrong solution based on assumptions.
105