Resume Sprint

Resume execution of a paused sprint.

Preflight Checks

Find the most recent sprint directory:

ls -dt .claude/sprints/*/ 2>/dev/null | head -1

Context

From the preflight output, identify the sprint directory path (e.g., .claude/sprints/YYYY-MM-DD_name/).

Then use the Read tool to read:

• <sprint-dir>/PROGRESS.yaml - to check current status

Task Instructions

1. Verify sprint status is "paused" or "paused-at-breakpoint":

   • If "in-progress": "Sprint is already running. Use /sprint-status to check."
   • If "not-started": "Sprint not started. Use /run-sprint."
   • If "completed": "Sprint completed. Nothing to resume."
   • If "paused-at-breakpoint": Continue to step 2 (breakpoint resume)
   • If "paused": Continue to step 2 (regular pause resume)

2. Update PROGRESS.yaml status:

   Edit PROGRESS.yaml to set status back to "in-progress":

   status: in-progress
   

   Also remove any of these fields if present:

   • pause-requested: true
   • pause-reason: ...
   • breakpoint-phase-id: ...

3. Output instructions:

   For regular paused sprints:

   Sprint resumed: {name}
   
   Status: in-progress
   Queue: {queue-count} tasks remaining
   Next task: {next-task-id}
   
   To start processing tasks:
   /run-sprint {sprint-dir}
   

   For breakpoint-paused sprints:

   Sprint resumed from breakpoint: {name}
   
   Breakpoint was at: {breakpoint-phase-id}
   Status: in-progress
   Remaining phases: {remaining-count}
   Next phase: {next-phase-id}
   
   To continue execution:
   /run-sprint {sprint-dir}
   

Notes

The resume command only updates the status. To actually start processing tasks again, the user needs to run /run-sprint which will launch the TypeScript sprint runtime with fresh context per task.

When resuming from a breakpoint:

• The runtime will automatically advance to the phase AFTER the breakpoint phase
• All work from the breakpoint phase is preserved
• Human edits made during the pause are incorporated

Success Criteria

• PROGRESS.yaml status set to "in-progress"
• pause-requested field removed if present
• breakpoint-phase-id field removed if present
• User instructed to run /run-sprint to continue