What problem does it solve? Planning a game development sprint requires pulling context from milestones, backlogs, risk registers, and prior velocity, then keeping the plan and its machine-readable status file in sync. This Skill automates that process and enforces quality gates before anything is written to disk. ## Core Features & Use Cases - Sprint Generation and Updates: Creates new sprint plans with capacity buffers, prioritized task tables (Must/Should/Nice to Have), carryover, and risk sections, or updates existing plans without resetting story statuses. - Status Reporting: Produces burndown-style status reports showing completed, in-progress, blocked, and at-risk tasks. - Quality Gates: Runs a producer feasibility review and a QA plan check before writing, with configurable review modes (full, lean, solo) stored in production/review-mode.txt. - Use Case: A solo game developer starting Sprint 3 runs the skill, which reads the current milestone and previous sprint velocity, drafts a realistic plan, flags missing QA coverage, and writes both sprint-3.md and sprint-status.yaml after approval. ## Quick Start Ask the AI to create a new sprint plan for the current milestone using the sprint-plan skill and confirm the write when prompted.
