sprint-plan

Generate sprint plans with acceptance criteria and gating checks.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill sprint-plan-imclab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/sprint-plan
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill sprint-plan-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Task.

What problem does it solve?

It prevents sprint chaos by turning a milestone, backlog, capacity, and risk context into a structured, reviewable sprint plan with explicit acceptance criteria and gating checks.

Core Features & Use Cases

  • Generates sprint plans (new/update/status): Creates or refreshes a sprint’s Must/Should/Nice tasks, carryover, risks, dependencies, and Definition of Done so execution is aligned with the milestone.
  • Aligns sprint work to studio processes: Pulls in milestone state, previous sprint velocity, ready-for-implementation design docs, and risk register to reduce mismatches.
  • Supports feasibility and QA gating: Runs a producer feasibility gate and verifies/forces QA plan presence so “done” is testable and realistic.

Quick Start

Use sprint-plan to generate a new sprint plan using your current milestone and backlog by running the command: sprint-plan new --review lean.

Frequently Asked Questions about sprint-plan

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

FAQPage Schema
How do I generate a sprint plan from a milestone and backlog?

A sprint plan prevents sprint chaos by aligning must/should/nice task prioritization with milestone state, previous velocity, and the risk register. It reduces mismatches between planned work and actual studio capacity by pulling these contexts into a structured plan.

What's the best way to manage sprint carryover and risk assessment?

Assess sprint carryover and risk by running an update mode that evaluates previous sprint carryover against the risk register and dependencies. This ensures planned work accounts for unresolved items and mitigates delivery blockers before the next sprint begins.

How do I enforce QA readiness and producer feasibility before a sprint starts?

Enforce QA readiness and producer feasibility by applying delivery gating checks during sprint plan generation. The gate verifies producer feasibility review and forces QA plan presence, ensuring the definition of done is testable and realistic.

Does sprint planning work without a dedicated design readiness document?

Sprint planning requires ready-for-implementation design docs to align sprint work to studio processes and reduce mismatches. The workflow pulls in design readiness context to ensure tasks are properly scoped before execution begins.

Can I track sprint status in a machine-readable format?

Track sprint status using an optional sprint-status.yaml machine-readable file for story tracking. This format enables automated downstream processing and status reporting alongside the standard task tables.

Why does my sprint plan fail when the QA plan is missing?

Sprint plan generation enforces QA plan presence as a required gate behavior, halting the workflow when missing. This enforcement guarantees that done criteria remain testable and that required delivery gating checks are satisfied.