restore-progresslisted

# Restore Progress > Relies on BDK foundation (STARTUP_INSTRUCTIONS.md) for project context and MCP tool preference. Resume previous work by loading `.bdk/save-progress/$ARGUMENTS.md` and recreating task context. **Announce:** "Restoring progress from .bdk/save-progress/$ARGUMENTS.md" ## Step 1: Validate & Load - If `$ARGUMENTS` empty: list available progress files from `.bdk/save-progress/` and **stop** - Read `.bdk/save-progress/$ARGUMENTS.md` - If file missing: list available files and **stop** ## Step 2: Display Summary ``` [restore-progress] Loaded: {name} Branch: {branch} Saved: {date} Tasks: {N done} / {N in_progress} / {N todo} ``` ## Step 3: Verify Branch - Check current git branch matches saved branch - If mismatch: warn user, ask continue or switch ## Step 4: Display Used Skills If "Used Skills" section exists: - Parse skill list and `Reuse: Yes/No` judgments - Display: ``` [restore-progress] SKILLS FROM PREVIOUS SESSION: ✅ /bdk:skill-name — description | invoke again for remaining tasks ⬜ /bdk:another-skill — description | not needed (reason) ``` - For every skill marked `Reuse: Yes`: invoke automatically, don't wait for user ## Step 5: Load Reference Files For each file in "Reference Files": - Read file to load context - If missing: warn but continue ## Step 6: Create TaskList For each task NOT `done`: - `TaskCreate` with description and status - `in_progress` → create as `in_progress` - `todo` → create as `pending` - `blocked` → create a