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…

MITAuto-check passed

Install Sprint Workflow

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sprint-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace sprint-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/sprint-workflow .claude/skills/sprint-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sprint-workflow
GitHub stars
2.8k
Token cost
~1.4k tokens
SKILL.md length
546 words
Files
4 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 7 steps: Phase 0 -- Load Specifications. The… → Phase 1 -- Architectural Planning. The… → Phase 2 -- Implementation. The… → …
  • Asks about how sprints work
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Sprint Workflow is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/errors.md`, `references/examples.md` and `references/sprint-phases.md`). Compatibility notes: Designed for Claude Code

The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Asks about how sprints work
  • Iteration workflow
  • Convergent development
  • Sprint lifecycle

Example prompts

  • “how sprints work”
  • “sprint phases”
  • “iteration workflow”
  • “/sprint-workflow”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Phase 0 -- Load Specifications. The orchestrator locates the sprint directory at .claude/sprint/[N]/, reads specs.md for requirements…
  2. Phase 1 -- Architectural Planning. The project-architect agent reads project-map.md for architecture context and project-goals.md for…
  3. Phase 2 -- Implementation. The orchestrator spawns implementation agents in parallel based on the architect's SPAWN REQUEST blocks. Agents…
  4. Phase 3 -- Testing. Testing agents execute sequentially: qa-test-agent runs first (API and unit tests), then ui-test-agent runs…
  5. Phase 4 -- Review and Iteration. The architect reviews all agent reports, analyzes conformity against specifications, updates specs…
  6. Phase 5 -- Finalization. The orchestrator writes the final status.md summary, ensures all spec files are in a consistent state, cleans up…
  7. Convergence model. Each iteration reduces noise: completed work is removed from specs, working code is preserved, and only failures are…

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Sprint Workflow loads about 1.4k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 546 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~96
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 546 words, ~1,413 tokens.

Download SKILL.mdSave it as .claude/skills/sprint-workflow/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
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
compatibility
Designed for Claude Code
version
1.20.0
author
Damien Laine <damien.laine@gmail.com>
license
MIT
tags
community, workflow, sprint-workflow

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

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. Phase 5 -- Finalization. The orchestrator writes the final 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.
  7. 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.
Show full SKILL.md (212 more words)Show less

Output

  • Phase-by-phase execution log showing agent spawns, reports, and decisions
  • Updated status.md after each iteration reflecting completed and remaining work
  • Specification files that shrink with each iteration as requirements are satisfied
  • Final status.md summary upon sprint completion
  • FINALIZE signal to the orchestrator when all specs are satisfied

Error Handling

ErrorCauseSolution
Sprint stuck in iteration loop (hits 5 iterations)Specs too broad or contain unresolvable conflictsReview status.md for blocking issues; narrow scope or resolve conflicting requirements
Phase 2 agents not spawnedArchitect SPAWN REQUEST missing or malformedVerify architect agent produced valid SPAWN REQUEST blocks with correct agent names
Tests fail repeatedly on same issueImplementation does not match contractCompare agent output against api-contract.md; check for schema mismatches
Sprint cannot find specsWrong sprint directory numberVerify .claude/sprint/[N]/specs.md exists; run /sprint:new if needed
Architect skips testing phaseTesting section missing from specs.mdAdd QA: required and UI Testing: required to the specs (see spec-writing skill)

Examples

Starting a new sprint:

bash
/sprint:new       # Creates .claude/sprint/1/specs.md
# Edit specs.md with requirements
/sprint           # Executes the full phase lifecycle

Resuming after iteration pause:

bash
# 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.md files
  • API contract skill for designing the shared interface between agents

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/.curated/sprint-workflow of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/errors.md
  • references/examples.md
  • references/sprint-phases.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Sprint Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sprint Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sprint Workflow this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.4kAutomated safety check: PassMIT
Executealirezarezvani/claude-skills28k—~831Automated safety check: PassMIT
Debugging Executionsn8n-io/n8n207k—~2.6kAutomated safety check: PassCustom licence
Sprint Planphuryn/pm-skills27k—~590Automated safety check: PassMIT
Sprint Status SnapshotDonchitos/Claude-Code-Game-Studios26k—~3kAutomated safety check: PassMIT
Sprint Plan BuilderDonchitos/Claude-Code-Game-Studios26k—~4.1kAutomated safety check: PassMIT

Similar skills

  • Execute

    alirezarezvani/claude-skills

    /cs:execute <decision — Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision.

    28k GitHub stars~831 tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed
  • Official

    Debug failed or wrong-output workflow executions using executions tools.

    207k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Sprint Plan

    phuryn/pm-skills

    Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification.

    27k GitHub stars~590 tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • Sprint Status Snapshot

    Donchitos/Claude-Code-Game-Studios

    Gives a fast, read-only sprint snapshot with burndown and emerging risks in under 30 lines, plus at most one concrete recommendation.

    26k GitHub stars~3k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed
  • Sprint Plan Builder

    Donchitos/Claude-Code-Game-Studios

    Creates or updates a sprint plan from the current milestone, completed work and available capacity, sizing the story count to the project's granularity setting.

    26k GitHub stars~4.1k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed
  • Ulw Execute

    code-yeongyu/oh-my-openagent

    Executes a written ulw-plan work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents.

    70k GitHub stars~6.3k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Sprint Workflow

What does Sprint Workflow do?

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 is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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.

When should I use Sprint Workflow?

Sprint Workflow fits situations like: asks about how sprints work; iteration workflow; convergent development; sprint lifecycle.

How do I install Sprint Workflow in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill sprint-workflow -a claude-code`. Or copy the skill folder (skills/.curated/sprint-workflow in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/sprint-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Sprint Workflow in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill sprint-workflow -a codex`. Or copy the skill folder (skills/.curated/sprint-workflow in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/sprint-workflow in your project. Codex loads it when a task matches its description.

Can I use Sprint Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill sprint-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sprint-workflow, .gemini/skills/sprint-workflow, .github/skills/sprint-workflow and .opencode/skills/sprint-workflow in your project.

What does Sprint Workflow need to run?

SKILL.md names no scripts, command-line tools or credentials: Sprint Workflow is instructions for the agent only. Its frontmatter pre-approves these tools: Read. Compatibility (from SKILL.md): Designed for Claude Code.

Does Sprint Workflow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sprint Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sprint Workflow use?

Sprint Workflow is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sprint Workflow use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.8k tokens, read only when the agent opens those files.

What are the alternatives to Sprint Workflow?

Skills that share tags, products or a category with Sprint Workflow: Execute (alirezarezvani/claude-skills, 28k stars), Debugging Executions (n8n-io/n8n, 207k stars), Sprint Plan (phuryn/pm-skills, 27k stars) and Sprint Status Snapshot (Donchitos/Claude-Code-Game-Studios, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sprint Workflow?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.