sprint-plan

Generate sprint plans aligned with milestones, capacity, and backlog readiness.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill sprint-plan-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/sprint-plan
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill sprint-plan-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns milestone goals, team capacity, backlog readiness, and QA requirements into a single actionable sprint plan so teams avoid scope creep, ambiguous acceptance criteria, and untested deliveries.

Core Features & Use Cases

  • Sprint authoring and updates: Create a new sprint plan or update an existing one using current milestones, previous sprint velocity, and ready stories from the design backlog.
  • Machine-readable status output: Auto-generate or update production/sprint-status.yaml to serve as the canonical source of story status for other studio tools and commands.
  • Quality and feasibility gates: Run producer feasibility checks, enforce QA plan presence, and surface risks and dependencies before writing the sprint to the repo.
  • Use Case: Prepare a sprint for the next milestone, run a producer gate in full review mode, and then write the sprint and sprint-status file for tracking and QA handoff.

Quick Start

Ask the skill to "sprint-plan new --review lean" to generate a draft sprint plan, run feasibility checks, and prompt to write the plan and sprint-status file.

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 that aligns milestone goals with team capacity and backlog readiness?

To generate a sprint plan aligned with milestone goals, the skill reads previous sprint velocity, design backlog files, and risk registers, then runs producer and QA gates to ensure scope matches team capacity before writing the final plan.

What is the best way to avoid scope creep and untested deliveries in agile game development?

Avoiding scope creep in agile game development requires enforcing producer feasibility checks and QA plan presence during sprint creation, ensuring all stories meet readiness criteria before entering the sprint backlog.

How do I create a machine-readable sprint status file for studio tools?

You can create a machine-readable sprint status file by generating or updating production/sprint-status.yaml, which serves as the canonical source of story status for downstream QA handoff and studio tracking tools.

Can I run producer feasibility checks and QA gates before writing a sprint plan to the repo?

Yes, you can run producer feasibility checks and enforce QA plan presence before writing the sprint to the repo by using the review mode during sprint generation to surface risks and dependencies.

Does sprint planning work with existing milestones and previous sprint velocity in a production repository?

Sprint planning works with existing milestones and previous sprint velocity by reading milestone goals, past sprint data, and design backlog files directly from the production-oriented game development repository.

What are the limitations of automated sprint planning for game development?

Automated sprint planning relies on accurate backlog readiness and risk register inputs; it cannot compensate for missing design documentation or undefined acceptance criteria in the source repository files.