| name | sprint-workflow |
| description | 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 understand the sprint execution model and its convergent diffusion approach. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
|
| allowed-tools | Read |
| version | 1.20.0 |
| author | Damien Laine <damien.laine@gmail.com> |
| license | MIT |
| tags | ["community","workflow","sprint-workflow"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Sprint Workflow
Overview
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.
Prerequisites
- Sprint plugin installed (
/plugin install sprint)
- Project onboarded via
/sprint:setup (creates .claude/project-goals.md and .claude/project-map.md)
- Sprint created via
/sprint:new with a completed specs.md
- Understanding of the agent system (see the
agent-patterns skill)
Instructions
- Phase 0 -- Load Specifications. The orchestrator locates the sprint directory at
.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.
- Phase 1 -- Architectural Planning. The project-architect agent reads
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.
- Phase 2 -- Implementation. The orchestrator spawns implementation agents in parallel based on the architect's SPAWN REQUEST blocks. Agents include
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.
- Phase 3 -- Testing. Testing agents execute sequentially:
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.
- Phase 4 -- Review and Iteration. The architect reviews all agent reports, analyzes conformity against specifications, updates specs (removing completed items, adding fixes for failures), and updates . The architect then decides: spawn more implementation agents, run more tests, or finalize.
