resume

Resume interrupted plans by detecting completed phases and continuing from the last checkpoint.

4|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/skaisser/blueprint --skill resume-skaisser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resume
Source: https://github.com/skaisser/blueprint/tree/main/skills/resume
Command: npx skills add https://github.com/skaisser/blueprint --skill resume-skaisser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resume a plan after context limit, crash, or session break. Detects completed phases, summarizes progress, and continues execution from where it stopped.

Core Features & Use Cases

  • Detects progress from [x] marks, skipping already finished work.
  • Generates a concise status report and re-enters execution from the last checkpoint.
  • Triggers on common resume phrases like "/resume", "continue the plan", or "plan status".

Quick Start

Say "/resume" to continue your interrupted blueprint plan from the last completed phase.

Frequently Asked Questions about resume

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

FAQPage Schema
How do I resume an interrupted plan after a context limit or session crash?

To resume an interrupted plan, the system detects completed phases marked with [x], summarizes progress, and continues execution from the last known checkpoint. This handles context limits, crashes, and session breaks automatically.

What is the best way to check plan execution status after an interruption?

Checking plan execution status involves reading the stored plan state to identify completed and remaining phases, generating a concise status report, and preparing to re-enter execution from the stopping point.

How does detecting completed phases work when continuing a blueprint plan?

Detecting completed phases works by scanning for [x] marks in the stored plan state, skipping already finished work, and performing integrity checks for missing outputs before constructing lean context for subsequent rounds.

Does this execution resume tool require a specific command to continue?

This execution resume tool triggers on common phrases like "/resume", "continue the plan", or "plan status" to detect progress, summarize previous work, and re-enter execution from the last checkpoint.

Can I use this to recover execution from a session break without losing context?

Yes, you can recover execution from a session break without losing context by reading stored plan state, identifying remaining phases, and constructing a lean context for subsequent rounds to continue the blueprint.