run-sprint
Skill1 starsChanged 2 days agoApache-2.0View on GitHub
Orchestrate an approved sprint — delegate every issue to the specialised agents lane by lane (locally) or dispatch issues to Claude in GitHub Actions (remotely), ending each issue as a pull request. Use when the maintainer asks to run or continue a sprint.
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- razbakov/skillstheir own version, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- razbakov/skills★ 5same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- add-methodSkill
- adr-newSkill
- commitSkill
- explain-changesSkill
- fix-ciSkill
- golden-caseSkill
- implement-specSkill
- onboardingSkill
- plan-sprintSkill
- pre-prSkill
- pr-triageSkill
- releaseSkill
- roadmap-updateSkill
- session-endSkill
- session-startSkill
- spec-newSkill
- translateSkill
- add-methodSkill
- adr-newSkill
- commitSkill
- explain-changesSkill
- fix-ciSkill
- golden-caseSkill
- implement-specSkill
- onboardingSkill
- plan-sprintSkill
- pre-prSkill
- pr-triageSkill
- releaseSkill
- roadmap-updateSkill
- run-sprintSkill
- session-endSkill
- session-startSkill
- spec-newSkill
- translateSkill
- fairmarkSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Read the issue (gh issue view N) and its spec.
- Very specific: line 18
No approved spec for method work: delegate to spec-writer, then stop this lane and ask the maintainer to approve.
- Distinctive: line 37
Keep a running table: issue, branch, PR, status, blockers.
- Very specific: line 41
when a lane needs generated artifacts, it becomes the generate lane of the sprint, the only one (sprints/README.md).
- Very specific: line 55
Do not change status to done: that is the maintainer's call.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
The main session is the orchestrator: subagents cannot start other subagents, so you delegate and keep the overview. Ask the maintainer which mode to use if not stated.
Preconditions
sprints/SNN.yamlexists withstatus: activeand passesuv run python scripts/sprint.py validate.mainis green.
Local mode (subagents, parallel lanes)
For each lane, in parallel where the agents tool supports isolated worktrees, otherwise one lane after the other. For each issue of the lane, in order:
- Read the issue (
gh issue view N) and its spec. Create branchsprint/SNN/N-<slug>. - No approved spec for method work: delegate to
spec-writer, then stop this lane and ask the maintainer to approve. test-engineerwrites failing tests for the issue's acceptance criteria.core-engineer(Rust core) ordocs-writer(documentation-only issues) implements.- Review by tier ("Effort proportional to risk" in AGENTS.md): none for small pull requests,
one
code-reviewerpass for substantial ones, plusnumerical-auditorfor numerical changes andsecurity-reviewerwhen dependencies or workflows changed. Fix every finding; a second pass only for a blocking logic defect, then escalate to the maintainer. Run at most three lanes at a time. uv run just checkgreen, docs in sync (the Stop hook enforces it).- Push and open the PR:
gh pr create --title "<type>(<scope>): ... [SPEC-NNNN]" --body "Closes #N ...". Never merge. Checkpoint state at every step: after each numbered step of this loop, runuv run python scripts/sprint.py state sprints/SNN.yaml N --step <step> [--pr <n> | --blocker "<why>" | --clear-blockers](the running table persisted, sprints/README.md, Sprint state). At every task switch append one line to.agents/journal/<date>-sprint-SNN-wip.md: issue, step, pull request, blockers, last commit of the lane. Both are local recovery state, git-ignored: a crash costs minutes, not a session of context. Keep a running table: issue, branch, PR, status, blockers. Each lane works in its own worktree (one worktree per session, AGENTS.md):
- a lane other than the generate lane never runs
uv run just generate; - when a lane needs generated artifacts, it becomes the generate lane of the sprint, the only one (sprints/README.md).
Remote mode (Claude in GitHub Actions)
For each issue: gh issue comment N --body "@claude Implement this issue following
.agents/skills/implement-spec/SKILL.md and AGENTS.md. Work test-first, run uv run just check,
and open a pull request that closes this issue." Issues of different lanes run in parallel
on separate runners. Then track the resulting PRs with scripts/sprint.py status.
End of run
Propose the merge order to the maintainer (sprints/README.md, Generated artifacts and the merge
order): pull requests carrying regenerated artifacts merge strictly one at a time; after each
of them merges, rebase the next on main and run uv run just generate in it again. Report
per lane: PRs opened, issues blocked and why, what the maintainer must review or decide.
Do not change status to done: that is the maintainer's call. Propose the removal of the
worktree of every merged pull request: the Retirement candidates of
uv run just workspace-report, never deleted without the maintainer's approval.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

