olympus-ai 4.0.2 → 4.0.4

package/resources/rules/inception/workflow-planning.md

@@ -1,487 +1,487 @@
-# Workflow Planning
-
-**Purpose**: Determine which phases to execute and create comprehensive execution plan
-
-**Always Execute**: This phase always runs after understanding requirements and scope
-
-## Execution Model
-
-**Orchestrator-only stage** — no agent delegation. Workflow Planning is meta-planning: the orchestrator synthesizes all prior context (requirements, stories, reverse engineering) to determine which stages to execute and at what depth. Delegating this work would be circular, as the output of this stage drives all subsequent delegation decisions. The orchestrator executes all steps directly.
-
-## Step 1: Load All Prior Context
-
-### 1.1 Load Reverse Engineering Artifacts (if brownfield)
-- architecture.md
-- component-inventory.md
-- technology-stack.md
-- dependencies.md
-
-### 1.2 Load Requirements Analysis
-- requirements.md (includes intent analysis)
-- requirement-verification-questions.md (with answers)
-
-### 1.3 Load User Stories (if executed)
-- stories.md
-- personas.md
-
-## Step 2: Detailed Scope and Impact Analysis
-
-**Now that we have complete context (requirements + stories), perform detailed analysis:**
-
-### 2.1 Transformation Scope Detection (Brownfield Only)
-
-**IF brownfield project**, analyze transformation scope:
-
-#### Architectural Transformation
-- **Single component change** vs **architectural transformation**
-- **Infrastructure changes** vs **application changes**
-- **Deployment model changes** (Lambda→Container, EC2→Serverless, etc.)
-
-#### Related Component Identification
-For transformations, identify:
-- **Infrastructure code** that needs updates
-- **CDK stacks** requiring changes
-- **API Gateway** configurations
-- **Load balancer** requirements
-- **Networking** changes needed
-- **Monitoring/logging** adaptations
-
-#### Cross-Package Impact
-- **CDK infrastructure** packages requiring updates
-- **Shared models** needing version updates
-- **Client libraries** requiring endpoint changes
-- **Test packages** needing new test scenarios
-
-### 2.2 Change Impact Assessment
-
-#### Impact Areas
-1. **User-facing changes**: Does this affect user experience?
-2. **Structural changes**: Does this change system architecture?
-3. **Data model changes**: Does this affect database schemas or data structures?
-4. **API changes**: Does this affect interfaces or contracts?
-5. **NFR impact**: Does this affect performance, security, or scalability?
-
-#### Application Layer Impact (if applicable)
-- **Code changes**: New entry points, adapters, configurations
-- **Dependencies**: New libraries, framework changes
-- **Configuration**: Environment variables, config files
-- **Testing**: Unit tests, integration tests
-
-#### Infrastructure Layer Impact (if applicable)
-- **Deployment model**: Lambda→ECS, EC2→Fargate, etc.
-- **Networking**: VPC, security groups, load balancers
-- **Storage**: Persistent volumes, shared storage
-- **Scaling**: Auto-scaling policies, capacity planning
-
-#### Operations Layer Impact (if applicable)
-- **Monitoring**: CloudWatch, custom metrics, dashboards
-- **Logging**: Log aggregation, structured logging
-- **Alerting**: Alarm configurations, notification channels
-- **Deployment**: CI/CD pipeline changes, rollback strategies
-
-### 2.3 Component Relationship Mapping (Brownfield Only)
-
-**IF brownfield project**, create component dependency graph:
-
-```markdown
-## Component Relationships
-- **Primary Component**: [Package being changed]
-- **Infrastructure Components**: [CDK/Terraform packages]
-- **Shared Components**: [Models, utilities, clients]
-- **Dependent Components**: [Services that call this component]
-- **Supporting Components**: [Monitoring, logging, deployment]
-```
-
-For each related component:
-- **Change Type**: Major, Minor, Configuration-only
-- **Change Reason**: Direct dependency, deployment model, networking
-- **Change Priority**: Critical, Important, Optional
-
-### 2.4 Risk Assessment
-
-Evaluate risk level:
-1. **Low**: Isolated change, easy rollback, well-understood
-2. **Medium**: Multiple components, moderate rollback, some unknowns
-3. **High**: System-wide impact, complex rollback, significant unknowns
-4. **Critical**: Production-critical, difficult rollback, high uncertainty
-
-## Step 3: Phase Determination
-
-### 3.1 User Stories - Already Executed or Skip?
-**Already executed**: Move to next determination
-**Not executed - Execute IF**:
-- Multiple user personas
-- User experience impact
-- Acceptance criteria needed
-- Team collaboration required
-
-**Skip IF**:
-- Internal refactoring
-- Bug fix with clear reproduction
-- Technical debt reduction
-- Infrastructure changes
-
-### 3.2 Application Design - Execute IF:
-- New components or services needed
-- Component methods and business rules need definition
-- Service layer design required
-- Component dependencies need clarification
-
-**Skip IF**:
-- Changes within existing component boundaries
-- No new components or methods
-- Pure implementation changes
-
-### 3.3 Design (Units Planning/Generation) - Execute IF:
-- New data models or schemas
-- API changes or new endpoints
-- Complex algorithms or business logic
-- State management changes
-- Multiple packages require changes
-- Infrastructure-as-code updates needed
-
-**Skip IF**:
-- Simple logic changes
-- UI-only changes
-- Configuration updates
-- Straightforward implementations
-
-### 3.4 NFR Implementation - Execute IF:
-- Performance requirements
-- Security considerations
-- Scalability concerns
-- Monitoring/observability needed
-
-**Skip IF**:
-- Existing NFR setup sufficient
-- No new NFR requirements
-- Simple changes with no NFR impact
-
-## Step 4: Note Adaptive Detail
-
-**See [depth-levels.md](../common/depth-levels.md) for adaptive depth explanation**
-
-For each stage that will execute:
-- All defined artifacts will be created
-- Detail level within artifacts adapts to problem complexity
-- Model determines appropriate detail based on problem characteristics
-
-## Step 5: Multi-Module Coordination Analysis (Brownfield Only)
-
-**IF brownfield with multiple modules/packages**, analyze dependencies and determine optimal update strategy:
-
-### 5.1 Analyze Module Dependencies
-- Examine build system dependencies and dependency manifests
-- Identify build-time vs runtime dependencies
-- Map API contracts and shared interfaces between modules
-
-### 5.2 Determine Update Strategy
-Based on dependency analysis, decide:
-- **Update sequence**: Which modules must be updated first due to dependencies
-- **Parallelization opportunities**: Which modules can be updated simultaneously
-- **Coordination requirements**: Version compatibility, API contracts, deployment order
-- **Testing strategy**: Per-module vs integrated testing approach
-- **Rollback strategy**: Recovery plan if mid-sequence failures occur
-
-### 5.3 Document Coordination Plan
-```markdown
-## Module Update Strategy
-- **Update Approach**: [Sequential/Parallel/Hybrid]
-- **Critical Path**: [Modules that block other updates]
-- **Coordination Points**: [Shared APIs, infrastructure, data contracts]
-- **Testing Checkpoints**: [When to validate integration]
-```
-
-Identify for each affected module:
-- **Update priority**: Must-update-first vs can-update-later
-- **Dependency constraints**: What it depends on, what depends on it
-- **Change scope**: Major (breaking), Minor (compatible), Patch (fixes)
-
-## Step 6: Generate Workflow Visualization
-
-Create Mermaid flowchart showing:
-- All phases in sequence
-- EXECUTE or SKIP decision for each conditional phase
-- Proper styling for each phase state
-
-**Styling rules** (add after flowchart):
-```
-style WD fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
-style CP fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
-style CG fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
-style BT fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
-style US fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000
-style Start fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,color:#000
-style End fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,color:#000
-
-linkStyle default stroke:#333,stroke-width:2px
-```
-
-**Style Guidelines**:
-- Completed/Always execute: `fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff` (Material Green with white text)
-- Conditional EXECUTE: `fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000` (Material Orange with black text)
-- Conditional SKIP: `fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000` (Material Gray with black text)
-- Start/End: `fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,color:#000` (Material Purple with black text)
-- Phase containers: Use lighter Material colors (INCEPTION: #BBDEFB, CONSTRUCTION: #C8E6C9, OPERATIONS: #FFF59D)
-
-## Step 7: Create Execution Plan Document
-
-Create `aidlc-docs/inception/plans/execution-plan.md`:
-
-```markdown
-# Execution Plan
-
-## Detailed Analysis Summary
-
-### Transformation Scope (Brownfield Only)
-- **Transformation Type**: [Single component/Architectural/Infrastructure]
-- **Primary Changes**: [Description]
-- **Related Components**: [List]
-
-### Change Impact Assessment
-- **User-facing changes**: [Yes/No - Description]
-- **Structural changes**: [Yes/No - Description]
-- **Data model changes**: [Yes/No - Description]
-- **API changes**: [Yes/No - Description]
-- **NFR impact**: [Yes/No - Description]
-
-### Component Relationships (Brownfield Only)
-[Component dependency graph]
-
-### Risk Assessment
-- **Risk Level**: [Low/Medium/High/Critical]
-- **Rollback Complexity**: [Easy/Moderate/Difficult]
-- **Testing Complexity**: [Simple/Moderate/Complex]
-
-## Workflow Visualization
-
-```mermaid
-flowchart TD
-    Start(["User Request"])
-    
-    subgraph INCEPTION["🔵 INCEPTION PHASE"]
-        WD["Workspace Detection<br/><b>STATUS</b>"]
-        RE["Reverse Engineering<br/><b>STATUS</b>"]
-        RA["Requirements Analysis<br/><b>STATUS</b>"]
-        US["User Stories<br/><b>STATUS</b>"]
-        WP["Workflow Planning<br/><b>STATUS</b>"]
-        AD["Application Design<br/><b>STATUS</b>"]
-        UP["Units Planning<br/><b>STATUS</b>"]
-        UG["Units Generation<br/><b>STATUS</b>"]
-    end
-    
-    subgraph CONSTRUCTION["🟢 CONSTRUCTION PHASE"]
-        FD["Functional Design<br/><b>STATUS</b>"]
-        NFRA["NFR Requirements<br/><b>STATUS</b>"]
-        NFRD["NFR Design<br/><b>STATUS</b>"]
-        ID["Infrastructure Design<br/><b>STATUS</b>"]
-        CP["Code Planning<br/><b>EXECUTE</b>"]
-        CG["Code Generation<br/><b>EXECUTE</b>"]
-        BT["Build and Test<br/><b>EXECUTE</b>"]
-    end
-    
-    subgraph OPERATIONS["🟡 OPERATIONS PHASE"]
-        OPS["Operations<br/><b>PLACEHOLDER</b>"]
-    end
-    
-    Start --> WD
-    WD --> RA
-    RA --> WP
-    WP --> CP
-    CP --> CG
-    CG --> BT
-    BT --> End(["Complete"])
-    
-    %% Replace STATUS with COMPLETED, SKIP, EXECUTE as appropriate
-    %% Apply styling based on status
-```
-
-**Note**: Replace STATUS placeholders with actual phase status (COMPLETED/SKIP/EXECUTE) and apply appropriate styling
-
-## Phases to Execute
-
-### 🔵 INCEPTION PHASE
-- [x] Workspace Detection (COMPLETED)
-- [x] Reverse Engineering (COMPLETED/SKIPPED)
-- [x] Requirements Elaboration (COMPLETED)
-- [x] User Stories (COMPLETED/SKIPPED)
-- [x] Execution Plan (IN PROGRESS)
-- [ ] Application Design - [EXECUTE/SKIP]
-  - **Rationale**: [Why executing or skipping]
-- [ ] Units Planning - [EXECUTE/SKIP]
-  - **Rationale**: [Why executing or skipping]
-- [ ] Units Generation - [EXECUTE/SKIP]
-  - **Rationale**: [Why executing or skipping]
-
-### 🟢 CONSTRUCTION PHASE
-- [ ] Functional Design - [EXECUTE/SKIP]
-  - **Rationale**: [Why executing or skipping]
-- [ ] NFR Requirements - [EXECUTE/SKIP]
-  - **Rationale**: [Why executing or skipping]
-- [ ] NFR Design - [EXECUTE/SKIP]
-  - **Rationale**: [Why executing or skipping]
-- [ ] Infrastructure Design - [EXECUTE/SKIP]
-  - **Rationale**: [Why executing or skipping]
-- [ ] Code Planning - EXECUTE (ALWAYS)
-  - **Rationale**: Implementation approach needed
-- [ ] Code Generation - EXECUTE (ALWAYS)
-  - **Rationale**: Code implementation needed
-- [ ] Build and Test - EXECUTE (ALWAYS)
-  - **Rationale**: Build, test, and verification needed
-
-### 🟡 OPERATIONS PHASE
-- [ ] Operations - PLACEHOLDER
-  - **Rationale**: Future deployment and monitoring workflows
-
-## Package Change Sequence (Brownfield Only)
-[If applicable, list package update sequence with dependencies]
-
-## Estimated Timeline
-- **Total Phases**: [Number]
-- **Estimated Duration**: [Time estimate]
-
-## Success Criteria
-- **Primary Goal**: [Main objective]
-- **Key Deliverables**: [List]
-- **Quality Gates**: [List]
-
-[IF brownfield]
-- **Integration Testing**: All components working together
-- **Operational Readiness**: Monitoring, logging, alerting working
-```
-
-## Step 8: MANDATORY: Initialize State Tracking
-
-**MANDATORY**: Update BOTH state files in the SAME interaction:
-1. Update `aidlc-docs/{workflow-id}/aidlc-state.md`:
-
-```markdown
-# AI-DLC State Tracking
-
-## Project Information
-- **Project Type**: [Greenfield/Brownfield]
-- **Start Date**: [ISO timestamp]
-- **Current Stage**: INCEPTION - Workflow Planning
-
-## Execution Plan Summary
-- **Total Stages**: [Number]
-- **Stages to Execute**: [List]
-- **Stages to Skip**: [List with reasons]
-
-## Stage Progress
-
-### 🔵 INCEPTION PHASE
-- [x] Workspace Detection
-- [x] Reverse Engineering (if applicable)
-- [x] Requirements Analysis
-- [x] User Stories (if applicable)
-- [x] Workflow Planning
-- [ ] Application Design - [EXECUTE/SKIP]
-- [ ] Units Planning - [EXECUTE/SKIP]
-- [ ] Units Generation - [EXECUTE/SKIP]
-
-### 🟢 CONSTRUCTION PHASE
-- [ ] Functional Design - [EXECUTE/SKIP]
-- [ ] NFR Requirements - [EXECUTE/SKIP]
-- [ ] NFR Design - [EXECUTE/SKIP]
-- [ ] Infrastructure Design - [EXECUTE/SKIP]
-- [ ] Code Planning - EXECUTE
-- [ ] Code Generation - EXECUTE
-- [ ] Build and Test - EXECUTE
-
-### 🟡 OPERATIONS PHASE
-- [ ] Operations - PLACEHOLDER
-
-## Current Status
-- **Lifecycle Phase**: INCEPTION
-- **Current Stage**: Workflow Planning Complete
-- **Next Stage**: [Next stage to execute]
-- **Status**: Ready to proceed
-```
-
-2. Update `aidlc-docs/{workflow-id}/checkpoint.json` — initialize workflow state with all stage statuses, current_inception_stage set to next stage after Workflow Planning
-- **Do NOT proceed to the next stage without completing this step**
-
-## Step 9: Present Plan to User
-
-```markdown
-# 📋 Workflow Planning Complete
-
-I've created a comprehensive execution plan based on:
-- Your request: [Summary]
-- Existing system: [Summary if brownfield]
-- Requirements: [Summary if executed]
-- User stories: [Summary if executed]
-
-**Detailed Analysis**:
-- Risk level: [Level]
-- Impact: [Summary of key impacts]
-- Components affected: [List]
-
-**Recommended Execution Plan**:
-
-I recommend executing [X] stages:
-
-🔵 **INCEPTION PHASE:**
-1. [Stage name] - *Rationale:* [Why executing]
-2. [Stage name] - *Rationale:* [Why executing]
-...
-
-🟢 **CONSTRUCTION PHASE:**
-3. [Stage name] - *Rationale:* [Why executing]
-4. [Stage name] - *Rationale:* [Why executing]
-...
-
-I recommend skipping [Y] stages:
-
-🔵 **INCEPTION PHASE:**
-1. [Stage name] - *Rationale:* [Why skipping]
-2. [Stage name] - *Rationale:* [Why skipping]
-...
-
-🟢 **CONSTRUCTION PHASE:**
-3. [Stage name] - *Rationale:* [Why skipping]
-4. [Stage name] - *Rationale:* [Why skipping]
-...
-
-[IF brownfield with multiple packages]
-**Recommended Package Update Sequence**:
-1. [Package] - [Reason]
-2. [Package] - [Reason]
-...
-
-**Estimated Timeline**: [Duration]
-
-> **📋 <u>**REVIEW REQUIRED:**</u>**  
-> Please examine the execution plan at: `aidlc-docs/inception/plans/execution-plan.md`
-
-> **🚀 <u>**WHAT'S NEXT?**</u>**
->
-> **You may:**
->
-> 🔧 **Request Changes** - Ask for modifications to the execution plan if required
-> [IF any stages are skipped:]
-> 📝 **Add Skipped Stages** - Choose to include stages currently marked as SKIP
-> ✅ **Approve & Continue** - Approve plan and proceed to **[Next Stage Name]**
-```
-
-## Step 10: Handle User Response
-
-- **If approved**: Proceed to next stage in execution plan
-- **If changes requested**: Update execution plan and re-confirm
-- **If user wants to force include/exclude stages**: Update plan accordingly
-
-## Step 11: Log Interaction
-
-Log in `aidlc-docs/audit.md`:
-
-```markdown
-## Workflow Planning - Approval
-**Timestamp**: [ISO timestamp]
-**AI Prompt**: "Ready to proceed with this plan?"
-**User Response**: "[User's COMPLETE RAW response]"
-**Status**: [Approved/Changes Requested]
-**Context**: Workflow plan created with [X] stages to execute
-
----
-```
+# Workflow Planning
+
+**Purpose**: Determine which phases to execute and create comprehensive execution plan
+
+**Always Execute**: This phase always runs after understanding requirements and scope
+
+## Execution Model
+
+**Orchestrator-only stage** — no agent delegation. Workflow Planning is meta-planning: the orchestrator synthesizes all prior context (requirements, stories, reverse engineering) to determine which stages to execute and at what depth. Delegating this work would be circular, as the output of this stage drives all subsequent delegation decisions. The orchestrator executes all steps directly.
+
+## Step 1: Load All Prior Context
+
+### 1.1 Load Reverse Engineering Artifacts (if brownfield)
+- architecture.md
+- component-inventory.md
+- technology-stack.md
+- dependencies.md
+
+### 1.2 Load Requirements Analysis
+- requirements.md (includes intent analysis)
+- requirements-analysis-questions.md (with answers)
+
+### 1.3 Load User Stories (if executed)
+- stories.md
+- personas.md
+
+## Step 2: Detailed Scope and Impact Analysis
+
+**Now that we have complete context (requirements + stories), perform detailed analysis:**
+
+### 2.1 Transformation Scope Detection (Brownfield Only)
+
+**IF brownfield project**, analyze transformation scope:
+
+#### Architectural Transformation
+- **Single component change** vs **architectural transformation**
+- **Infrastructure changes** vs **application changes**
+- **Deployment model changes** (Lambda→Container, EC2→Serverless, etc.)
+
+#### Related Component Identification
+For transformations, identify:
+- **Infrastructure code** that needs updates
+- **CDK stacks** requiring changes
+- **API Gateway** configurations
+- **Load balancer** requirements
+- **Networking** changes needed
+- **Monitoring/logging** adaptations
+
+#### Cross-Package Impact
+- **CDK infrastructure** packages requiring updates
+- **Shared models** needing version updates
+- **Client libraries** requiring endpoint changes
+- **Test packages** needing new test scenarios
+
+### 2.2 Change Impact Assessment
+
+#### Impact Areas
+1. **User-facing changes**: Does this affect user experience?
+2. **Structural changes**: Does this change system architecture?
+3. **Data model changes**: Does this affect database schemas or data structures?
+4. **API changes**: Does this affect interfaces or contracts?
+5. **NFR impact**: Does this affect performance, security, or scalability?
+
+#### Application Layer Impact (if applicable)
+- **Code changes**: New entry points, adapters, configurations
+- **Dependencies**: New libraries, framework changes
+- **Configuration**: Environment variables, config files
+- **Testing**: Unit tests, integration tests
+
+#### Infrastructure Layer Impact (if applicable)
+- **Deployment model**: Lambda→ECS, EC2→Fargate, etc.
+- **Networking**: VPC, security groups, load balancers
+- **Storage**: Persistent volumes, shared storage
+- **Scaling**: Auto-scaling policies, capacity planning
+
+#### Operations Layer Impact (if applicable)
+- **Monitoring**: CloudWatch, custom metrics, dashboards
+- **Logging**: Log aggregation, structured logging
+- **Alerting**: Alarm configurations, notification channels
+- **Deployment**: CI/CD pipeline changes, rollback strategies
+
+### 2.3 Component Relationship Mapping (Brownfield Only)
+
+**IF brownfield project**, create component dependency graph:
+
+```markdown
+## Component Relationships
+- **Primary Component**: [Package being changed]
+- **Infrastructure Components**: [CDK/Terraform packages]
+- **Shared Components**: [Models, utilities, clients]
+- **Dependent Components**: [Services that call this component]
+- **Supporting Components**: [Monitoring, logging, deployment]
+```
+
+For each related component:
+- **Change Type**: Major, Minor, Configuration-only
+- **Change Reason**: Direct dependency, deployment model, networking
+- **Change Priority**: Critical, Important, Optional
+
+### 2.4 Risk Assessment
+
+Evaluate risk level:
+1. **Low**: Isolated change, easy rollback, well-understood
+2. **Medium**: Multiple components, moderate rollback, some unknowns
+3. **High**: System-wide impact, complex rollback, significant unknowns
+4. **Critical**: Production-critical, difficult rollback, high uncertainty
+
+## Step 3: Phase Determination
+
+### 3.1 User Stories - Already Executed or Skip?
+**Already executed**: Move to next determination
+**Not executed - Execute IF**:
+- Multiple user personas
+- User experience impact
+- Acceptance criteria needed
+- Team collaboration required
+
+**Skip IF**:
+- Internal refactoring
+- Bug fix with clear reproduction
+- Technical debt reduction
+- Infrastructure changes
+
+### 3.2 Application Design - Execute IF:
+- New components or services needed
+- Component methods and business rules need definition
+- Service layer design required
+- Component dependencies need clarification
+
+**Skip IF**:
+- Changes within existing component boundaries
+- No new components or methods
+- Pure implementation changes
+
+### 3.3 Design (Units Planning/Generation) - Execute IF:
+- New data models or schemas
+- API changes or new endpoints
+- Complex algorithms or business logic
+- State management changes
+- Multiple packages require changes
+- Infrastructure-as-code updates needed
+
+**Skip IF**:
+- Simple logic changes
+- UI-only changes
+- Configuration updates
+- Straightforward implementations
+
+### 3.4 NFR Implementation - Execute IF:
+- Performance requirements
+- Security considerations
+- Scalability concerns
+- Monitoring/observability needed
+
+**Skip IF**:
+- Existing NFR setup sufficient
+- No new NFR requirements
+- Simple changes with no NFR impact
+
+## Step 4: Note Adaptive Detail
+
+**See [depth-levels.md](../common/depth-levels.md) for adaptive depth explanation**
+
+For each stage that will execute:
+- All defined artifacts will be created
+- Detail level within artifacts adapts to problem complexity
+- Model determines appropriate detail based on problem characteristics
+
+## Step 5: Multi-Module Coordination Analysis (Brownfield Only)
+
+**IF brownfield with multiple modules/packages**, analyze dependencies and determine optimal update strategy:
+
+### 5.1 Analyze Module Dependencies
+- Examine build system dependencies and dependency manifests
+- Identify build-time vs runtime dependencies
+- Map API contracts and shared interfaces between modules
+
+### 5.2 Determine Update Strategy
+Based on dependency analysis, decide:
+- **Update sequence**: Which modules must be updated first due to dependencies
+- **Parallelization opportunities**: Which modules can be updated simultaneously
+- **Coordination requirements**: Version compatibility, API contracts, deployment order
+- **Testing strategy**: Per-module vs integrated testing approach
+- **Rollback strategy**: Recovery plan if mid-sequence failures occur
+
+### 5.3 Document Coordination Plan
+```markdown
+## Module Update Strategy
+- **Update Approach**: [Sequential/Parallel/Hybrid]
+- **Critical Path**: [Modules that block other updates]
+- **Coordination Points**: [Shared APIs, infrastructure, data contracts]
+- **Testing Checkpoints**: [When to validate integration]
+```
+
+Identify for each affected module:
+- **Update priority**: Must-update-first vs can-update-later
+- **Dependency constraints**: What it depends on, what depends on it
+- **Change scope**: Major (breaking), Minor (compatible), Patch (fixes)
+
+## Step 6: Generate Workflow Visualization
+
+Create Mermaid flowchart showing:
+- All phases in sequence
+- EXECUTE or SKIP decision for each conditional phase
+- Proper styling for each phase state
+
+**Styling rules** (add after flowchart):
+```
+style WD fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
+style CP fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
+style CG fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
+style BT fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
+style US fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000
+style Start fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,color:#000
+style End fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,color:#000
+
+linkStyle default stroke:#333,stroke-width:2px
+```
+
+**Style Guidelines**:
+- Completed/Always execute: `fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff` (Material Green with white text)
+- Conditional EXECUTE: `fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000` (Material Orange with black text)
+- Conditional SKIP: `fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000` (Material Gray with black text)
+- Start/End: `fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,color:#000` (Material Purple with black text)
+- Phase containers: Use lighter Material colors (INCEPTION: #BBDEFB, CONSTRUCTION: #C8E6C9, OPERATIONS: #FFF59D)
+
+## Step 7: Create Execution Plan Document
+
+Create `aidlc-docs/inception/plans/execution-plan.md`:
+
+```markdown
+# Execution Plan
+
+## Detailed Analysis Summary
+
+### Transformation Scope (Brownfield Only)
+- **Transformation Type**: [Single component/Architectural/Infrastructure]
+- **Primary Changes**: [Description]
+- **Related Components**: [List]
+
+### Change Impact Assessment
+- **User-facing changes**: [Yes/No - Description]
+- **Structural changes**: [Yes/No - Description]
+- **Data model changes**: [Yes/No - Description]
+- **API changes**: [Yes/No - Description]
+- **NFR impact**: [Yes/No - Description]
+
+### Component Relationships (Brownfield Only)
+[Component dependency graph]
+
+### Risk Assessment
+- **Risk Level**: [Low/Medium/High/Critical]
+- **Rollback Complexity**: [Easy/Moderate/Difficult]
+- **Testing Complexity**: [Simple/Moderate/Complex]
+
+## Workflow Visualization
+
+```mermaid
+flowchart TD
+    Start(["User Request"])
+    
+    subgraph INCEPTION["🔵 INCEPTION PHASE"]
+        WD["Workspace Detection<br/><b>STATUS</b>"]
+        RE["Reverse Engineering<br/><b>STATUS</b>"]
+        RA["Requirements Analysis<br/><b>STATUS</b>"]
+        US["User Stories<br/><b>STATUS</b>"]
+        WP["Workflow Planning<br/><b>STATUS</b>"]
+        AD["Application Design<br/><b>STATUS</b>"]
+        UP["Units Planning<br/><b>STATUS</b>"]
+        UG["Units Generation<br/><b>STATUS</b>"]
+    end
+    
+    subgraph CONSTRUCTION["🟢 CONSTRUCTION PHASE"]
+        FD["Functional Design<br/><b>STATUS</b>"]
+        NFRA["NFR Requirements<br/><b>STATUS</b>"]
+        NFRD["NFR Design<br/><b>STATUS</b>"]
+        ID["Infrastructure Design<br/><b>STATUS</b>"]
+        CP["Code Planning<br/><b>EXECUTE</b>"]
+        CG["Code Generation<br/><b>EXECUTE</b>"]
+        BT["Build and Test<br/><b>EXECUTE</b>"]
+    end
+    
+    subgraph OPERATIONS["🟡 OPERATIONS PHASE"]
+        OPS["Operations<br/><b>PLACEHOLDER</b>"]
+    end
+    
+    Start --> WD
+    WD --> RA
+    RA --> WP
+    WP --> CP
+    CP --> CG
+    CG --> BT
+    BT --> End(["Complete"])
+    
+    %% Replace STATUS with COMPLETED, SKIP, EXECUTE as appropriate
+    %% Apply styling based on status
+```
+
+**Note**: Replace STATUS placeholders with actual phase status (COMPLETED/SKIP/EXECUTE) and apply appropriate styling
+
+## Phases to Execute
+
+### 🔵 INCEPTION PHASE
+- [x] Workspace Detection (COMPLETED)
+- [x] Reverse Engineering (COMPLETED/SKIPPED)
+- [x] Requirements Elaboration (COMPLETED)
+- [x] User Stories (COMPLETED/SKIPPED)
+- [x] Execution Plan (IN PROGRESS)
+- [ ] Application Design - [EXECUTE/SKIP]
+  - **Rationale**: [Why executing or skipping]
+- [ ] Units Planning - [EXECUTE/SKIP]
+  - **Rationale**: [Why executing or skipping]
+- [ ] Units Generation - [EXECUTE/SKIP]
+  - **Rationale**: [Why executing or skipping]
+
+### 🟢 CONSTRUCTION PHASE
+- [ ] Functional Design - [EXECUTE/SKIP]
+  - **Rationale**: [Why executing or skipping]
+- [ ] NFR Requirements - [EXECUTE/SKIP]
+  - **Rationale**: [Why executing or skipping]
+- [ ] NFR Design - [EXECUTE/SKIP]
+  - **Rationale**: [Why executing or skipping]
+- [ ] Infrastructure Design - [EXECUTE/SKIP]
+  - **Rationale**: [Why executing or skipping]
+- [ ] Code Planning - EXECUTE (ALWAYS)
+  - **Rationale**: Implementation approach needed
+- [ ] Code Generation - EXECUTE (ALWAYS)
+  - **Rationale**: Code implementation needed
+- [ ] Build and Test - EXECUTE (ALWAYS)
+  - **Rationale**: Build, test, and verification needed
+
+### 🟡 OPERATIONS PHASE
+- [ ] Operations - PLACEHOLDER
+  - **Rationale**: Future deployment and monitoring workflows
+
+## Package Change Sequence (Brownfield Only)
+[If applicable, list package update sequence with dependencies]
+
+## Estimated Timeline
+- **Total Phases**: [Number]
+- **Estimated Duration**: [Time estimate]
+
+## Success Criteria
+- **Primary Goal**: [Main objective]
+- **Key Deliverables**: [List]
+- **Quality Gates**: [List]
+
+[IF brownfield]
+- **Integration Testing**: All components working together
+- **Operational Readiness**: Monitoring, logging, alerting working
+```
+
+## Step 8: MANDATORY: Initialize State Tracking
+
+**MANDATORY**: Update BOTH state files in the SAME interaction:
+1. Update `aidlc-docs/{workflow-id}/aidlc-state.md`:
+
+```markdown
+# AI-DLC State Tracking
+
+## Project Information
+- **Project Type**: [Greenfield/Brownfield]
+- **Start Date**: [ISO timestamp]
+- **Current Stage**: INCEPTION - Workflow Planning
+
+## Execution Plan Summary
+- **Total Stages**: [Number]
+- **Stages to Execute**: [List]
+- **Stages to Skip**: [List with reasons]
+
+## Stage Progress
+
+### 🔵 INCEPTION PHASE
+- [x] Workspace Detection
+- [x] Reverse Engineering (if applicable)
+- [x] Requirements Analysis
+- [x] User Stories (if applicable)
+- [x] Workflow Planning
+- [ ] Application Design - [EXECUTE/SKIP]
+- [ ] Units Planning - [EXECUTE/SKIP]
+- [ ] Units Generation - [EXECUTE/SKIP]
+
+### 🟢 CONSTRUCTION PHASE
+- [ ] Functional Design - [EXECUTE/SKIP]
+- [ ] NFR Requirements - [EXECUTE/SKIP]
+- [ ] NFR Design - [EXECUTE/SKIP]
+- [ ] Infrastructure Design - [EXECUTE/SKIP]
+- [ ] Code Planning - EXECUTE
+- [ ] Code Generation - EXECUTE
+- [ ] Build and Test - EXECUTE
+
+### 🟡 OPERATIONS PHASE
+- [ ] Operations - PLACEHOLDER
+
+## Current Status
+- **Lifecycle Phase**: INCEPTION
+- **Current Stage**: Workflow Planning Complete
+- **Next Stage**: [Next stage to execute]
+- **Status**: Ready to proceed
+```
+
+2. Update `aidlc-docs/{workflow-id}/checkpoint.json` — initialize workflow state with all stage statuses, current_inception_stage set to next stage after Workflow Planning
+- **Do NOT proceed to the next stage without completing this step**
+
+## Step 9: Present Plan to User
+
+```markdown
+# 📋 Workflow Planning Complete
+
+I've created a comprehensive execution plan based on:
+- Your request: [Summary]
+- Existing system: [Summary if brownfield]
+- Requirements: [Summary if executed]
+- User stories: [Summary if executed]
+
+**Detailed Analysis**:
+- Risk level: [Level]
+- Impact: [Summary of key impacts]
+- Components affected: [List]
+
+**Recommended Execution Plan**:
+
+I recommend executing [X] stages:
+
+🔵 **INCEPTION PHASE:**
+1. [Stage name] - *Rationale:* [Why executing]
+2. [Stage name] - *Rationale:* [Why executing]
+...
+
+🟢 **CONSTRUCTION PHASE:**
+3. [Stage name] - *Rationale:* [Why executing]
+4. [Stage name] - *Rationale:* [Why executing]
+...
+
+I recommend skipping [Y] stages:
+
+🔵 **INCEPTION PHASE:**
+1. [Stage name] - *Rationale:* [Why skipping]
+2. [Stage name] - *Rationale:* [Why skipping]
+...
+
+🟢 **CONSTRUCTION PHASE:**
+3. [Stage name] - *Rationale:* [Why skipping]
+4. [Stage name] - *Rationale:* [Why skipping]
+...
+
+[IF brownfield with multiple packages]
+**Recommended Package Update Sequence**:
+1. [Package] - [Reason]
+2. [Package] - [Reason]
+...
+
+**Estimated Timeline**: [Duration]
+
+> **📋 <u>**REVIEW REQUIRED:**</u>**  
+> Please examine the execution plan at: `aidlc-docs/inception/plans/execution-plan.md`
+
+> **🚀 <u>**WHAT'S NEXT?**</u>**
+>
+> **You may:**
+>
+> 🔧 **Request Changes** - Ask for modifications to the execution plan if required
+> [IF any stages are skipped:]
+> 📝 **Add Skipped Stages** - Choose to include stages currently marked as SKIP
+> ✅ **Approve & Continue** - Approve plan and proceed to **[Next Stage Name]**
+```
+
+## Step 10: Handle User Response
+
+- **If approved**: Proceed to next stage in execution plan
+- **If changes requested**: Update execution plan and re-confirm
+- **If user wants to force include/exclude stages**: Update plan accordingly
+
+## Step 11: Log Interaction
+
+Log in `aidlc-docs/audit.md`:
+
+```markdown
+## Workflow Planning - Approval
+**Timestamp**: [ISO timestamp]
+**AI Prompt**: "Ready to proceed with this plan?"
+**User Response**: "[User's COMPLETE RAW response]"
+**Status**: [Approved/Changes Requested]
+**Context**: Workflow plan created with [X] stages to execute
+
+---
+```