recovery
Recover session state from memory-keeper after context loss.
When & Why to Use This Skill
The Recovery skill is a specialized utility designed to restore session states and progress from a persistent memory-keeper after context loss or session restarts. It enables Claude to retrieve recent checkpoints, summarize previous activities, and reconstruct the current task state—including modified files, implementation progress, and recommended next actions—ensuring seamless continuity in complex, long-term workflows.
Use Cases
- Resuming a complex development project after a session timeout or manual context clearing to maintain workflow continuity without repeating instructions.
- Reconstructing the current state of work, including modified files and pending tasks, when the AI's context window has been exhausted.
- Providing an immediate status update and 'next steps' recommendation when a user returns to a project and asks 'what was I working on?'.
- Recovering high-priority items and progress summaries from memory to bridge the gap between different chat sessions or after a system restart.
- Identifying blockers and implementation gaps by analyzing historical context items stored in the memory-keeper.
| name | recovery |
|---|---|
| description | Recover session state from memory-keeper after context loss. |
Recovery Skill
Restore session state from memory-keeper checkpoints after context is lost or when starting a new session.
When to Use
- Starting a new session on existing work
- After context was exhausted
- When asked "what was I working on?"
- When asked to "recover" or "restore" context
- After
/clearor session restart
Recovery Actions
1. Load Recent Context
context_get(limit: 50, sort: "created_desc")
2. Get Context Summary
context_summarize()
3. Find Progress Items
context_get(category: "progress", limit: 20)
4. Find High Priority Items
context_get(priority: "high", limit: 10)
5. Reconstruct State
From the retrieved context, extract:
current-task: What was being worked onfiles-modified: Files that were changedimplementation-progress: How far alongnext-action: What needs to happen nextblockers: Any known issues
Recovery Output Format
Present the recovered state clearly:
## Session Recovered
### Previous Task
<current-task value>
### Progress
<implementation-progress value>
### Files Modified
<list of files-modified>
### Blockers/Issues
<any blockers found>
### Recommended Next Action
<next-action value>
### Recent Checkpoints
1. <checkpoint 1 name>: <description>
2. <checkpoint 2 name>: <description>
---
Ready to continue. Confirm to proceed with: <next-action>
Recovery Checklist
- Load all recent context items
- Identify the current/last task
- Find all files that were modified
- Determine progress percentage/phase
- Locate the next action to take
- Check for any blockers
- Verify todo list state if available
- Present summary to user
- Get confirmation before proceeding
If No Context Found
If memory-keeper has no relevant context:
## No Previous Context Found
No checkpoints or progress items found in memory-keeper.
Possible reasons:
- This is a new session with no prior work
- Previous session did not checkpoint (work may be lost)
- Memory was cleared
To start fresh, describe what you'd like to work on.
Partial Recovery
If only some context is found:
## Partial Recovery
Found limited context from previous session:
### Available Information
<whatever was found>
### Missing Information
- [ ] Current task (not found)
- [ ] Files modified (not found)
- etc.
Would you like to:
1. Continue with available context
2. Start fresh
3. Provide additional context manually