One-click install
npx skills add https://github.com/zabuuq/sdd-plugin --skill pause-zabuuq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pause
Source: https://github.com/zabuuq/sdd-plugin/tree/main/plugins/sdd/skills/pause
Command: npx skills add https://github.com/zabuuq/sdd-plugin --skill pause-zabuuq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of losing context during an ongoing SDD interview flow by turning the current in-flight state into a resume file a fresh model can pick up.

Core Features & Use Cases

  • Distills the active conversation state into docs/<command>-resume.md so the next session continues the same decision point.
  • Prevents unintended state clobbering by preserving lastCommand so /sdd:unpause can dispatch the correct command.
  • Supports multi-session continuity for pauseable phases like discovery, scope, PRD, spec, planning, refinement, and polish.

Quick Start

Ask your agent to run /sdd:pause when you need to stop mid-flow and resume later with /sdd:unpause.

Frequently Asked Questions about pause

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

FAQPage Schema
How do I save Claude Code workflow state to resume a session later?

You resume a paused SDD phase by running the unpause command, which dispatches the correct command using the preserved lastCommand state. This loads the saved markdown file to continue the interview flow exactly where it left off.

How does context snapshotting work for multi-session SDD workflows?

Pauseable SDD phases include discovery, scope, prd, spec, plan, refine, and polish. You can snapshot and resume the decision state during any of these interview-driven phases to maintain workflow continuity across multiple sessions.

What is the best way to prevent state clobbering when pausing an SDD interview?

The best way to prevent state clobbering is to preserve the lastCommand value when snapshotting the current state. This ensures the resume mechanism dispatches the correct command and overwrites only the existing resume file without corrupting project state.

Does the pause workflow require a specific project state file format?

Yes, the pause workflow requires a docs/project-state.json file indicating a pauseable SDD phase. It also needs a shared guide and pause-resume reference loaded before it can write the docs/<command>-resume.md file correctly.

Why does my context snapshot only output a single paused message?

The context snapshot outputs only 'Paused. Run /sdd:unpause to resume.' as a final confirmation after successfully writing the resume file. This strict output constraint prevents context pollution while confirming the state snapshot saved correctly.