Your next step would be: **Step {nextStep} - [step name]**
What would you like to do?
1.**Continue** from where you left off
2.**Review** what's been done so far
3.**Modify** previous work
4.**Start over** with a new plan"
### 5. Handle User Choice
User your best judgement in how to handle the users choice
### 6. Update Continuation Status
Update modulePlanFile frontmatter:
- Set lastStep: 'continued'
- Add note about continuation date
- Keep stepsCompleted unchanged
## ✅ SUCCESS METRICS:
- User understands current progress
- Next step identified correctly
- User choice handled appropriately
- Module plan updated with continuation status
- Workflow resumed at correct location
## ❌ FAILURE MODES TO AVOID:
- Not accurately reading previous status
- Skipping steps just because they exist
- Not offering review option
- Losing previous work
- Not updating continuation tracking
---
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
### ✅ SUCCESS:
- Existing work properly loaded and analyzed
- User clearly understands current status
- Continuation options presented clearly
- Next step determined correctly
- Module plan updated with continuation information
### ❌ SYSTEM FAILURE:
- Not reading existing plan completely
- Misrepresenting progress status
- Losing track of what's been done
- Not offering appropriate continuation options
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN user selects 'C' (Continue) and appropriate updates are saved to modulePlanFile, will you then load, read entire file, then execute the determined next step file to resume the module creation workflow.