/rapid:resume -- Resume a Paused Set

/rapid:resume -- Resume a Paused Set

You are the RAPID resume handler. This skill resumes a previously paused set by loading its HANDOFF.md and STATE.json context, allowing execution to continue from where it left off. Follow these steps IN ORDER. Do not skip steps.

Step 1: Load Environment

if [ -z "${RAPID_TOOLS:-}" ] && [ -n "${CLAUDE_SKILL_DIR:-}" ] && [ -f "${CLAUDE_SKILL_DIR}/../../.env" ]; then export $(grep -v '^#' "${CLAUDE_SKILL_DIR}/../../.env" | xargs); fi
if [ -z "${RAPID_TOOLS}" ]; then echo "[RAPID ERROR] RAPID_TOOLS is not set. Run /rapid:install or ./setup.sh to configure RAPID."; exit 1; fi
echo "Environment loaded. RAPID_TOOLS=${RAPID_TOOLS}"

Step 2: Determine Set to Resume

If the user provided a set name as argument (/rapid:resume {setName} or /rapid:resume 1):

Resolve Set Reference

Resolve the set argument through the numeric ID resolver:

# (env preamble here)
RESOLVE_RESULT=$(node "${RAPID_TOOLS}" resolve set "<user-input>" 2>&1)
RESOLVE_EXIT=$?
if [ $RESOLVE_EXIT -ne 0 ]; then
  echo "$RESOLVE_RESULT"
  # Display the error message from the JSON and STOP
fi
SET_NAME=$(echo "$RESOLVE_RESULT" | node -e "d=JSON.parse(require('fs').readFileSync(0,'utf-8')); console.log(d.resolvedId)")

Use SET_NAME for all subsequent operations. Skip to Step 3.

If no set name was provided, list paused sets:

node "${RAPID_TOOLS}" worktree list 2>/dev/null

Parse the JSON output and filter for entries with phase: "Paused".

If multiple paused sets: Use AskUserQuestion with:

• question: "Which set would you like to resume?"
• options: One option per paused set, where name is the set id and description shows pause cycle count and last update time.

If exactly one paused set: Use that set automatically and inform the user: "Found one paused set: {setName}"

If no paused sets: Print: "No paused sets found. Use /pause to pause an executing set first." and end.

Step 3: Load Resume Data (Info Only)

Call the resume CLI with --info-only to load handoff data and STATE.json context without transitioning the set's phase:

node "${RAPID_TOOLS}" resume --info-only {setName}

Parse the JSON output which contains:

• resumed: boolean (will be false since --info-only does not transition state)
• setName: the set name
• handoff: parsed HANDOFF.md data (frontmatter + sections)
• stateContext: wave/job progress from STATE.json (may be null)
• definitionPath: path to DEFINITION.md
• contractPath: path to CONTRACT.json
• pauseCycles: number of times this set has been paused

If the command fails (set not in Paused phase or HANDOFF.md missing): Display the error and end.

Step 4: Display Handoff Summary

Present the handoff data in a clear format:

Resuming Set: {setName}

Pause Cycle: {pauseCycles} Last Action: {handoff.frontmatter.handoff_done or 'Not recorded'} Remaining Work: {handoff.frontmatter.handoff_remaining or 'Not recorded'} Pause Notes: {handoff.frontmatter.handoff_resume or 'No notes'}

Wave/Job Progress: {Format stateContext.waves showing completion status per wave, or 'No state context available'}

Step 5: Confirm Resume

Use AskUserQuestion with:

• question: "Resume set '{setName}'?"
• options:
  • "Resume" -- "Restore context and transition set back to Executing phase"
  • "View HANDOFF.md" -- "Read the full handoff file before deciding"
  • "Cancel" -- "Keep set paused, exit resume flow"

If "View HANDOFF.md": Read and display the file:

cat .planning/sets/{setName}/HANDOFF.md

Then ask again with AskUserQuestion:

• question: "Proceed with resume?"
• options:
  • "Resume" -- "Restore context and continue execution"
  • "Cancel" -- "Keep set paused"

If "Cancel": Print "Resume cancelled. Set remains paused." and end.

Step 6: Transition State

Now that the user has confirmed, call the resume CLI without --info-only to transition the set from Paused to Executing:

node "${RAPID_TOOLS}" resume {setName}

If the command fails: Display the error and end.

Step 7: Resume Confirmed

The resume CLI (Step 6) has transitioned the set from Paused to Executing in REGISTRY.json.

Display the resume confirmation:

Set '{setName}' resumed.

• Worktree: {worktree path from registry}
• Branch: rapid/{setName}
• Phase: Executing

The set is ready for continued execution. Run /execute {setName} to proceed from where the previous session left off.

The executor will receive the HANDOFF.md context automatically and continue from the first incomplete task.

Important Notes

• Resume transitions set to Executing: The resume CLI command (without --info-only) updates REGISTRY.json phase from Paused to Executing. The --info-only flag loads handoff data without transitioning state, used in Step 3 before user confirmation.
• HANDOFF.md is preserved: The handoff file remains after resume for reference. It is cleaned up when the set reaches Done.
• STATE.json context: If STATE.json exists and contains the set, the resume response includes wave/job progress to help the executor pick up where it left off.
• Multiple pause cycles: If the set has been paused 3+ times, the pause skill will have warned about replanning. The resume skill does not block on this -- it is advisory.