game-producer

Provide your backlog, team capacity, and past velocity data. The producer proposes a committed scope with a 20% buffer, identifies risks, and outputs a sprint plan document with stretch goals and capacity breakdown.

A cut list is a pre-ranked list of every planned feature ordered by proximity to the game's core pillars. When scope pressure hits, features are cut from the bottom up without debate, protecting the schedule and the core vision.

It analyzes burndown data against trailing 3-sprint velocity, quantifies the gap, and presents options such as executing cut list items or adjusting the milestone date, with trade-offs for each option.

No. It explicitly routes creative decisions to a creative director role, technical decisions to a technical director, and design work to a designer. It only coordinates schedules, scope, risks, and resources.

It describes MCP integrations with GitHub for issue and milestone tracking, Notion for GDD and risk registers, Google Calendar for milestone scheduling, and Slack for team status updates.

Avoid it for creative vision, game mechanics design, narrative writing, or architecture decisions. It is scoped to production coordination: scheduling, scope management, risk tracking, and team communication.