Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
inariku wants to merge 4 commits into
base: main
Choose a base branch
from
Open

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
bbeba80
fix: update execution-plan.md status on stage completion
Feb 7, 2026
3f85eb1
fix: clarify that execution-plan.md status updates apply to both Merm…
Feb 7, 2026
a0de927
fix: strengthen execution-plan.md update instructions
Feb 7, 2026
6f9c14a
fix: include text alternative in execution-plan.md update instructions
Feb 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions aidlc-rules/aws-aidlc-rule-details/construction/build-and-test.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

---
Expand Down
2 changes: 2 additions & 0 deletions aidlc-rules/aws-aidlc-rule-details/construction/code-generation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,7 @@ This stage generates code for each unit of work through two integrated parts:

## Step 9: Update Progress
- [ ] Mark Code Generation Part 1 (Planning) complete in `aidlc-state.md`
- [ ] Update Code Generation Part 1 (Planning) status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
- [ ] Update the "Current Status" section
Comment on lines +91 to 92
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This stage is “Code Generation” in execution-plan.md (the template shows a single node: “Code Generation (Planning + Generation)”), so asking to mark “Code Generation Part 1 (Planning)” as COMPLETED in execution-plan.md doesn’t match any stage/status in that file. Also, marking the stage COMPLETED at the end of planning would be premature (generation hasn’t happened yet). Suggest removing this execution-plan update from Part 1, or updating the execution-plan format to explicitly track Part 1 vs Part 2 if that’s the intent.

Suggested change
- [ ] Update Code Generation Part 1 (Planning) status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
- [ ] Update the "Current Status" section
- [ ] Keep `aidlc-docs/inception/plans/execution-plan.md` using a single "Code Generation (Planning + Generation)" stage; do not mark Code Generation as COMPLETED until Part 2 (Generation) is finished
- [ ] Update the "Current Status" section in `aidlc-state.md` to reflect that planning is complete and generation is ready to start

Copilot uses AI. Check for mistakes.
- [ ] Prepare for transition to Code Generation

Expand Down Expand Up @@ -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)
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Generation is defined as an ALWAYS, per-unit stage (common/process-overview.md). Updating the single “Code Generation” status in execution-plan.md to COMPLETED at the end of each unit risks marking the overall stage done while other units remain. Consider gating this update so it only flips to COMPLETED once the final unit’s code generation is approved, or revise execution-plan.md to track per-unit progress explicitly.

Suggested change
- Update Code Generation status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
- Only when **all units' Code Generation** is approved, update the global Code Generation status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist). Otherwise, leave the global status as IN PROGRESS and track per-unit completion in `aidlc-state.md`.

Copilot uses AI. Check for mistakes.

---

Expand Down
1 change: 1 addition & 0 deletions aidlc-rules/aws-aidlc-rule-details/construction/functional-design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Functional Design is a per-unit stage (common/process-overview.md). Updating the single “Functional Design” status in execution-plan.md to COMPLETED at the end of one unit would incorrectly mark the overall stage complete when multiple units exist. Consider updating execution-plan.md only after Functional Design is complete for all units (or introduce per-unit tracking in execution-plan.md).

Suggested change
- Update Functional Design status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
- For multi-unit projects, only update the overall Functional Design status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist) once Functional Design is complete for all units, or use per-unit Functional Design status tracking in `execution-plan.md` if available.

Copilot uses AI. Check for mistakes.
1 change: 1 addition & 0 deletions aidlc-rules/aws-aidlc-rule-details/construction/infrastructure-design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,3 +97,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)
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Infrastructure Design is a per-unit stage (common/process-overview.md). Updating the single “Infrastructure Design” status in execution-plan.md to COMPLETED at the end of one unit could incorrectly show the overall stage as done while other units remain. Consider only marking COMPLETED in execution-plan.md once all units have finished Infrastructure Design, or update the execution plan to track per-unit completion.

Suggested change
- Update Infrastructure Design status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
- Update Infrastructure Design status in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist) **only when Infrastructure Design is complete for all units**; otherwise, ensure any per-unit tracking in the execution plan is updated for the current unit

Copilot uses AI. Check for mistakes.
1 change: 1 addition & 0 deletions aidlc-rules/aws-aidlc-rule-details/construction/nfr-design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,3 +93,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)
Comment on lines 95 to +96
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NFR Design is a per-unit stage (common/process-overview.md). Updating the overall “NFR Design” status in execution-plan.md to COMPLETED after finishing one unit risks marking the stage complete while other units still need NFR Design. Consider deferring the execution-plan.md COMPLETED update until the last unit completes this stage, or add per-unit tracking to execution-plan.md.

Suggested change
- 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)
- Mark NFR Design stage complete for this unit in `aidlc-state.md`
- Ensure NFR Design completion is tracked per unit in accordance with `common/process-overview.md` (for example via a per-unit checklist or section)
- Only after NFR Design has been completed for all units, update the overall NFR Design status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)

Copilot uses AI. Check for mistakes.
1 change: 1 addition & 0 deletions aidlc-rules/aws-aidlc-rule-details/construction/nfr-requirements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NFR Requirements is a per-unit stage (common/process-overview.md). Updating the overall “NFR Requirements” status in execution-plan.md to COMPLETED at the end of a single unit would be inaccurate for multi-unit workflows. Consider updating execution-plan.md only once NFR Requirements is complete for all units, or extend execution-plan.md to represent per-unit progress.

Suggested change
- Update NFR Requirements status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
- Ensure `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist) accurately reflects NFR Requirements progress; only set the overall NFR Requirements status to COMPLETED once NFR Requirements is complete for all units in the workflow

Copilot uses AI. Check for mistakes.
1 change: 1 addition & 0 deletions aidlc-rules/aws-aidlc-rule-details/inception/application-design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,5 +143,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
3 changes: 2 additions & 1 deletion aidlc-rules/aws-aidlc-rule-details/inception/requirements-analysis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,4 +187,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
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This completion checklist still references “aidlc-state.md” without the canonical aidlc-docs/ prefix, even though earlier in this file Step 8 updates aidlc-docs/aidlc-state.md and the core workflow’s directory structure puts the file under aidlc-docs/. Consider updating this line to aidlc-docs/aidlc-state.md to avoid ambiguity about which file should be edited.

Suggested change
- Update Requirements Analysis stage complete in aidlc-state.md
- Update Requirements Analysis stage complete in `aidlc-docs/aidlc-state.md`

Copilot uses AI. Check for mistakes.
- Update Requirements Analysis status to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
2 changes: 2 additions & 0 deletions aidlc-rules/aws-aidlc-rule-details/inception/reverse-engineering.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 12: Present Completion Message to User
Comment on lines 288 to 292
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For consistency with the surrounding “Update State Tracking” step (which is a bulleted checklist), consider making this new execution-plan update instruction a bullet in the same list (rather than a standalone sentence between code fences/headings). That makes it less likely to be missed during stage completion.

Copilot uses AI. Check for mistakes.

```markdown
Expand Down
2 changes: 2 additions & 0 deletions aidlc-rules/aws-aidlc-rule-details/inception/units-generation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,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
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This step still says “Mark Units Planning complete in aidlc-state.md” (no aidlc-docs/ prefix), while the canonical path in the workflow is aidlc-docs/aidlc-state.md (core-workflow.md “Directory Structure”). Since this step is being touched, consider updating the state-file reference here to the canonical path to avoid creating/updating the wrong file.

Suggested change
- Mark Units Planning complete in aidlc-state.md
- Mark Units Planning complete in aidlc-docs/aidlc-state.md

Copilot uses AI. Check for mistakes.
- 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

Expand Down Expand Up @@ -156,6 +157,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

Expand Down
1 change: 1 addition & 0 deletions aidlc-rules/aws-aidlc-rule-details/inception/user-stories.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The workflow’s directory structure places the canonical state file at aidlc-docs/aidlc-state.md (core-workflow.md “Directory Structure”). This step still references aidlc-state.md without the aidlc-docs/ prefix, which can lead agents to write/update the wrong file. Consider updating this reference to aidlc-docs/aidlc-state.md for consistency with other stages.

Suggested change
- Mark User Stories stage complete in `aidlc-state.md`
- Mark User Stories stage complete in `aidlc-docs/aidlc-state.md`

Copilot uses AI. Check for mistakes.
- 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

Expand Down
6 changes: 4 additions & 2 deletions aidlc-rules/aws-aidlc-rule-details/inception/workflow-planning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -289,7 +289,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.

Comment on lines +292 to 293
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This note (and the new stage-completion instructions) refer to updating a “text alternative” in execution-plan.md, but the execution-plan template defined in Step 7 currently includes only the Mermaid flowchart and the checklist sections (no dedicated text-alternative section). To make this requirement actionable, consider adding an explicit text-alternative section to the template (and clarifying what it should contain) or removing/renaming the reference here to match the actual template structure.

Suggested change
**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.
**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, the Text Alternative section below, and the checklist.
## Text Alternative for Workflow Diagram
Provide a concise text description of the workflow for accessibility (for example, for screen readers). At minimum, list each phase and the status of its stages in reading order.
- **Inception Phase**:
- Workspace Detection – [STATUS]
- Reverse Engineering – [STATUS]
- Requirements Analysis – [STATUS]
- User Stories – [STATUS]
- Workflow Planning – [STATUS]
- Application Design – [STATUS]
- Units Planning – [STATUS]
- Units Generation – [STATUS]
- **Construction Phase**:
- Functional Design – [STATUS]
- NFR Requirements – [STATUS]
- NFR Design – [STATUS]
- Infrastructure Design – [STATUS]
- Code Generation – [STATUS]
- Build and Test – [STATUS]
- **Operations Phase**:
- Operations – [STATUS]

Copilot uses AI. Check for mistakes.
## Phases to Execute

Expand Down Expand Up @@ -453,7 +453,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)
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the execution-plan template’s checklist, the INCEPTION item is currently “Execution Plan (IN PROGRESS)” rather than “Workflow Planning (IN PROGRESS)”, so the instruction here to update Workflow Planning in the checklist is ambiguous/non-actionable. Either update the execution-plan checklist template to include a “Workflow Planning” entry (and align naming with the flowchart WP node), or adjust this instruction to match the checklist item name that actually exists.

Suggested change
1. Update Workflow Planning status from IN PROGRESS to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)
1. Update the INCEPTION checklist item "Execution Plan" status from IN PROGRESS to COMPLETED in `aidlc-docs/inception/plans/execution-plan.md` (Mermaid flowchart, text alternative, and checklist)

Copilot uses AI. Check for mistakes.
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

Expand Down
1 change: 1 addition & 0 deletions aidlc-rules/aws-aidlc-rules/core-workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -451,6 +451,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.
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new mandatory principle requires updating the execution plan to COMPLETED on “ANY stage completion”, but several CONSTRUCTION stages are explicitly per-unit (see common/process-overview.md). If agents follow this literally, they may mark a stage COMPLETED in execution-plan.md after finishing the first unit, even though other units remain. Consider tightening the wording to clarify that execution-plan.md should only be updated to COMPLETED when the stage is complete for the overall workflow (e.g., last unit completed), or update the execution-plan format to track per-unit progress.

Suggested change
- **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.
- **Execution Plan Tracking**: When a stage is FULLY COMPLETE for the overall workflow (e.g., all units finished for per-unit CONSTRUCTION stages), 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 overall stage completion; do NOT mark a stage COMPLETED in the execution plan based only on the first or partial unit being finished.

Copilot uses AI. Check for mistakes.
- **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
Expand Down
Loading