sprint

Orchestrate sprint planning, implementation, and review cycles with checkpoint-driven workflows.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/lasswellt/cc-plugin-suite --skill sprint-lasswellt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint
Source: https://github.com/lasswellt/cc-plugin-suite/tree/main/skills/sprint
Command: npx skills add https://github.com/lasswellt/cc-plugin-suite --skill sprint-lasswellt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end sprint cycles (planning, implementation, and review) across multiple sub-skills to deliver software on a predictable cadence.

Core Features & Use Cases

  • Orchestrates the three sprint phases: planning, implementation, and review with optional loop mode.
  • Supports flags for resuming interrupted work, planning-only workflows, and autonomous execution without prompts.
  • Maintains state via checkpoints and integrates with sprint-dev and sprint-review to enforce a repeatable sprint process.

Quick Start

Run the sprint skill to start planning, implementing, and reviewing a sprint, with optional autonomous loop mode.

Frequently Asked Questions about sprint

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

FAQPage Schema
How do I automate end-to-end sprint planning and review cycles?

Automated sprint orchestration coordinates planning, implementation, and review phases across sub-skills to deliver software predictably. It uses a checkpoint-driven workflow and supports autonomous loop mode to maintain structured development cadences without manual intervention.

Can I resume an interrupted sprint cycle without losing progress?

Yes, interrupted sprint cycles can be resumed using the --resume flag. The workflow maintains state via checkpoints, allowing the orchestration process to pick up exactly where the previous development or review phase left off.

How does loop mode work for continuous software development sprints?

Loop mode enables autonomous execution of consecutive sprint cycles by automatically chaining planning, implementation, and review phases. It enforces a repeatable process using sprint-dev and sprint-review sub-skills without requiring manual prompts between iterations.

What's the best way to enforce a structured cadence for backlog management?

Enforcing a structured cadence requires a checkpoint-driven workflow that integrates planning, implementation, and review. Targeting software development projects with structured cadences ensures backlog management remains repeatable and predictable across autonomous iterations.

Do I need sub-skills to run a sprint planning-only workflow?

Sprint orchestration requires integration with sprint-dev and sprint-review sub-skills to execute full cycles. However, you can run a planning-only workflow by applying the appropriate flags to limit execution to the initial planning phase.

Why does sprint orchestration require checkpoint-driven workflows?

Checkpoint-driven workflows are required to maintain state across planning, implementation, and review phases. This ensures repeatable sprint processes, supports resuming interrupted work, and coordinates multiple sub-skills effectively during autonomous loop execution.