sprint-plan

Generates sprint plans and status files from milestones, backlogs, and team capacity.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill sprint-plan-claretagrapelike32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/sprint-plan
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill sprint-plan-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Planning a game development sprint requires pulling together milestone goals, previous velocity, design backlog items, and risk data scattered across many files, then validating the plan against real team capacity. This Skill automates that gathering and produces a structured sprint plan plus a machine-readable status file. ## Core Features & Use Cases - Sprint Plan Generation: Creates a new sprint plan with capacity calculation, prioritized task tables (Must/Should/Nice to Have), carryover, risks, and a Definition of Done checklist. - Update and Status Modes: Updates an existing sprint plan while preserving in-progress story statuses, or generates a progress status report with burndown assessment. - Feasibility and QA Gates: Runs a producer feasibility review on the story list and verifies a QA plan exists before implementation begins. - Use Case: A solo game developer starting Sprint 3 runs the skill, which reads the current milestone and previous sprint, drafts a capacity-aware plan, flags an unrealistic scope, and writes both production/sprints/sprint-3.md and production/sprint-status.yaml after approval. ## Quick Start Use the sprint-plan skill to generate a new sprint plan for the current milestone based on my design backlog and team capacity.

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 for a game development project?

Run the skill in new mode and it reads your current milestone, previous sprint, design backlog, and risk register, then drafts a capacity-aware plan with prioritized task tables. A producer feasibility gate reviews the story list before the plan is written to production/sprints/.

How do I update an existing sprint plan without losing story progress?

Use update mode, which reads the latest sprint plan and sprint-status.yaml, then lets you add, remove, reprioritize, or re-estimate stories. Stories already marked in-progress or done keep their status; only backlog and ready-for-dev stories can be freely changed.

What is the sprint-status.yaml file used for?

It is the machine-readable source of truth for story status, generated alongside the markdown sprint plan. Other skills like sprint-status, story-done, and dev-story read it directly without parsing markdown, tracking each story's priority, status, owner, and estimate.

What review modes does the sprint planning workflow support?

Three modes are supported: full spawns all director gate reviews, lean skips non-phase-gate director reviews and is the default, and solo skips all gates. The mode is stored in production/review-mode.txt or set per run with the --review flag.

What happens if no QA plan exists for the sprint?

The skill warns that the sprint cannot pass the Production to Polish gate without a QA plan and prompts you to run the qa-plan skill first. If you skip, a warning block is added to the sprint plan noting that QA sign-off will be blocked.