fix: add [next-stage-name] substitution guidance for construction app…

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

@@ -108,6 +108,16 @@ Design detailed business logic for the unit, technology-agnostic and focused pur
 ---
 ```
 
+**`[next-stage-name]` substitution**: Replace `[next-stage-name]` with the name of the next
+ENABLED stage for this unit, following the Construction phase order:
+1. **NFR Requirements** (if enabled for this unit)
+2. **NFR Design** (if NFR Requirements is skipped but NFR Design is enabled)
+3. **Infrastructure Design** (if both NFR stages are skipped)
+4. **Code Generation** (if all intermediate stages are skipped)
+
+Check `aidlc-docs/aidlc-state.md` or the execution plan to determine which stages are enabled.
+
+
 ### Step 8: Wait for Explicit Approval
 - Do not proceed until the user explicitly approves the functional design
 - Approval must be clear and unambiguous

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

@@ -84,6 +84,14 @@ Incorporate NFR requirements into unit design using patterns and logical compone
 ---
 ```
 
+**`[next-stage-name]` substitution**: Replace `[next-stage-name]` with the name of the next
+ENABLED stage for this unit, following the Construction phase order:
+1. **Infrastructure Design** (if enabled for this unit)
+2. **Code Generation** (if Infrastructure Design is skipped)
+
+Check `aidlc-docs/aidlc-state.md` or the execution plan to determine which stages are enabled.
+
+
 ### Step 8: Wait for Explicit Approval
 - Do not proceed until the user explicitly approves the NFR design
 - Approval must be clear and unambiguous

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

@@ -88,6 +88,15 @@ Determine non-functional requirements for the unit and make tech stack choices.
 ---
 ```
 
+**`[next-stage-name]` substitution**: Replace `[next-stage-name]` with the name of the next
+ENABLED stage for this unit, following the Construction phase order:
+1. **NFR Design** (if enabled for this unit)
+2. **Infrastructure Design** (if NFR Design is skipped)
+3. **Code Generation** (if both NFR Design and Infrastructure Design are skipped)
+
+Check `aidlc-docs/aidlc-state.md` or the execution plan to determine which stages are enabled.
+
+
 ### Step 8: Wait for Explicit Approval
 - Do not proceed until the user explicitly approves the NFR requirements
 - Approval must be clear and unambiguous