- Update frontmatter `lastStep` to reflect current navigation
- Execute the selected step file
- Let that step handle the detailed continuation logic
**State Preservation:**
- Maintain all existing content in the document
- Keep `stepsCompleted` accurate
- Track the resumption in workflow status
### 5. Special Continuation Cases
#### If `stepsCompleted` is empty but document has content:
- This suggests an interrupted workflow
- Ask user: "I see the document has content but no steps are marked as complete. Should I analyze what's here and set the appropriate step status?"
#### If document appears corrupted or incomplete:
- Ask user: "The document seems incomplete. Would you like me to try to recover what's here, or would you prefer to start fresh?"
#### If document is complete but workflow not marked as done:
- Ask user: "The architecture looks complete! Should I mark this workflow as finished, or is there more you'd like to work on?"
## SUCCESS METRICS:
✅ Existing document state properly analyzed and understood
✅ User presented with clear continuation options
✅ User choice handled appropriately and transparently
✅ Workflow state preserved and updated correctly
✅ Navigation to appropriate step handled smoothly
## FAILURE MODES:
❌ Not reading the complete existing document before making suggestions
❌ Losing track of what steps were actually completed
❌ Automatically proceeding without user confirmation of next steps
❌ Not checking for incomplete or placeholder content
❌ Losing existing document content during resumption
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
## NEXT STEP:
After user selects their continuation option, load the appropriate step file based on their choice. The step file will handle the detailed work from that point forward.
