gdd-pause

name	gdd-pause
description	Write a numbered checkpoint so work can resume in a new session without re-running completed stages.
argument-hint	[context note]
tools	Read, Write, Bash, AskUserQuestion, mcp__gdd_state__get, mcp__gdd_state__set_status, mcp__gdd_state__add_blocker, mcp__gdd_state__checkpoint
disable-model-invocation	true

@reference/retrieval-contract.md @reference/cycle-handoff-preamble.md

/gdd:pause

Captures enough state that a killed or stopped session can resume cleanly via /gdd:resume or /gdd:continue.

Each invocation writes an immutable numbered checkpoint - it does not overwrite previous pauses. This enables branched cycles: you can pause, take a detour via /gdd:sketch, compare, and resume an older snapshot via /gdd:resume N.

Steps

1. mcp__gdd_state__get → snapshot current pipeline state. Extract:

   • Current stage and cycle
   • last_checkpoint timestamp
   • task_progress and status for the current run
   • Open todos (from .design/TODO.md if present - this file is outside the MCP catalog, so Read is still used)
   • Active sketch/spike directories (scan .design/sketches/ and .design/spikes/ for in-progress markers)

2. Determine checkpoint number: run

   ls .design/checkpoints/ 2>/dev/null | grep -E '^[0-9]+' | sort -n | tail -1
   

   Next checkpoint = last number + 1 (or 01 if none exist).

3. Collect context: if no context argument was passed, ask (AskUserQuestion): "What are you in the middle of? (optional context to capture)"

4. Flip status via MCP so /gdd:resume can detect the pause and recover the prior status:

   1. mcp__gdd_state__set_status with status: "paused:<prior-status>" - the paused: prefix preserves the prior status for resume parsing.
   2. If the user supplied a context/blocker message: mcp__gdd_state__add_blocker with { stage: <current>, date: <today>, text: <message> }.
   3. mcp__gdd_state__checkpoint to stamp last_checkpoint via MCP.

5. Write numbered checkpoint: create .design/checkpoints/ with mkdir -p, then write:

   .design/checkpoints/NN-<stage>-<ISO-date>.md
   

   e.g. 01-design-2026-04-24.md

   Content:

   # Checkpoint NN
   **Saved**: <ISO timestamp>
   **Stage**: <stage>
   **Cycle**: <cycle>
   **In progress**: <task description + wave/index>
   **Next**: <next step>
   **Context**: <user note or "none">
   **Active sketch**: <path or none>
   **Open todos**: <N items (see .design/TODO.md)>
   **Completed this session**: <list>
   

6. Update HANDOFF.md pointer: write .design/HANDOFF.md with:

   # Session Handoff (pointer)
   Latest checkpoint: `.design/checkpoints/NN-<stage>-<ISO-date>.md`
   Run `/gdd:resume` to restore, or `/gdd:resume N` for a specific checkpoint.
   

7. Print: "Checkpoint NN saved. Run /gdd:resume or /gdd:continue to pick back up."

Do Not

• Do not mutate STATE.md directly - all STATE.md writes go through the gdd-state MCP tools above. Checkpoint files + HANDOFF.md are sibling artifacts, written with Write.
• Do not abort in-progress sketches; just record them.
• Do not delete previous checkpoint files.
• Do not call mcp__gdd_state__transition_stage - pause is status-only, never a stage transition.

PAUSE COMPLETE