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

[inariku]

Problem

When stages complete, aidlc-state.md is updated correctly, but execution-plan.md is never updated. This leaves the execution plan with stale status values (e.g., IN PROGRESS or EXECUTE) even after stages have finished.

Solution

1. Added an instruction to update the corresponding stage status to COMPLETED in aidlc-docs/inception/plans/execution-plan.md at every stage completion point across all rule-details files
2. Explicitly specified (Mermaid flowchart, text alternative, and checklist) to ensure all three representations are updated
3. Added a MANDATORY execution plan tracking principle in core-workflow.md to ensure AI agents prioritize this update

Changes

core-workflow.md (1 file):

• Added Execution Plan Tracking as a MANDATORY Key Principle

Inception phase (7 files):

• workflow-planning.md — update on user approval (numbered sub-list for visibility) + note in execution-plan template
• reverse-engineering.md — Step 10: Update State Tracking
• requirements-analysis.md — approval handling
• user-stories.md — Step 23: Update Progress
• application-design.md — Step 15: Update Progress
• units-generation.md — Step 11 (Units Planning) and Step 19 (Units Generation)

Construction phase (6 files):

• functional-design.md — approval handling
• nfr-requirements.md — approval handling
• nfr-design.md — approval handling
• infrastructure-design.md — approval handling
• code-generation.md — Code Planning (Step 9) and Code Generation completion
• build-and-test.md — Step 8: Update State Tracking

Test Evidence

Tested by running a full AI-DLC workflow (simple TODO CLI app in Python) with the modified rules in Kiro CLI.

Test Setup

• Clean project directory with modified rules copied to .kiro/steering/ and .kiro/aws-aidlc-rule-details/
• Ran: Using AI-DLC, create a simple TODO list CLI app in Python

Results — execution-plan.md status updates

Stage	Mermaid Flowchart	Checklist
Workflow Planning (approve)	✅ IN PROGRESS → COMPLETED	✅ Updated
Code Generation (completion)	✅ EXECUTE → COMPLETED	✅ EXECUTE → COMPLETED

Before (Workflow Planning created, before approve)

L26: WP["Workflow Planning<br/><b>IN PROGRESS</b>"]
L71: - [x] Workflow Planning (IN PROGRESS)
L30: CG["Code Generation<br/><b>EXECUTE</b>"]
L89: - [ ] Code Generation - EXECUTE (ALWAYS)

After (Code Generation completed)

L26: WP["Workflow Planning<br/><b>COMPLETED</b>"]
L71: - [x] Workflow Planning (COMPLETED)
L30: CG["Code Generation<br/><b>COMPLETED</b>"]
L89: - [x] Code Generation - COMPLETED

Key Findings

• The MANDATORY principle in core-workflow.md was essential for making the AI consistently perform the updates. Without it (tested in earlier iterations), the AI skipped the execution-plan.md updates despite instructions in individual stage files.
• Initial testing only specified "Mermaid flowchart and checklist", which left the text alternative section stale. Updated all instructions to include text alternative as well.

Closes #23

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[inariku]

Hey @raj-jain-aws 👋 Same ask as #68 — would appreciate a merge commit instead of squash so the contribution shows up. Thanks!

[scottschreckengaust]

Hi @inariku. You are already a contributor. We squash commits that show contribution, this PR shows your participation (no commits).