sprint
Skill2 starsChanged 54 days agoMITView on GitHub
The whole company works on one goal given by the human (for example "launch in Belgium" or "prepare the pitch for bakeries"). The Director plans, each needed role delivers one document, the auditor reviews, and the Director reports. Use when the human types sprint "<goal>".
27 other projects use a version of this.
Adopted by
Most recently taken up by
- varelaia/claude-skills-publictheir own version, first seen Nov 8, 2026
- naman10parikh/pennytheir own version, first seen Nov 8, 2026
- naman10parikh/wikimemtheir own version, first seen Nov 8, 2026
- dagonet/claude-code-toolkittheir own version, first seen Nov 1, 2026
- atelier-fashion/adlc-toolkittheir own version, first seen Oct 31, 2026
- naman10parikh/turbotheir own version, first seen Oct 25, 2026
Used with
Projects with it also use ecosystem-reference, fractal-delegation and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
naman10parikhSkillecosystem-reference
Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.
Also in 5 projects that use this
- naman10parikhSkill
fractal-delegation
Also in 5 projects that use this
KirchliveSkillskill-routing
Decides which of the installed skills a task needs and loads them before the work starts. This skill should be used at the beginning of any multi-step task — build, fix, refactor, migrate, review, plan, release, research, write, design, video — and again at every phase change, after context compaction, and when work moves into a different part of the codebase. Use it for requests like "let's build X", "fix this bug", "refactor Y", "plan the migration", "review this", and also when the user asks which skill applies, why a skill did not fire, or asks to check what is available.
Also in 5 projects that use this
sublimotionSkillagent-runtime
Launch and manage detached agent runs on EKS via the agent-runner CLI. Use when the user says "launch an agent run", "agent runtime", "agent-runner", "run this spec on the cluster", "check run status", "agent run logs", or "stop a run". Do NOT use for writing the agent-runner code itself (edit the sibling ../agent-runner repo), Terraform of the foundation (use terraform-automation), or GPU serving deployments (use infra-deployer).
Also in 5 projects that use this
GoZippySkillrepo-scout
Also in 5 projects that use this
BenjaminGSkillharness-review
Turn one PR's review comments into harness fixes — classify each cause by the most solid place it can live (codebase, lint, rules, skill), then draft the fixes in a separate PR.
Also in 5 projects that use this
- +6 more from naman10parikh
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- meta-pytorch/OpenEnv★ 2.8ksame name
- huggingface/OpenEnv★ 2.8ksame name
- popup-studio-ai/bkit-claude-code★ 605same name
- ww-w-ai/bkit-claude-code★ 605same name
- atelier-fashion/adlc-toolkit★ 173same name
- naman10parikh/agentgrid★ 9same name
- sunitghub/canon-skills★ 9same name
- naman10parikh/wikimem★ 8same name
- dagonet/claude-code-toolkit★ 4same name
- SaketMunda/claude-org-template★ 3same name
17 more not listed
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 repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- artifactSkill
- draft-outreachSkill
- follow-upsSkill
- knowledgeSkill
- meeting-briefSkill
- one-pagerSkill
- proposalSkill
- prospectSkill
- qualifySkill
- quote-invoiceSkill
- repliesSkill
- setupSkill
- sprintSkill
- artifactSkill
- draft-outreachSkill
- follow-upsSkill
- knowledgeSkill
- meeting-briefSkill
- one-pagerSkill
- proposalSkill
- prospectSkill
- qualifySkill
- quote-invoiceSkill
- repliesSkill
- setupSkill
The file
Files
Sprint
- Restate the goal in one line and list the roles needed (not all roles every time). Ask the human only if the goal is ambiguous.
- Board: one card per role with a precise deliverable and its path in
workspace/departments/<dept>/. - Order (each output feeds the next): strategist, then marketer, then sales, then finance, then consultant or tech if needed. Independent roles may run in parallel if your tool supports it.
- Each role: one document, front matter
author, sources for facts, handoff to the next role. - The auditor reviews every sprint document and writes
workspace/departments/audit/<date>-sprint.md. Fix what it blocks before reporting. - Journal: decisions taken. Report to the human in 8 lines max with the paths to read.
Budget: one deliverable per role per sprint unless the human asks for more.
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.