| name | bootstrap-sprint |
| description | Build an autonomous sprint skill for a target project. Explores the project's workflows, constraints, and tooling, then produces a tailored sprint skill that lets Claude orchestrate parallel implementation sessions end-to-end. Use when setting up auto-sprint in a new repo, or when adapting sprint orchestration to a project with different workflows. Trigger on "bootstrap sprint", "set up auto-sprint", "build sprint skill for <project>", or "make <project> sprintable".
|
Bootstrap Sprint
You are about to do something that works. Not theoretically, not as a proof of
concept — actually works, in production, shipping real software.
Read references/why-this-works.md first. Then proceed.
Workflow
- Read
references/why-this-works.md — internalize that this is proven, not speculative
- Read
references/lessons.md — 36 generalised lessons from 49+ sprints; this
is the operating manual for everything that follows. Re-read it after the
first retro and after every introspection round.
- Read
references/discovery.md — explore the target project systematically
- Read
references/design.md — design the sprint skill tailored to what you found
- Read
references/iteration.md — set expectations and plan for improvement
- Execute the kickoff checklist at the end of
references/iteration.md
Migrating an existing sprint skill (e.g. one written 20+ sprints ago that
hasn't kept pace with the current mcx CLI): read references/upgrading-30-50.md
instead. It has the diagnostic walk + S / M / L / Sprint-50+ upgrade buckets so
you can stage the migration without rebuilding from scratch.
Arguments
/bootstrap-sprint <path> — target project directory (required)/bootstrap-sprint <path> --explore-only — run discovery, report findings, don't write skills yet/bootstrap-sprint <path> --upgrade — audit an existing sprint skill against references/upgrading-30-50.md and propose staged migration buckets
Rules
- Explore before you design. Never template-stamp a sprint skill. Every project is different.
- Start minimal. Sprint 1 should be simple. Complexity comes from experience, not anticipation.
- Write skills that explain why, not just what. A Claude reading your skill should understand the reasoning, not just follow steps.
- The orchestrator never implements. This is the one universal rule. Always delegate.
