recovery

name	recovery
description	Workflow recovery protocol for resuming workflows after context loss, session interruption, or errors. Handles state reconstruction, artifact recovery, and seamless workflow continuation.
version	1.0.0
model	sonnet
invoked_by	both
user_invocable	true
tools	["Read","Write","Edit","Bash","Glob","Grep"]
error_handling	graceful
streaming	supported
verified	false
lastVerifiedAt	"2026-02-19T05:29:09.098Z"
source	builtin
trust_score	100
provenance_sha	94594ed6c501d7f8

Recovery Skill

Recovery Skill - Workflow recovery protocol for resuming workflows after context loss, session interruption, or errors. Handles state reconstruction, artifact recovery, and seamless workflow continuation. - Resuming workflows after context window exhaustion - Recovering from session interruptions - Reconstructing workflow state from artifacts and gate files - Identifying and continuing from last completed step - Preventing duplicate work during recovery

When to Use

• Context window exhausted mid-workflow
• Session interrupted or lost
• Need to resume from last completed step
• Workflow state needs reconstruction

Step 1: Identify Last Completed Step

1. Check gate files for last successful validation:

   • Location: .claude/context/history/gates/{workflow_id}/
   • Find highest step number with validation_status: "pass"
   • This is the last successfully completed step

2. Review reasoning files for progress:

   • Location: .claude/context/history/reasoning/{workflow_id}/
   • Read reasoning files up to last completed step
   • Extract context and decisions made

3. Identify artifacts created:

   • Check artifact registry: .claude/context/artifacts/registry-{workflow_id}.json
   • List all artifacts created up to last step
   • Verify artifact files exist

Step 2: Load Plan Documents

1. Read plan document (stateless):

   • Load plan-{workflow_id}.json from artifact registry
   • Extract current workflow state
   • Identify completed vs pending tasks

2. Load relevant phase plan (if multi-phase):

   • Check if project is multi-phase (exceeds phase_size_max_lines threshold)
   • Load active phase plan: plan-{workflow_id}-phase-{n}.json
   • Understand phase boundaries and dependencies

3. Understand current state:

   • Map completed tasks to plan
   • Identify next steps
   • Check for dependencies

Step 3: Context Recovery

1. Load artifacts from last completed step:

**Recovery after context loss**: