Game Sprint Plan
Builds a sprint plan for a team or solo developer: one pillar-aligned goal, day-sized tasks that each end in a check, dependencies, capacity with buffer, AI-agent estimates with review budgets and vibe-debt paydown, written to production/sprints/. Not for whole-project scope (use game-scope-check).
Install
/plugin marketplace add AlterLab-IEU/AlterLab_GameForgeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add AlterLab-IEU/AlterLab_GameForge --skill game-sprint-plangit clone --depth 1 https://github.com/AlterLab-IEU/AlterLab_GameForge.git /tmp/AlterLab_GameForge
mkdir -p ~/.claude/skills
cp -r /tmp/AlterLab_GameForge/skills/workflows/game-sprint-plan ~/.claude/skills/game-sprint-planPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# AlterLab GameForge -- Sprint Planning Game sprints fail for different reasons than software sprints. A business-app team struggles with unclear requirements; a game team struggles with cross-discipline dependencies and the unpredictability of fun. You can build an inventory system exactly to spec and discover in the playtest that it makes the game worse. So a game sprint plans discovery time (spikes, feel passes, playtests) as real work, not as leftovers. There is a newer failure mode. With Claude Code or a similar agent, code arrives fast, and it is easy to plan a sprint as if generation were the whole job. It is not. Someone still has to run the checks, read the diff, play the change and notice what the agent added that nobody asked for. This workflow budgets that verification on every task, and reserves capacity to pay down the "vibe debt" that accumulates when agent-written code is accepted faster than it is understood. The output is a sprint plan file in `production/sprints/` that a team, a solo developer, or a coding agent working from task cards can execute against. ## When to Use / When Not To Use before a new sprint, when a solo developer wants to structure the next one or two weeks, right after a retrospective, when a milestone needs decomposing, or when design work from `game-gdd-author` or `game-design-review` must become executable tasks. | Instead of this skill... | Use | |---|---|
Details
- Skill name
game-sprint-plan- Repository
- AlterLab-IEU/AlterLab_GameForge
- Path
skills/workflows/game-sprint-plan/SKILL.md- License
- MIT
- Repo updated
- 6 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Game Sprint Plan skill do?
Builds a sprint plan for a team or solo developer: one pillar-aligned goal, day-sized tasks that each end in a check, dependencies, capacity with buffer, AI-agent estimates with review budgets and vibe-debt paydown, written to production/sprints/. Not for whole-project scope (use game-scope-check).
How do I install the Game Sprint Plan skill?
Claude Code plugin: /plugin marketplace add AlterLab-IEU/AlterLab_GameForge. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Game Sprint Plan popular?
It lives in AlterLab-IEU/AlterLab_GameForge, which has 57 GitHub stars and 6 forks, and is included in 1 curated skill list.
Related skills
Game Accessibility Specialist
57AlterLab-IEU/AlterLab_GameForge
Accessibility Specialist (Kael Oduya). Designs motor, visual, auditory and cognitive accommodations, runs accessibility audits, scopes the European Accessibility Act, CVAA and Game Accessibility Guidelines, and maps fixes to Godot, Unity, Unreal or web. Use for "accessibility audit", "EAA", "colorblind", "subtitles", "remapping". Not for general UX flows (use game-ux-designer).
Game AI Assets
57AlterLab-IEU/AlterLab_GameForge
Runs an AI-assisted asset pipeline for models, sprites, textures, audio and voice: generate vs make vs buy, license-first tool choice, style lock, engine post-processing, and a per-asset provenance log for Steam, itch.io and EU AI Act disclosures. Use for "generate a sprite with AI", "ElevenLabs", "can I ship this AI asset". Not for defining art style (use game-art-director).
Game Analytics Setup
57AlterLab-IEU/AlterLab_GameForge
Sets up privacy-first game analytics: question-driven event taxonomies, consent-gated telemetry (GDPR, COPPA, ATT), engine and web SDK choice, KPI definitions, dashboards, A/B tests, and AI feedback summaries validated against real data. Use for "analytics", "telemetry", "KPIs", "retention", "funnel", "A/B test". Not for balance tuning (use game-balance-check).
Game Start
57AlterLab-IEU/AlterLab_GameForge
Sets up a game project for GameForge: detects engine and project state, writes .gameforge/project.json and session state, merges the engine starter CLAUDE.md, configures Git and Git LFS, and connects coding agents to the engine (MCP, llms.txt). Use for "start a new game", "set up my project", "initialize GameForge". Not for finding an idea (use game-brainstorm).
Game Scope Check
57AlterLab-IEU/AlterLab_GameForge
Checks scope against time and capacity: feature inventory, MoSCoW with effort caps, impact and risk scores, buffer math, scope-creep signals and a cut list, with velocity calibrated for AI-agent work and vibe debt counted as risk. Use for "scope creep", "can we fit this", "what should we cut", "are we on track". Not for sprint task planning (use game-sprint-plan).
Game Team Orchestrator
57AlterLab-IEU/AlterLab_GameForge
Runs the GameForge studio as a team: briefs studio subagents in parallel or in sequence, synthesizes their reports, routes conflicts by the agent hierarchy, and runs resumable named pipelines (new project, sprint, design iteration, release). Not for single-domain questions (use game-help).
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.