dan:pause

Save and resume DAN workflow session state across phases, plans, tasks, stages, and waves.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/RavBogard/DAN --skill dan-pause
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dan:pause
Source: https://github.com/RavBogard/DAN/tree/main/.claude/skills/dan-pause
Command: npx skills add https://github.com/RavBogard/DAN --skill dan-pause

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save the current session state so work can be resumed later by capturing position and context, enabling seamless continuation.

Core Features & Use Cases

  • Save and store current session position (phase, plan, task, stage, wave) to STATE.md.
  • Update last session, stopped at, and commit a WIP snapshot for resume.
  • Operate in in-session mode without spawning new processes.

Quick Start

Prompt the DAN CLI to pause and save your current progress at the specified phase, plan, task, stage, and wave.

Frequently Asked Questions about dan:pause

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

FAQPage Schema
How do I pause and save my AI workflow session state?

To pause and save your AI workflow session state, prompt the DAN CLI to capture your current phase, plan, task, stage, and wave position. The state is recorded to STATE.md, and a WIP snapshot is committed for later resumption.

What is the best way to resume a long-running AI workflow after stopping?

Resuming a long-running AI workflow requires reading the saved session position from STATE.md. The DAN CLI captures the stopped phase, plan, task, stage, and wave, allowing you to seamlessly continue from the committed WIP snapshot.

Does the DAN CLI pause command require any specific file formats to work?

Yes, the DAN CLI pause command requires a valid SKILL.md frontmatter with name and description fields. It uses this to capture and commit the in-session state to STATE.md without spawning new processes.

Can I save session progress across multiple phases and waves without spawning new processes?

Yes, you can save session progress across phases, plans, tasks, stages, and waves in-session. The DAN CLI operates without spawning new processes, directly updating the last session and committing a WIP snapshot to STATE.md.

Why does my session state need to be committed as a WIP snapshot?

Committing a WIP snapshot records your stopped position and context accurately. This ensures the paused session state in STATE.md captures the exact phase, plan, task, stage, and wave, enabling seamless continuation later.