What problem does it solve? When a restore, cleanup, or rollback operation is interrupted, paused, or handed off, critical recovery state is often lost: what was attempted, what still exists, what is protected, and what to do next. This Skill keeps recovery state reconstructable so no one repeats destructive actions or loses track of unresolved cleanup. ## Core Features & Use Cases - Recovery Journaling: Records failed state, desired target, protected data, rollback identity, owned resources, attempted actions, and evidence in a minimum recovery journal. - Status Tracking: Uses explicit statuses (RECOVERY OPEN, PARTIAL / OWNERSHIP PRESERVED, AWAITING AUTHORITY, READY FOR HANDOFF, CLOSED / VERIFIED, STOP) so unresolved work is never rewritten as closed. - STOP Conditions: Halts when a journal would erase unresolved ownership, imply an unverified cleanup pass, fabricate chronology, or omit the last trustworthy rollback. - Use Case: A database migration fails halfway, leaving orphaned resources. Use this Skill to record which resources were created, which cleanup steps ran, what rollback remains available, and the exact next action, so a teammate can resume recovery days later without guessing. ## Quick Start Use the signalproof-recovery-continuity skill to write a recovery journal for the interrupted restore operation, capturing current state, remaining rollback options, and the exact next recovery action.
