resume

Resume interrupted OpenSpec AutoDev workflows with multi-session state recovery.

1|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/wonder-zhang/openspec-autodev --skill resume-wonder-zhang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resume
Source: https://github.com/wonder-zhang/openspec-autodev/tree/main/skills/resume
Command: npx skills add https://github.com/wonder-zhang/openspec-autodev --skill resume-wonder-zhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resume interrupted AutoDev workflows across multiple sessions and preserve progress, enabling migrations from legacy plans.

Core Features & Use Cases

  • Session-aware recovery for auto-dev, iterate, and bugfix workflows.
  • Safe re-execution: idempotent steps and clear state management.
  • Legacy migration: migrate old workflow states into session-based tracking.

Quick Start

Invoke the resume action to continue an interrupted multi-session AutoDev workflow.

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 AutoDev workflow across multiple sessions?▼

To resume an interrupted AutoDev workflow across multiple sessions, invoke the resume action to restore session-aware recovery. It preserves progress and safely re-executes interrupted phases using idempotent steps and clear state management.

What is the best way to handle legacy migration for OpenSpec workflow states?▼

Legacy migration for OpenSpec workflow states involves migrating old workflow plans into session-based tracking. The resume action handles this migration automatically, ensuring historical states are preserved and integrated into the current multi-session workflow.

Can I safely re-execute interrupted auto-dev, iterate, or bugfix phases?▼

Yes, you can safely re-execute interrupted auto-dev, iterate, and bugfix phases. The recovery process uses idempotent steps and clear session state management to ensure safe re-runs without duplicating completed work or corrupting the workflow.

Does session recovery work for all types of AutoDev workflows?▼

Session recovery applies specifically to auto-dev, iterate, and bugfix workflows. It handles session recovery, legacy migration, and safe re-execution of interrupted phases for these supported OpenSpec AutoDev scenarios.

Why does my multi-session AutoDev run need idempotent re-runs?▼

Multi-session AutoDev runs need idempotent re-runs to satisfy robust recovery and prevent duplicate side effects. When an interrupted phase is safely re-executed, idempotency ensures the workflow resumes accurately without repeating completed operations.

When should I not use the resume action for workflow recovery?▼

You should not use the resume action for workflows outside the auto-dev, iterate, and bugfix scenarios. It is specifically designed for OpenSpec AutoDev session recovery and legacy migration, and may not apply to other software engineering workflow types.