recover

Resume interrupted AI workflows from saved file-based task states.

24|5|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/myrtlepn/gran-maestro --skill recover-myrtlepn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recover
Source: https://github.com/myrtlepn/gran-maestro/tree/main/skills/recover
Command: npx skills add https://github.com/myrtlepn/gran-maestro --skill recover-myrtlepn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows users to seamlessly resume interrupted AI workflows from their last saved state, preventing data loss and eliminating the need to restart complex tasks from scratch.

Core Features & Use Cases

  • Automated Recovery: Automatically detects and recovers incomplete requests and tasks.
  • Stateful Resumption: Resumes workflows from the exact phase and task where they left off, whether it was executing, reviewing, or facing merge conflicts.
  • Use Case: If your AI coding session was interrupted, use this Skill to pick up exactly where you left off, whether it was in the middle of writing code, reviewing a pull request, or resolving merge conflicts.

Quick Start

Use the recover skill to resume any interrupted requests.

Frequently Asked Questions about recover

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume an interrupted AI workflow from where it left off?

To resume an interrupted workflow, the system analyzes file-based states and task statuses to restore execution from the exact phase it stopped, preventing data loss without restarting from scratch.

Can I recover an AI coding session that was stopped during merge conflict resolution?

Yes, you can recover sessions stopped during merge conflict resolution by analyzing saved state statuses and handling user interaction to resume conflict resolution and recovery choices directly.

Does the workflow recovery process support tasks that were in a pending or review state?

Workflow recovery supports restoring tasks across various saved states including pending, executing, review, feedback, merging, and merge conflicts to seamlessly continue the interrupted request.

How does state management handle task re-execution for interrupted requests?

State management handles task re-execution by integrating with external execution skills like mst:codex and mst:gemini to re-run tasks based on their analyzed file-based statuses.

What's the best way to prevent data loss when an AI coding session is unexpectedly interrupted?

The best way to prevent data loss is utilizing automated recovery to detect incomplete requests and resume workflows from the exact task phase where the interruption occurred.

Are there limitations on which workflow phases can be restored after an interruption?

There are no stated limitations on restorable phases; recovery explicitly supports pending, executing, review, feedback, merging, and merge conflict states across multiple requests and tasks.