jeremylongshore/tons-of-skills-marketplace / plugins/community/sprint/skills/sprint-workflow
sprint-workflow
VerifiedExecute 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.
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.mdand.claude/project-map.md) - Sprint created via
/sprint:newwith a completedspecs.md - Understanding of the agent system (see the
agent-patternsskill)
Instructions
- Phase 0 -- Load Specifications. The orchestrator locates the sprint directory at
.claude/sprint/[N]/, readsspecs.mdfor requirements, readsstatus.mdif resuming a prior iteration, and detects the project type for framework-specific agent selection. See${CLAUDE_SKILL_DIR}/references/sprint-phases.mdfor the full phase reference. - Phase 1 -- Architectural Planning. The project-architect agent reads
project-map.mdfor architecture context andproject-goals.mdfor 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, andallpurpose-agent. Each agent reads its assigned spec files and the sharedapi-contract.md, then returns a structured report. - Phase 3 -- Testing. Testing agents execute sequentially:
qa-test-agentruns first (API and unit tests), thenui-test-agentruns 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
status.md. The architect then decides: spawn more implementation agents, run more tests, or finalize. - Phase 5 -- Finalization. The orchestrator writes the final
status.mdsummary, ensures all spec files are in a consistent state, cleans up temporary files likemanual-test-report.md, and signals FINALIZE to end the sprint. - Convergence model. Each iteration reduces noise: completed work is removed from specs, working code is preserved, and only failures are re-addressed. Most sprints converge within 3-5 iterations. After 5 iterations without convergence, the orchestrator pauses and prompts for manual intervention.
Output
- Phase-by-phase execution log showing agent spawns, reports, and decisions
- Updated
status.mdafter each iteration reflecting completed and remaining work - Specification files that shrink with each iteration as requirements are satisfied
- Final
status.mdsummary upon sprint completion - FINALIZE signal to the orchestrator when all specs are satisfied
Error Handling
| 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) |
Examples
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
Resources
${CLAUDE_SKILL_DIR}/references/sprint-phases.md-- Detailed reference for all six phases with agent assignments and handoff rules- Agent patterns skill for SPAWN REQUEST format and report structure
- Spec writing skill for authoring effective
specs.mdfiles - API contract skill for designing the shared interface between agents
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |