Execute this skill should be used when the user asks about "how sprints work", "sprint phases", "iteration workflow", "convergent development", "sprint lifecycle", "when to use sprints", or wants to...
Sprint Workflow describes the convergent diffusion execution model used by the Sprint plugin. A sprint progresses through six distinct phases -- from loading specifications through architectural planning, parallel implementation, testing, review, and finalization.
/plugin install sprint)/sprint:setup (creates .claude/project-goals.md and .claude/project-map.md)/sprint:new with a completed specs.mdagent-patterns skill).claude/sprint/[N]/, reads specs.md for requirements, reads status.md if resuming a prior iteration, and detects the project type for framework-specific agent selection. See ${CLAUDE_SKILL_DIR}/references/sprint-phases.md for the full phase reference.project-map.md for architecture context and project-goals.md for business objectives. It produces specification files (api-contract.md, backend-specs.md, frontend-specs.md) and returns SPAWN REQUEST blocks for implementation agents.python-dev, nextjs-dev, cicd-agent, and allpurpose-agent. Each agent reads its assigned spec files and the shared api-contract.md, then returns a structured report.qa-test-agent runs first (API and unit tests), then ui-test-agent runs browser-based E2E tests. Framework-specific diagnostics agents (e.g., nextjs-diagnostics-agent) run in parallel with UI tests. All agents produce test reports.status.md. The architect then decides: spawn more implementation agents, run more tests, or finalize.status.md summary, ensures all spec files are in a consistent state, cleans up temporary files like manual-test-report.md, and signals FINALIZE to end the sprint.status.md after each iteration reflecting completed and remaining workstatus.md summary upon sprint completion| Error | Cause | Solution |
|---|---|---|
| Sprint stuck in iteration loop (hits 5 iterations) | Specs too broad or contain unresolvable conflicts | Review status.md for blocking issues; narrow scope or resolve conflicting requirements |
| Phase 2 agents not spawned | Architect SPAWN REQUEST missing or malformed | Verify architect agent produced valid SPAWN REQUEST blocks with correct agent names |
| Tests fail repeatedly on same issue | Implementation does not match contract | Compare agent output against api-contract.md; check for schema mismatches |
| Sprint cannot find specs | Wrong sprint directory number | Verify .claude/sprint/[N]/specs.md exists; run /sprint:new if needed |
| Architect skips testing phase | Testing section missing from specs.md |
Add QA: required and UI Testing: required to the specs (see spec-writing skill) |
Starting a new sprint:
/sprint:new # Creates .claude/sprint/1/specs.md
# Edit specs.md with requirements
/sprint # Executes the full phase lifecycle
Resuming after iteration pause:
# Review .claude/sprint/1/status.md for blockers
# Adjust specs.md to narrow scope or fix conflicts
/sprint # Resumes from Phase 0, reads updated specs and status
Typical convergence flow:
Iteration 1: Architect plans → 3 agents implement → tests find 2 failures
Iteration 2: Architect narrows specs to 2 fixes → agents patch → tests pass
Iteration 3: All specs satisfied → FINALIZE
${CLAUDE_SKILL_DIR}/references/sprint-phases.md -- Detailed reference for all six phases with agent assignments and handoff rulesspecs.md files