sprint

Coordinate multi-stage milestones into iterative brainstorms, plans, and coding.

42|3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/onsails/cc --skill sprint-onsails
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint
Source: https://github.com/onsails/cc/tree/main/sprint/skills/sprint
Command: npx skills add https://github.com/onsails/cc --skill sprint-onsails

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Milestones that are too large for a single spec often drift without structure. Sprint provides a living, stage-by-stage workflow where brainstorms, plans, and coding are coordinated under a single conductor, while executors handle implementation in isolated worktrees.

Core Features & Use Cases

  • Decompose large milestones into iterative stages with clear spec/plan artifacts.
  • Hand off coding to an executor (codex or mimo) while you steer the process.
  • Resume where you left off across sessions using a living sprint document.

Quick Start

Brainstorm and decompose a milestone into staged plans, then guide execution with an executor while you stay the conductor.

Frequently Asked Questions about sprint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage multi-stage milestones without losing progress across sessions?

Manage multi-stage milestones by decomposing them into iterative stages with a living sprint document. This document tracks brainstorms, plans, and coding, allowing you to resume exactly where you left off across sessions.

What is the best way to break down a large coding milestone into actionable plans?

Break down a large coding milestone by orchestrating iterative brainstorms and plans into per-stage spec files. This structure prevents drift and hands off clear implementation tasks to an executor.

Can I use isolated worktrees for executor coding tasks during a sprint?

Yes, you can use isolated worktrees for coding tasks. The sprint workflow uses nested subagents and isolated worktrees to ensure clean, auditable progress while the conductor steers the overall process.

How do codex and mimo executors handle implementation in a multi-stage sprint?

Codex and mimo executors handle implementation by receiving per-stage plan and spec files generated during the sprint. They execute coding tasks in isolated worktrees while you act as the conductor coordinating the workflow.

When should I use a structured sprint workflow instead of a single spec for milestone planning?

Use a structured sprint workflow instead of a single spec when milestones are too large and require multiple cycles of ideation, planning, isolation, execution, and review. A single spec often causes drift without proper stage-by-stage structure.