Session Recovery

Detect and recover previous planning sessions, reconstructing lost context from persistent planning files.

509 stars

bya5c-ai

View on GitHub Installation ↓

Best use case

Session Recovery is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Detect and recover previous planning sessions, reconstructing lost context from persistent planning files.

Teams using Session Recovery should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/session-recovery/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/methodologies/planning-with-files/skills/session-recovery/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/session-recovery/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How Session Recovery Compares

Feature / Agent	Session Recovery	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Detect and recover previous planning sessions, reconstructing lost context from persistent planning files.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Session Recovery

Detect and recover previous planning sessions, reconstructing lost context from persistent planning files.

## Agent
Session Manager - `pwf-session-manager`

## Workflow
1. Check project path for existing planning files
2. Check ~/.claude/projects/ for session data
3. Find last planning file update timestamp
4. Extract post-update conversation context (lost context)
5. Build catchup report summarizing accomplished work
6. Merge recovered state into current session

## Inputs
- `projectPath` - Root path for planning files
- `sessionId` - Session identifier for recovery
- `previousSessionPath` - Path to previous session (optional)

## Outputs
- Recovery report with completed phases and lost context estimate
- Merged session state with preserved checkboxes
- Catchup summary for manual sync

## Process Files
- `planning-orchestrator.js` - Session recovery at startup
- `planning-session.js` - Full recovery pipeline

Related Skills

session-management

509

from a5c-ai/babysitter

Manage agent sessions including initialization, handoffs, revival (seance), and persistent identity for Polecats and Crew agents.

session-memory

509

from a5c-ai/babysitter

Mandatory memory persistence system across session resets using three markdown surfaces in .claude/cc10x/. Iron law - every workflow must load at start and update at end.

process-builder

509

from a5c-ai/babysitter

Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.

Workflow & Productivity

babysitter

509

from a5c-ai/babysitter

Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)