sprint-workflow
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.
- License 许可
- MIT
- 最近更新
- 2026-05-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- sprint-workflow
- author
- Damien Laine <damien.laine@gmail.com>
- license
- MIT
- version
- 1.0.0
- 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
- compatible-with
- claude-code, codex, openclaw
02 资源文件 3
- 参考文档references/errors.md165 B
- 参考文档references/examples.md8.8 KB
- 参考文档references/sprint-phases.md1.6 KB
03 SKILL.md 正文
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
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
zustand-store-creator
Zustand Store Creator - Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category.
zero-trust-config-helper
Zero Trust Config Helper - Auto-activating skill for Security Advanced. Triggers on: zero trust config helper, zero trust config helper Part of the Security Advanced skill category.
zapier-integration-helper
Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.
zai-cli
Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP. Use when user needs image/video analysis, OCR, UI-to-code conversion, error diagnosis, real-time web search, web page to markdown extraction, or GitHub code exploration. Trigger with phrases like "analyze this image", "search the web for", "read this page", "explore this repo", or "use zai". Requires Z_AI_API_KEY.
yt-research
Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.