An end-to-end sprint orchestrator that coordinates starting, planning, validating, implementing, reviewing, and reflecting on a sprint. A sprint is a fixed period in which a team delivers selected work.

Use it to run sprint ceremonies, create a branch and pull request, monitor continuous integration checks, and optionally merge after the checks and definition of done pass.

It connects the separate stages of a sprint so the whole cycle can be run from one command, while still requiring human approval before automatic merging by default.

auto-sprint — Command for Claude Code by TheBeardedBearSAS

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craft

Made for: Claude Code.

Or install claude-craft, the plugin that ships this one along with the rest of its 56 skills, 94 commands, 47 agents, 5 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/auto-sprint/github.svg)](https://agentmods.dev/commands/thebeardedbearsas/claude-craft/auto-sprint)

Your own site

<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/auto-sprint"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/auto-sprint/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/auto-sprint"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/auto-sprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,937 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00033	$0.02937
Opus 5.5	$0.00013	$0.01175
Sonnet 5.5	$0.00007	$0.00587
Haiku 4.5	$0.00003	$0.00294

Measured 4d ago against content hash bc37bfbd799b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

auto-sprint scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/workflow/auto-sprint.md · 198 lines

How it starts

The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Auto Sprint — Orchestrateur de Sprint de Bout en Bout

Tu joues le rôle de Product Owner / Scrum Master et tu pilotes un sprint complet, du lancement au merge, en une seule commande. Chaque cérémonie s'exécute dans un sous-agent isolé : la fenêtre de contexte propre au sous-agent remplace le /clear manuel entre les étapes, ce qui permet à ton contexte d'orchestrateur de rester léger. La phase d'implémentation est conduite par toi en tant que chef d'orchestre (même logique que /team:sprint) afin d'éviter l'imbrication d'Agent Teams.

Cette commande automatise ce qui nécessitait auparavant six commandes manuelles avec un /clear entre chaque :

/workflow:start N -> /project:decompose-tasks 00N -> /gate:validate-sprint 00N
-> /team:sprint "sprint-00N" -> /workflow:review N -> /workflow:retro N

…et ajoute : branche, commit, Pull Request, surveillance CI et merge.

Arguments

$ARGUMENTS

<N> : Numéro du sprint (ex. 5). Obligatoire.
--auto-merge : Merge automatiquement dès que la CI est verte et que la DoD est validée. Défaut : DÉSACTIVÉ — la commande se met en pause et attend un GO humain explicite avant de merger (respecte la règle de « revue obligatoire », règle 09, et le principe Karpathy « pas d'auto-merge sans revue humaine »).
--max-fix-attempts=2 : Nombre maximal de tentatives de correction automatique par gate échoué avant abandon (défaut : 2).
--max-workers=3 : Nombre maximal de workers dev parallèles pendant la phase d'implémentation (défaut : 2, max : 3).
--base=main : Branche de base pour la PR (défaut : main).
--dry-run : Affiche les 9 phases planifiées et le contexte de sprint résolu, puis s'arrête. Aucune écriture.
--overnight : Transmis à la phase d'implémentation (borné, s'arrête à 6h).

Prérequis

Claude Code v2.1.32+ avec le support Agent Teams
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 défini
CLI gh authentifié (création de PR / checks / merge)
Docker disponible (tous les tests s'exécutent via Docker — voir le CLAUDE.md du projet)
Projet BMAD v6 : .bmad/sprint-status.yaml est créé par /workflow:start (phase 1) s'il n'existe pas

Read the full file on GitHub · 198 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

4d ago Changed bc37bfbd799b
1mo ago First seen · 198 lines · 33 tokens per session scan A 1c4d16af458d

Subscribe to this mod's changes

auto-sprint is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (107 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 2,937 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Claude Code Git and workflow Project management agents ai-tools bmad clean-architecture ddd

swarm-migrate

Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…

yonatangross/orchestkit · 103 tokens

auto-sprint

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Auto Sprint — Orchestrateur de Sprint de Bout en Bout

Arguments

Prérequis

What this file has done since we first saw it

Other commands, from other repositories

swarm-migrate

deploy

update-counts

lavra-ship

update-docs

speckit.chore.issue