unpause

Resume a paused SDD interview from docs/project-state.json.

Updated Apr 9, 2026

Search Tags:#workflow #state management #resume #SDD #markdown artifacts #interview-driven planning #guard rails

Ready to run

npx skills add https://github.com/zabuuq/sdd-plugin --skill unpause

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unpause
Source: https://github.com/zabuuq/sdd-plugin/tree/main/plugins/sdd/skills/unpause
Command: npx skills add https://github.com/zabuuq/sdd-plugin --skill unpause

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It lets you continue a previously paused SDD interview without restarting the entire planning or spec workflow.

Core Features & Use Cases

Resume-and-delegate: Reads the paused command name from docs/project-state.json and delegates back to that command instead of acting as a separate chain.
Resume-file validation: Ensures the expected docs/<command>-resume.md file exists before loading any command logic or continuing the interview.
State-safe behavior: Avoids clobbering lastCommand and does not run the open-concerns protocol—your original command resumes with its own startup rules.

Quick Start

Run /sdd:unpause with no arguments to pick up exactly where you left off in your last paused SDD command.

Frequently Asked Questions about unpause

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

FAQPage Schema

How do I resume a paused SDD interview without restarting the workflow?▼

To resume a paused SDD interview, run the unpause command with no arguments. It reads the last command from docs/project-state.json and delegates control back to it, picking up exactly where you left off.

What is needed to restore a paused state management workflow?▼

Restoring a paused state management workflow requires the docs/project-state.json file and the expected docs/<command>-resume.md file to exist. The system validates the resume file before loading any command logic.

How does state-safe behavior work when resuming an interview-driven planning session?▼

State-safe behavior prevents clobbering the lastCommand value and skips the open-concerns protocol. Your original command resumes with its own startup rules, ensuring pending decisions remain intact.

Can I run the resume command with arguments to continue a specific markdown artifact workflow?▼

No, the resume command applies to zero-argument continuation scenarios only. It reads the paused command name from project-state.json and automatically delegates back to that specific command.

Why does my resume file validation fail when I try to unpause an SDD workflow?▼

Resume file validation fails when the expected docs/<command>-resume.md file does not exist. The system requires this file to be present before loading plugins/sdd/skills/<command>/SKILL.md to restore pending decisions.