skills.rest
imgamer
imgamerCOMMUNITY
Explore all skills by this author →
GitHub

sprint-plan

Generate sprint plans and sprint-status YAML from milestones and risk data.

Updated Dec 22, 2024
Search Tags:#sprint planning#status tracking#capacity planning#agile workflow#feasibility gate#roadmap execution#qa plan readiness
One-click install
npx skills add https://github.com/imgamer/AILearn --skill sprint-plan-imgamer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/imgamer/AILearn/tree/main/game-studios/Claude-Code-Game-Studios-e375f/.claude/skills/sprint-plan
Command: npx skills add https://github.com/imgamer/AILearn --skill sprint-plan-imgamer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns scattered production milestones, previous sprints, design-ready documents, and risk context into a coherent sprint plan with a machine-readable sprint status file.

Core Features & Use Cases

  • Sprint plan generation for new sprints, producing a structured markdown plan (goal, capacity, task tables, risks, dependencies, and definition of done).
  • Sprint plan updates for existing sprints, letting you add/remove/reprioritize/re-estimate stories while preserving in-progress/done statuses and re-running feasibility checks.
  • Sprint status file creation by generating production/sprint-status.yaml with consistent priority/status mapping to drive other sprint tooling.

Quick Start

Use sprint-plan in new mode to generate a sprint proposal from the current milestone and available production/backlog context.

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 existing backlog context?▼

Sprint plan generation parses production milestones, past sprint data, and design-ready documents to produce a structured markdown plan with capacity, task tables, risks, and definition of done.

What is a sprint status source of truth and how does it work?▼

A sprint status source of truth is a machine-readable `production/sprint-status.yaml` file mapping story priorities and statuses to drive other sprint tooling and QA-alignment workflows.

Can I update an existing sprint plan without losing in-progress or done statuses?▼

Yes, sprint plan updates allow you to add, remove, reprioritize, or re-estimate stories while preserving in-progress and done statuses, then re-run feasibility checks against the updated backlog.

How do I enforce producer and QA gate readiness during sprint planning?▼

Sprint planning enforces producer and QA gate logic by reviewing the risk register and design-ready documents, ensuring feasibility and QA-alignment before finalizing the sprint proposal.

What is the best way to track sprint status against production milestones?▼

The best way to track sprint status is generating a `sprint-status.yaml` file from live backlog context, mapping story priorities and statuses to maintain a single source of truth for roadmap execution.

What context do I need for sprint feasibility review and capacity planning?▼

Sprint feasibility review requires scanning designated directories for production milestones, previous sprints, design-ready documents, and the risk register to validate capacity planning and QA readiness.

Related Skills

Explore More Product & Management Skills→
pixel-cellarpixel-cellar
277

sprint-plan

Generate or update sprint plans from milestones, completed work, and capacity.

Official
Intermediate
ldk-hubldk-hub

bmad-sprint-status

Summarize sprint status and surface risks from sprint-status.yaml.

Community
Advanced
imclabimclab
1

sprint-plan

Generate sprint plans with acceptance criteria and gating checks.

Official
Advanced
wsmanwsman
18

sprint-plan

Generate feasibility-checked sprint plans from milestones, backlogs, and capacity.

Community
Advanced