npx claudepluginhub mission42-ai/m42-claude-plugins --plugin m42-sprintResume execution of a paused sprint.
Find the most recent sprint directory:
ls -dt .claude/sprints/*/ 2>/dev/null | head -1
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 statusVerify sprint status is "paused" or "paused-at-breakpoint":
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: truepause-reason: ...breakpoint-phase-id: ...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}
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: