From dream-team
Autonomous sprint execution with checkpoint-based progress tracking
How this skill is triggered — by the user, by Claude, or both
Slash command
/dream-team:sprint-runnerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The sprint runner (`scripts/run-task.sh`) enables autonomous execution of sprint tasks. It reads the checkpoint from `progress.md`, launches Claude with fresh context each iteration, and loops until the sprint is complete or blocked.
The sprint runner (scripts/run-task.sh) enables autonomous execution of sprint tasks. It reads the checkpoint from progress.md, launches Claude with fresh context each iteration, and loops until the sprint is complete or blocked.
<!-- CHECKPOINT --> block from progress.md to determine current stateprogress.md (checkpoint + log) and tasks.md (checkboxes)phase: done or phase: blockedSPRINT_DIR=planning/sprints/sprint-N-name
mkdir -p $SPRINT_DIR
Copy the templates from this plugin's templates/ directory:
plan.md — Architecture decisions, phases, riskstasks.md — Task checklist with status trackingprogress.md — Checkpoint block + progress logComplete plan.md with architecture decisions and phases. Fill in tasks.md with all implementation tasks. Initialize progress.md with the first checkpoint.
./scripts/run-task.sh planning/sprints/sprint-N-name
The checkpoint is the ONLY state that persists between runner iterations. Make it precise:
<!-- CHECKPOINT
sprint: 5
sprint_name: dark-mode
active_task: "Implement theme provider service"
phase: implementing
last_completed: "Created ThemeConfig model with color palette and font definitions"
next_step: "Create ThemeProvider service with system preference detection and manual toggle"
blockers: none
files_modified: src/models/ThemeConfig.ts
-->
active_task: Exact task name from tasks.mdnext_step: Specific enough that a fresh session can start immediatelyfiles_modified: Every file touched in the current session (helps the next iteration know what to read)The runner handles bug fixes with a TDD workflow:
next_step in the checkpoint points to the next task, not a vague descriptionnpx claudepluginhub numanumanuma/claude-plugins --plugin dream-teamExplains sprint workflow's convergent diffusion model, 6 phases from spec loading to finalization, agent spawning for Python/Next.js/CI-CD, testing/review, and resumption.
Runs opinionated sprint pipeline from brainstorm to retro, generating Markdown artifacts and JSON handoffs per phase. Includes CLI for init, status, complete, skip, and dry-run.
Manages agile sprints with Skeleton → Muscles → Skin layers, checkpoints, status checks, and quality gates for iterative development. Triggers on 'start sprint', 'checkpoint', or /agile commands.