fix: update execution-plan.md status on stage completion

aidlc-rules/aws-aidlc-rule-details/construction/build-and-test.md

@@ -300,6 +300,7 @@ Create `aidlc-docs/construction/build-and-test/build-and-test-summary.md`:
 
 Update `aidlc-docs/aidlc-state.md`:
 - Mark Build and Test stage as complete
+- Update Build and Test status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
 - Update current status
 
 ---

aidlc-rules/aws-aidlc-rule-details/construction/code-generation.md

@@ -88,6 +88,7 @@ This stage generates code for each unit of work through two integrated parts:
 
 ## Step 9: Update Progress
 - [ ] Mark Code Planning complete in `aidlc-state.md`
+- [ ] Update Code Planning status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
 - [ ] Update the "Current Status" section
 - [ ] Prepare for transition to Code Generation
 
@@ -166,6 +167,7 @@ This stage generates code for each unit of work through two integrated parts:
 - Log approval in audit.md with timestamp
 - Record the user's approval response with timestamp
 - Mark Code Generation stage as complete for this unit in aidlc-state.md
+- Update Code Generation status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
 
 ---
 

aidlc-rules/aws-aidlc-rule-details/construction/functional-design.md

@@ -117,3 +117,4 @@ Design detailed business logic for the unit, technology-agnostic and focused pur
 - Log approval in audit.md with timestamp
 - Record the user's approval response with timestamp
 - Mark Functional Design stage complete in aidlc-state.md
+- Update Functional Design status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)

aidlc-rules/aws-aidlc-rule-details/construction/infrastructure-design.md

@@ -92,3 +92,4 @@ Map logical software components to actual infrastructure choices for deployment
 - Log approval in audit.md with timestamp
 - Record the user's approval response with timestamp
 - Mark Infrastructure Design stage complete in aidlc-state.md
+- Update Infrastructure Design status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)

aidlc-rules/aws-aidlc-rule-details/construction/nfr-design.md

@@ -88,3 +88,4 @@ Incorporate NFR requirements into unit design using patterns and logical compone
 - Log approval in audit.md with timestamp
 - Record the user's approval response with timestamp
 - Mark NFR Design stage complete in aidlc-state.md
+- Update NFR Design status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)

aidlc-rules/aws-aidlc-rule-details/construction/nfr-requirements.md

@@ -97,3 +97,4 @@ Determine non-functional requirements for the unit and make tech stack choices.
 - Log approval in audit.md with timestamp
 - Record the user's approval response with timestamp
 - Mark NFR Requirements stage complete in aidlc-state.md
+- Update NFR Requirements status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)

aidlc-rules/aws-aidlc-rule-details/inception/application-design.md

@@ -141,5 +141,6 @@ If the analysis in step 8 reveals ANY ambiguous answers, you MUST:
 
 ### 15. Update Progress
 - Mark Application Design stage complete in `aidlc-docs/aidlc-state.md`
+- Update Application Design status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
 - Update the "Current Status" section
 - Prepare for transition to next stage

aidlc-rules/aws-aidlc-rule-details/inception/requirements-analysis.md

@@ -171,4 +171,5 @@ Update `aidlc-docs/aidlc-state.md`:
 
    - Wait for explicit user approval before proceeding
    - Record approval response with timestamp
-   - Update Requirements Analysis stage complete in aidlc-state.md
+   - Update Requirements Analysis stage complete in aidlc-state.md
+   - Update Requirements Analysis status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)

aidlc-rules/aws-aidlc-rule-details/inception/reverse-engineering.md

@@ -287,6 +287,8 @@ Update `aidlc-docs/aidlc-state.md`:
 - **Artifacts Location**: aidlc-docs/inception/reverse-engineering/
 ```
 
+Update Reverse Engineering status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist).
+
 ## Step 11: Present Completion Message to User
 
 ```markdown

aidlc-rules/aws-aidlc-rule-details/inception/units-generation.md

@@ -93,6 +93,7 @@ If the analysis in step 7 reveals ANY ambiguous answers, you MUST:
 
 ## Step 11: Update Progress
 - Mark Units Planning complete in aidlc-state.md
+- Update Units Planning status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
 - Update the "Current Status" section
 - Prepare for transition to Units Generation
 
@@ -151,6 +152,7 @@ If the analysis in step 7 reveals ANY ambiguous answers, you MUST:
 
 ## Step 19: Update Progress
 - Mark Units Generation stage complete in `aidlc-docs/aidlc-state.md`
+- Update Units Generation status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
 - Update the "Current Status" section
 - Prepare for transition to CONSTRUCTION PHASE
 

aidlc-rules/aws-aidlc-rule-details/inception/user-stories.md

@@ -298,6 +298,7 @@ If the analysis in step 9 reveals ANY ambiguous answers, you MUST:
 
 ## Step 23: Update Progress
 - Mark User Stories stage complete in `aidlc-state.md`
+- Update User Stories status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
 - Update the "Current Status" section
 - Prepare for transition to next stage
 

aidlc-rules/aws-aidlc-rule-details/inception/workflow-planning.md

@@ -292,7 +292,7 @@ flowchart TD
     %% Apply styling based on status
 ```
 
-**Note**: Replace STATUS placeholders with actual phase status (COMPLETED/SKIP/EXECUTE) and apply appropriate styling
+**Note**: Replace STATUS placeholders with actual phase status (COMPLETED/SKIP/EXECUTE) and apply appropriate styling. When updating a stage status to COMPLETED, update it in the Mermaid flowchart, text alternative, and checklist.
 
 ## Phases to Execute
 
@@ -459,7 +459,9 @@ I recommend skipping [Y] stages:
 
 ## Step 10: Handle User Response
 
-- **If approved**: Proceed to next stage in execution plan
+- **If approved**:
+  1. Update Workflow Planning status from IN PROGRESS to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
+  2. 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
 

aidlc-rules/aws-aidlc-rules/core-workflow.md

@@ -423,6 +423,7 @@ The Operations stage will eventually include:
 - **Transparent Planning**: Always show execution plan before starting
 - **User Control**: User can request stage inclusion/exclusion
 - **Progress Tracking**: Update aidlc-state.md with executed and skipped stages
+- **Execution Plan Tracking**: When completing ANY stage, update that stage's status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist). This is MANDATORY for every stage completion.
 - **Complete Audit Trail**: Log ALL user inputs and AI responses in audit.md with timestamps
   - **CRITICAL**: Capture user's COMPLETE RAW INPUT exactly as provided
   - **CRITICAL**: Never summarize or paraphrase user input in audit log