plan-interruption

Detect plan interruptions, confirm user choice, and preserve plan state for resume.

7|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/robertphyatt/ironclaude --skill plan-interruption
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-interruption
Source: https://github.com/robertphyatt/ironclaude/tree/main/worker/skills/plan-interruption
Command: npx skills add https://github.com/robertphyatt/ironclaude --skill plan-interruption

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handle graceful interruption of plan execution and preserve current plan state.

Core Features & Use Cases

  • Announce interruption detection and clearly communicate the current plan and progress.
  • Guide the user through a confirmation flow with options to Stop, Continue, or Pause.
  • Preserve plan state when interrupted and set workflow to PLAN_INTERRUPTED, enabling safe resume later.
  • Provide a seamless transition between ARCHITECT and EXECUTION modes and support resume via dedicated commands.
  • Integrate with executing-plans to resume or re-acquire tasks when the user is ready.

Quick Start

Announce interruption detection and guide the user to choose a course of action to resume later.

Frequently Asked Questions about plan-interruption

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

FAQPage Schema
How do I pause a multi-session plan execution and preserve its state?

To pause plan execution, trigger the interruption detection flow to set the workflow state to PLAN_INTERRUPTED, which safely preserves current progress for later resumption.

What happens to my workflow state when a user interrupts a plan execution?

When user interaction interrupts plan execution, the workflow state transitions to PLAN_INTERRUPTED, ensuring current progress is safely saved before the session pauses or stops.

Can I resume a paused plan across different architect and execution modes?

Yes, you can resume a paused plan seamlessly across architect and execution modes by using the dedicated resume commands integrated with your executing-plans workflow.

How do I handle a topic change during an active workflow orchestration?

When a topic change occurs during workflow orchestration, the system detects the interruption and guides you through a confirmation flow to stop, continue, or pause the task.

What is the best way to transition between architect and execution modes without losing plan state?

The best way to transition modes without losing state is using the graceful interruption flow, which preserves your plan and enables seamless resume behavior via dedicated execution commands.