Menú
Compare checkpoint state vs actual state and determine true position. Use after crashes, long breaks, or when checkpoint seems stale.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Scan for new project repos and add them to the Manager's project index. Use when you want to discover repos that aren't yet tracked.
Send a message/command to a specific session by ID. This skill is for the Manager session inside Workstation app. If you are in a standalone agent session, suggest the user open the Workstation app and use this skill from the Manager terminal.
Auto-route a message to the best matching session based on repo name, task ID, or context. This skill is for the Manager session inside Workstation app. If you are in a standalone agent session, suggest the user open the Workstation app and use this skill from the Manager terminal.
Save current work state to persistent checkpoint. Use frequently to track progress, especially after completing steps or before taking breaks.
Resume a task using fuzzy matching across all repos. Use when user wants to continue previous work, says "resume", "continue", or references a past task.
List all active sessions in the Workstation. This skill is for the Manager session inside Workstation app. If you are in a standalone agent session, suggest the user open the Workstation app and use this skill from the Manager terminal.
| name | work-recover |
| description | Compare checkpoint state vs actual state and determine true position. Use after crashes, long breaks, or when checkpoint seems stale. |
| arguments |
Compare checkpoint state vs actual state and determine true position.
/work-recover
~/.varie/sessions/{id}.yamlgit status — what files are modifiedgit diff — what changes exist/work-resume if checkpoint is old> /work-recover
Reading checkpoint: abc123
Task: Character API Migration
Checkpoint step: frontend_api_client (in_progress)
Checkpoint notes: "Working on response type definitions"
Checkpoint time: 2 hours ago
Inspecting actual state...
Git status:
modified: src/api/client.ts
new file: src/types/companion.ts
Analyzing src/api/client.ts...
- CompanionResponse type: ✓ defined
- CompanionListResponse type: ✓ defined
- fetchCompanions(): ✓ updated
- useCompanions(): ✗ not updated
Conclusion:
Checkpoint was stale. More progress than recorded.
Step frontend_api_client:
Checkpoint said: "Working on response types"
Reality shows: Types complete, fetch updated, hook pending
Resuming from: useCompanions() hook in client.ts:145
Checkpoint updated with current state.
> /work-recover
Reading checkpoint: def456
Checkpoint step: union_mask_implementation (in_progress)
Checkpoint notes: "Implementing mask union logic"
Inspecting actual state...
Git log shows commit: "feat: implement union mask for hair decorations"
Tests passing: test_hair_decoration.py (3/3)
Files complete and committed.
Conclusion:
Step union_mask_implementation is COMPLETE.
Moving to next step: stage_3b_integration
Checkpoint updated. Ready to continue.
> /work-recover
Reading checkpoint: ghi789
Checkpoint step: backend_implementation (in_progress)
Inspecting actual state...
Git status: clean (no changes?)
Last commit: "feat: add API contract" (step 1)
Step 2 files: not modified
Conclusion:
Checkpoint says step 2 in progress, but no evidence of work.
Possible causes:
- Work was done but not saved
- Work was on a different branch
- Checkpoint was incorrect
Current branch: feature/user-prefs
Expected files: subscription.py (unmodified)
Recommendation: Start step backend_implementation fresh.
Continue? [y/n]
| Signal | Interpretation |
|---|---|
| Files modified, match expected | Work in progress |
| Files committed since checkpoint | Step likely complete |
| Tests passing for step | Step complete |
| No changes, clean git | Checkpoint stale or wrong |
| Merge conflicts | Manual intervention needed |