Cursor rule

1---
2alwaysApply: false
3---
4 
5# Adaptive Depth
6 
7**Purpose**: Explain how AI-DLC adapts detail level to problem complexity
8 
9## Core Principle
10 
11**When a stage executes, ALL its defined artifacts are created. The "depth" refers to the level of detail and rigor within those artifacts, which adapts to the problem's complexity.**
12 
13## Stage Selection vs Detail Level
14 
15### Stage Selection (Binary)
16- **Workflow Planning** decides: EXECUTE or SKIP for each stage
17- **If EXECUTE**: Stage runs and creates ALL its defined artifacts
18- **If SKIP**: Stage doesn't run at all
19 
20### Detail Level (Adaptive)
21- **Simple problems**: Concise artifacts with essential detail
22- **Complex problems**: Comprehensive artifacts with extensive detail
23- **Model decides**: Based on problem characteristics, not prescriptive rules
24 
25## Factors Influencing Detail Level
26 
27The model considers these factors when determining appropriate detail:
28 
291. **Request Clarity**: How clear and complete is the user's request?
302. **Problem Complexity**: How intricate is the solution space?
313. **Scope**: Single file, component, multiple components, or system-wide?
324. **Risk Level**: What's the impact of errors or omissions?
335. **Available Context**: Greenfield vs brownfield, existing documentation
346. **User Preferences**: Has user expressed preference for brevity or detail?
35 
36## Example: Requirements Analysis Artifacts
37 
38**All scenarios create the same artifacts**:
39- `requirement-verification-questions.md` (if needed)
40- `requirements.md`
41 
42**Note**: User's initial request is captured in `audit.md` (no separate user-intent.md needed)
43 
44**Detail level varies by complexity**:
45 
46### Simple Scenario (Bug Fix)
47- **requirement-verification-questions.md**: necessary clarifying questions
48- **requirements.md**: Concise functional requirement, minimal sections
49 
50### Complex Scenario (System Migration)
51- **requirement-verification-questions.md**: Multiple rounds, 10+ questions
52- **requirements.md**: Comprehensive functional + non-functional requirements, traceability, acceptance criteria
53 
54## Example: Application Design Artifacts
55 
56**All scenarios create the same artifacts**:
57- `application-design.md`
58- `component-diagram.md`
59 
60**Detail level varies by complexity**:
61 
62### Simple Scenario (Single Component)
63- **application-design.md**: Basic component description, key methods
64- **component-diagram.md**: Simple diagram with essential relationships
65 
66### Complex Scenario (Multi-Component System)
67- **application-design.md**: Detailed component responsibilities, all methods with signatures, design patterns, alternatives considered
68- **component-diagram.md**: Comprehensive diagram with all relationships, data flows, integration points
69 
70## Guiding Principle for Model
71 
72**"Create exactly the detail needed for the problem at hand - no more, no less."**
73 
74- Don't artificially inflate simple problems with unnecessary detail
75- Don't shortchange complex problems by omitting critical detail
76- Let problem characteristics drive detail level naturally
77- All required artifacts are always created when stage executes
78