Cursor rule

1---
2alwaysApply: false
3---
4 
5# Workflow Planning
6 
7**Purpose**: Determine which phases to execute and create comprehensive execution plan
8 
9**Always Execute**: This phase always runs after understanding requirements and scope
10 
11## Step 1: Load All Prior Context
12 
13### 1.1 Load Reverse Engineering Artifacts (if brownfield)
14- architecture.md
15- component-inventory.md
16- technology-stack.md
17- dependencies.md
18 
19### 1.2 Load Requirements Analysis
20- requirements.md (includes intent analysis)
21- requirement-verification-questions.md (with answers)
22 
23### 1.3 Load User Stories (if executed)
24- stories.md
25- personas.md
26 
27## Step 2: Detailed Scope and Impact Analysis
28 
29**Now that we have complete context (requirements + stories), perform detailed analysis:**
30 
31### 2.1 Transformation Scope Detection (Brownfield Only)
32 
33**IF brownfield project**, analyze transformation scope:
34 
35#### Architectural Transformation
36- **Single component change** vs **architectural transformation**
37- **Infrastructure changes** vs **application changes**
38- **Deployment model changes** (Lambda→Container, EC2→Serverless, etc.)
39 
40#### Related Component Identification
41For transformations, identify:
42- **Infrastructure code** that needs updates
43- **CDK stacks** requiring changes
44- **API Gateway** configurations
45- **Load balancer** requirements
46- **Networking** changes needed
47- **Monitoring/logging** adaptations
48 
49#### Cross-Package Impact
50- **CDK infrastructure** packages requiring updates
51- **Shared models** needing version updates
52- **Client libraries** requiring endpoint changes
53- **Test packages** needing new test scenarios
54 
55### 2.2 Change Impact Assessment
56 
57#### Impact Areas
581. **User-facing changes**: Does this affect user experience?
592. **Structural changes**: Does this change system architecture?
603. **Data model changes**: Does this affect database schemas or data structures?
614. **API changes**: Does this affect interfaces or contracts?
625. **NFR impact**: Does this affect performance, security, or scalability?
63 
64#### Application Layer Impact (if applicable)
65- **Code changes**: New entry points, adapters, configurations
66- **Dependencies**: New libraries, framework changes
67- **Configuration**: Environment variables, config files
68- **Testing**: Unit tests, integration tests
69 
70#### Infrastructure Layer Impact (if applicable)
71- **Deployment model**: Lambda→ECS, EC2→Fargate, etc.
72- **Networking**: VPC, security groups, load balancers
73- **Storage**: Persistent volumes, shared storage
74- **Scaling**: Auto-scaling policies, capacity planning
75 
76#### Operations Layer Impact (if applicable)
77- **Monitoring**: CloudWatch, custom metrics, dashboards
78- **Logging**: Log aggregation, structured logging
79- **Alerting**: Alarm configurations, notification channels
80- **Deployment**: CI/CD pipeline changes, rollback strategies
81 
82### 2.3 Component Relationship Mapping (Brownfield Only)
83 
84**IF brownfield project**, create component dependency graph:
85 
86```markdown
87## Component Relationships
88- **Primary Component**: [Package being changed]
89- **Infrastructure Components**: [CDK/Terraform packages]
90- **Shared Components**: [Models, utilities, clients]
91- **Dependent Components**: [Services that call this component]
92- **Supporting Components**: [Monitoring, logging, deployment]
93```
94 
95For each related component:
96- **Change Type**: Major, Minor, Configuration-only
97- **Change Reason**: Direct dependency, deployment model, networking
98- **Change Priority**: Critical, Important, Optional
99 
100### 2.4 Risk Assessment
101 
102Evaluate risk level:
1031. **Low**: Isolated change, easy rollback, well-understood
1042. **Medium**: Multiple components, moderate rollback, some unknowns
1053. **High**: System-wide impact, complex rollback, significant unknowns
1064. **Critical**: Production-critical, difficult rollback, high uncertainty
107 
108## Step 3: Phase Determination
109 
110### 3.1 User Stories - Already Executed or Skip?
111**Already executed**: Move to next determination
112**Not executed - Execute IF**:
113- Multiple user personas
114- User experience impact
115- Acceptance criteria needed
116- Team collaboration required
117 
118**Skip IF**:
119- Internal refactoring
120- Bug fix with clear reproduction
121- Technical debt reduction
122- Infrastructure changes
123 
124### 3.2 Application Design - Execute IF:
125- New components or services needed
126- Component methods and business rules need definition
127- Service layer design required
128- Component dependencies need clarification
129 
130**Skip IF**:
131- Changes within existing component boundaries
132- No new components or methods
133- Pure implementation changes
134 
135### 3.3 Design (Units Planning/Generation) - Execute IF:
136- New data models or schemas
137- API changes or new endpoints
138- Complex algorithms or business logic
139- State management changes
140- Multiple packages require changes
141- Infrastructure-as-code updates needed
142 
143**Skip IF**:
144- Simple logic changes
145- UI-only changes
146- Configuration updates
147- Straightforward implementations
148 
149### 3.4 NFR Implementation - Execute IF:
150- Performance requirements
151- Security considerations
152- Scalability concerns
153- Monitoring/observability needed
154 
155**Skip IF**:
156- Existing NFR setup sufficient
157- No new NFR requirements
158- Simple changes with no NFR impact
159 
160## Step 4: Note Adaptive Detail
161 
162**See [depth-levels.md](../common/depth-levels.md) for adaptive depth explanation**
163 
164For each stage that will execute:
165- All defined artifacts will be created
166- Detail level within artifacts adapts to problem complexity
167- Model determines appropriate detail based on problem characteristics
168 
169## Step 5: Multi-Module Coordination Analysis (Brownfield Only)
170 
171**IF brownfield with multiple modules/packages**, analyze dependencies and determine optimal update strategy:
172 
173### 5.1 Analyze Module Dependencies
174- Examine build system dependencies and dependency manifests
175- Identify build-time vs runtime dependencies
176- Map API contracts and shared interfaces between modules
177 
178### 5.2 Determine Update Strategy
179Based on dependency analysis, decide:
180- **Update sequence**: Which modules must be updated first due to dependencies
181- **Parallelization opportunities**: Which modules can be updated simultaneously
182- **Coordination requirements**: Version compatibility, API contracts, deployment order
183- **Testing strategy**: Per-module vs integrated testing approach
184- **Rollback strategy**: Recovery plan if mid-sequence failures occur
185 
186### 5.3 Document Coordination Plan
187```markdown
188## Module Update Strategy
189- **Update Approach**: [Sequential/Parallel/Hybrid]
190- **Critical Path**: [Modules that block other updates]
191- **Coordination Points**: [Shared APIs, infrastructure, data contracts]
192- **Testing Checkpoints**: [When to validate integration]
193```
194 
195Identify for each affected module:
196- **Update priority**: Must-update-first vs can-update-later
197- **Dependency constraints**: What it depends on, what depends on it
198- **Change scope**: Major (breaking), Minor (compatible), Patch (fixes)
199 
200## Step 6: Generate Workflow Visualization
201 
202Create Mermaid flowchart showing:
203- All phases in sequence
204- EXECUTE or SKIP decision for each conditional phase
205- Proper styling for each phase state
206 
207**Styling rules** (add after flowchart):
208```
209style WD fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
210style CG fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
211style BT fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
212style US fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000
213style Start fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,color:#000
214style End fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,color:#000
215 
216linkStyle default stroke:#333,stroke-width:2px
217```
218 
219**Style Guidelines**:
220- Completed/Always execute: `fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff` (Material Green with white text)
221- Conditional EXECUTE: `fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000` (Material Orange with black text)
222- Conditional SKIP: `fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000` (Material Gray with black text)
223- Start/End: `fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,color:#000` (Material Purple with black text)
224- Phase containers: Use lighter Material colors (INCEPTION: #BBDEFB, CONSTRUCTION: #C8E6C9, OPERATIONS: #FFF59D)
225 
226## Step 7: Create Execution Plan Document
227 
228Create `aidlc-docs/inception/plans/execution-plan.md`:
229 
230```markdown
231# Execution Plan
232 
233## Detailed Analysis Summary
234 
235### Transformation Scope (Brownfield Only)
236- **Transformation Type**: [Single component/Architectural/Infrastructure]
237- **Primary Changes**: [Description]
238- **Related Components**: [List]
239 
240### Change Impact Assessment
241- **User-facing changes**: [Yes/No - Description]
242- **Structural changes**: [Yes/No - Description]
243- **Data model changes**: [Yes/No - Description]
244- **API changes**: [Yes/No - Description]
245- **NFR impact**: [Yes/No - Description]
246 
247### Component Relationships (Brownfield Only)
248[Component dependency graph]
249 
250### Risk Assessment
251- **Risk Level**: [Low/Medium/High/Critical]
252- **Rollback Complexity**: [Easy/Moderate/Difficult]
253- **Testing Complexity**: [Simple/Moderate/Complex]
254 
255## Workflow Visualization
256 
257```mermaid
258flowchart TD
259    Start(["User Request"])
260    
261    subgraph INCEPTION["🔵 INCEPTION PHASE"]
262        WD["Workspace Detection<br/><b>STATUS</b>"]
263        RE["Reverse Engineering<br/><b>STATUS</b>"]
264        RA["Requirements Analysis<br/><b>STATUS</b>"]
265        US["User Stories<br/><b>STATUS</b>"]
266        WP["Workflow Planning<br/><b>STATUS</b>"]
267        AD["Application Design<br/><b>STATUS</b>"]
268        UP["Units Planning<br/><b>STATUS</b>"]
269        UG["Units Generation<br/><b>STATUS</b>"]
270    end
271    
272    subgraph CONSTRUCTION["🟢 CONSTRUCTION PHASE"]
273        FD["Functional Design<br/><b>STATUS</b>"]
274        NFRA["NFR Requirements<br/><b>STATUS</b>"]
275        NFRD["NFR Design<br/><b>STATUS</b>"]
276        ID["Infrastructure Design<br/><b>STATUS</b>"]
277        CG["Code Generation<br/>(Planning + Generation)<br/><b>EXECUTE</b>"]
278        BT["Build and Test<br/><b>EXECUTE</b>"]
279    end
280    
281    subgraph OPERATIONS["🟡 OPERATIONS PHASE"]
282        OPS["Operations<br/><b>PLACEHOLDER</b>"]
283    end
284    
285    Start --> WD
286    WD --> RA
287    RA --> WP
288    WP --> CG
289    CG --> BT
290    BT --> End(["Complete"])
291    
292    %% Replace STATUS with COMPLETED, SKIP, EXECUTE as appropriate
293    %% Apply styling based on status
294```
295 
296**Note**: Replace STATUS placeholders with actual phase status (COMPLETED/SKIP/EXECUTE) and apply appropriate styling
297 
298## Phases to Execute
299 
300### 🔵 INCEPTION PHASE
301- [x] Workspace Detection (COMPLETED)
302- [x] Reverse Engineering (COMPLETED/SKIPPED)
303- [x] Requirements Analysis (COMPLETED)
304- [x] User Stories (COMPLETED/SKIPPED)
305- [x] Execution Plan (IN PROGRESS)
306- [ ] Application Design - [EXECUTE/SKIP]
307  - **Rationale**: [Why executing or skipping]
308- [ ] Units Planning - [EXECUTE/SKIP]
309  - **Rationale**: [Why executing or skipping]
310- [ ] Units Generation - [EXECUTE/SKIP]
311  - **Rationale**: [Why executing or skipping]
312 
313### 🟢 CONSTRUCTION PHASE
314- [ ] Functional Design - [EXECUTE/SKIP]
315  - **Rationale**: [Why executing or skipping]
316- [ ] NFR Requirements - [EXECUTE/SKIP]
317  - **Rationale**: [Why executing or skipping]
318- [ ] NFR Design - [EXECUTE/SKIP]
319  - **Rationale**: [Why executing or skipping]
320- [ ] Infrastructure Design - [EXECUTE/SKIP]
321  - **Rationale**: [Why executing or skipping]
322- [ ] Code Generation - EXECUTE (ALWAYS)
323  - **Rationale**: Implementation planning and code generation needed
324- [ ] Build and Test - EXECUTE (ALWAYS)
325  - **Rationale**: Build, test, and verification needed
326 
327### 🟡 OPERATIONS PHASE
328- [ ] Operations - PLACEHOLDER
329  - **Rationale**: Future deployment and monitoring workflows
330 
331## Package Change Sequence (Brownfield Only)
332[If applicable, list package update sequence with dependencies]
333 
334## Estimated Timeline
335- **Total Phases**: [Number]
336- **Estimated Duration**: [Time estimate]
337 
338## Success Criteria
339- **Primary Goal**: [Main objective]
340- **Key Deliverables**: [List]
341- **Quality Gates**: [List]
342 
343[IF brownfield]
344- **Integration Testing**: All components working together
345- **Operational Readiness**: Monitoring, logging, alerting working
346```
347 
348## Step 8: Initialize State Tracking
349 
350Update `aidlc-docs/aidlc-state.md`:
351 
352```markdown
353# AI-DLC State Tracking
354 
355## Project Information
356- **Project Type**: [Greenfield/Brownfield]
357- **Start Date**: [ISO timestamp]
358- **Current Stage**: INCEPTION - Workflow Planning
359 
360## Execution Plan Summary
361- **Total Stages**: [Number]
362- **Stages to Execute**: [List]
363- **Stages to Skip**: [List with reasons]
364 
365## Stage Progress
366 
367### 🔵 INCEPTION PHASE
368- [x] Workspace Detection
369- [x] Reverse Engineering (if applicable)
370- [x] Requirements Analysis
371- [x] User Stories (if applicable)
372- [x] Workflow Planning
373- [ ] Application Design - [EXECUTE/SKIP]
374- [ ] Units Planning - [EXECUTE/SKIP]
375- [ ] Units Generation - [EXECUTE/SKIP]
376 
377### 🟢 CONSTRUCTION PHASE
378- [ ] Functional Design - [EXECUTE/SKIP]
379- [ ] NFR Requirements - [EXECUTE/SKIP]
380- [ ] NFR Design - [EXECUTE/SKIP]
381- [ ] Infrastructure Design - [EXECUTE/SKIP]
382- [ ] Code Generation - EXECUTE
383- [ ] Build and Test - EXECUTE
384 
385### 🟡 OPERATIONS PHASE
386- [ ] Operations - PLACEHOLDER
387 
388## Current Status
389- **Lifecycle Phase**: INCEPTION
390- **Current Stage**: Workflow Planning Complete
391- **Next Stage**: [Next stage to execute]
392- **Status**: Ready to proceed
393```
394 
395## Step 9: Present Plan to User
396 
397```markdown
398# 📋 Workflow Planning Complete
399 
400I've created a comprehensive execution plan based on:
401- Your request: [Summary]
402- Existing system: [Summary if brownfield]
403- Requirements: [Summary if executed]
404- User stories: [Summary if executed]
405 
406**Detailed Analysis**:
407- Risk level: [Level]
408- Impact: [Summary of key impacts]
409- Components affected: [List]
410 
411**Recommended Execution Plan**:
412 
413I recommend executing [X] stages:
414 
415🔵 **INCEPTION PHASE:**
4161. [Stage name] - *Rationale:* [Why executing]
4172. [Stage name] - *Rationale:* [Why executing]
418...
419 
420🟢 **CONSTRUCTION PHASE:**
4213. [Stage name] - *Rationale:* [Why executing]
4224. [Stage name] - *Rationale:* [Why executing]
423...
424 
425I recommend skipping [Y] stages:
426 
427🔵 **INCEPTION PHASE:**
4281. [Stage name] - *Rationale:* [Why skipping]
4292. [Stage name] - *Rationale:* [Why skipping]
430...
431 
432🟢 **CONSTRUCTION PHASE:**
4333. [Stage name] - *Rationale:* [Why skipping]
4344. [Stage name] - *Rationale:* [Why skipping]
435...
436 
437[IF brownfield with multiple packages]
438**Recommended Package Update Sequence**:
4391. [Package] - [Reason]
4402. [Package] - [Reason]
441...
442 
443**Estimated Timeline**: [Duration]
444 
445> **📋 <u>**REVIEW REQUIRED:**</u>**  
446> Please examine the execution plan at: `aidlc-docs/inception/plans/execution-plan.md`
447 
448> **🚀 <u>**WHAT'S NEXT?**</u>**
449>
450> **You may:**
451>
452> 🔧 **Request Changes** - Ask for modifications to the execution plan if required
453> [IF any stages are skipped:]
454> 📝 **Add Skipped Stages** - Choose to include stages currently marked as SKIP
455> ✅ **Approve & Continue** - Approve plan and proceed to **[Next Stage Name]**
456```
457 
458## Step 10: Handle User Response
459 
460- **If approved**: Proceed to next stage in execution plan
461- **If changes requested**: Update execution plan and re-confirm
462- **If user wants to force include/exclude stages**: Update plan accordingly
463 
464## Step 11: Log Interaction
465 
466Log in `aidlc-docs/audit.md`:
467 
468```markdown
469## Workflow Planning - Approval
470**Timestamp**: [ISO timestamp]
471**AI Prompt**: "Ready to proceed with this plan?"
472**User Response**: "[User's COMPLETE RAW response]"
473**Status**: [Approved/Changes Requested]
474**Context**: Workflow plan created with [X] stages to execute
475 
476---
477```
478