Cursor rule

1---
2alwaysApply: false
3---
4 
5# AI-DLC Welcome Message
6 
7**Purpose**: This file contains the user-facing welcome message that should be displayed ONCE at the start of any AI-DLC workflow.
8 
9---
10 
11# 👋 Welcome to AI-DLC (AI-Driven Development Life Cycle)! 👋
12 
13I'll guide you through an adaptive software development workflow that intelligently tailors itself to your specific needs.
14 
15## What is AI-DLC?
16 
17AI-DLC is a structured yet flexible software development process that adapts to your project's needs. Think of it as having an experienced software architect who:
18 
19- **Analyzes your requirements** and asks clarifying questions when needed
20- **Plans the optimal approach** based on complexity and risk
21- **Skips unnecessary steps** for simple changes while providing comprehensive coverage for complex projects
22- **Documents everything** so you have a complete record of decisions and rationale
23- **Guides you through each phase** with clear checkpoints and approval gates
24 
25## The Three-Phase Lifecycle
26 
27```
28                         User Request
29                              |
30                              v
31        +---------------------------------------+
32        |     INCEPTION PHASE                   |
33        |     Planning & Application Design     |
34        +---------------------------------------+
35        | * Workspace Detection (ALWAYS)        |
36        | * Reverse Engineering (COND)          |
37        | * Requirements Analysis (ALWAYS)      |
38        | * User Stories (CONDITIONAL)          |
39        | * Workflow Planning (ALWAYS)          |
40        | * Application Design (CONDITIONAL)    |
41        | * Units Generation (CONDITIONAL)      |
42        +---------------------------------------+
43                              |
44                              v
45        +---------------------------------------+
46        |     CONSTRUCTION PHASE                |
47        |     Design, Implementation & Test     |
48        +---------------------------------------+
49        | * Per-Unit Loop (for each unit):      |
50        |   - Functional Design (COND)          |
51        |   - NFR Requirements Assess (COND)    |
52        |   - NFR Design (COND)                 |
53        |   - Infrastructure Design (COND)      |
54        |   - Code Generation (ALWAYS)          |
55        | * Build and Test (ALWAYS)             |
56        +---------------------------------------+
57                              |
58                              v
59        +---------------------------------------+
60        |     OPERATIONS PHASE                  |
61        |     Placeholder for Future            |
62        +---------------------------------------+
63        | * Operations (PLACEHOLDER)            |
64        +---------------------------------------+
65                              |
66                              v
67                          Complete
68```
69 
70### Phase Breakdown:
71 
72**INCEPTION PHASE** - *Planning & Application Design*
73- **Purpose**: Determines WHAT to build and WHY
74- **Activities**: Understanding requirements, analyzing existing code (if any), planning the approach
75- **Output**: Clear requirements, execution plan, decisions on the number of units of work for parallel development
76- **Your Role**: Answer questions, review plans, approve direction
77 
78**CONSTRUCTION PHASE** - *Detailed Design, Implementation & Test*
79- **Purpose**: Determines HOW to build it
80- **Activities**: Detailed design (when needed), code generation, comprehensive testing
81- **Output**: Working code, tests, build instructions
82- **Your Role**: Review designs, approve implementation plans, validate results
83 
84**OPERATIONS PHASE** - *Deployment & Monitoring (Future)*
85- **Purpose**: How to DEPLOY and RUN it
86- **Status**: Placeholder for future deployment and monitoring workflows
87- **Current State**: Build and test activities handled in CONSTRUCTION phase
88 
89## Key Principles:
90 
91- ⚡ **Fully Adaptive**: Each stage independently evaluated based on your needs
92- 🎯 **Efficient**: Simple changes execute only essential stages
93- 📋 **Comprehensive**: Complex changes get full treatment with all safeguards
94- 🔍 **Transparent**: You see and approve the execution plan before work begins
95- 📝 **Documented**: Complete audit trail of all decisions and changes
96- 🎛️ **User Control**: You can request stages be included or excluded
97 
98## What Happens Next:
99 
1001. **I'll analyze your workspace** to understand if this is a new or existing project
1012. **I'll gather requirements** and ask clarifying questions if needed
1023. **I'll create an execution plan** showing which stages I propose to run and why
1034. **You'll review and approve** the plan (or request changes)
1045. **We'll execute the plan** with checkpoints at each major stage
1056. **You'll get working code** with complete documentation and tests
106 
107The AI-DLC process adapts to:
108- 📋 Your intent clarity and complexity
109- 🔍 Existing codebase state
110- 🎯 Scope and impact of changes
111- ⚡ Risk and quality requirements
112 
113Let's begin!
114