sprint-plan

Generates sprint plans from milestones, previous results, and design backlogs for agile teams.

Updated May 24, 2026
One-click install
npx skills add https://github.com/LeKay/ai-game --skill sprint-plan-lekay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/LeKay/ai-game/tree/main/.claude/skills/sprint-plan
Command: npx skills add https://github.com/LeKay/ai-game --skill sprint-plan-lekay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of creating and updating sprint plans, tracking progress, and managing sprint status for agile teams, saving time and reducing errors.

Core Features & Use Cases

  • Sprint Plan Generation: Automatically generates a new sprint plan or updates an existing one based on current milestones, completed work, and available capacity.
  • Contextual Information: Pulls context from production documents and design backlogs.
  • Review Modes: Supports different review modes for sprint planning (full, lean, solo).
  • Status Reporting: Generates sprint status reports to track progress and identify emerging risks.

Quick Start

Generate a new sprint plan for Sprint N using the 'new' command.

Frequently Asked Questions about sprint-plan

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

FAQPage Schema
How do I automate sprint planning for agile teams?

Automating sprint planning involves generating or updating sprint plans based on milestone data, previous sprint results, and design backlogs. The Skill requires access to production documents to pull contextual information for the sprint.

What is the best way to track agile sprint status and identify risks?

Tracking agile sprint status is done by generating automated sprint status reports. These reports track current progress against milestones and help identify emerging risks during the sprint cycle.

Do I need production documents to generate a sprint plan?

Yes, production documents and design backlogs are required to generate a sprint plan. The automation pulls contextual information from these inputs to update the plan based on available capacity and completed work.

Can I use different review modes for sprint plan automation?

Yes, different review modes for sprint plan automation are supported, including full, lean, and solo modes. These options adjust the sprint planning and QA plan verification process based on your team's workflow.

How to update an existing sprint plan based on previous sprint results?

Updating an existing sprint plan requires inputting previous sprint results and current milestone data. The automation uses this information, along with design backlogs, to adjust the plan for available capacity and completed work.