What problem does it solve? Indie game projects die from scope creep: feature lists that only grow, everything labeled "Must Have", and schedules with no buffer. This Skill replaces opinion-based scope debates with a structured, data-driven evaluation that produces a concrete cut list and a realistic timeline assessment. ## Core Features & Use Cases - Feature Inventory & MoSCoW Classification: Catalogs every planned, in-progress, and requested feature, then enforces the 60/25/15 Must/Should/Could effort allocation. - Feature Scoring Matrix: Scores each feature on Impact, Feasibility, and Risk with the formula (Impact x Feasibility) / Risk, producing Keep/Evaluate/Cut verdicts. - Timeline Sanity Check & Creep Detection: Computes net capacity versus planned work, reports buffer percentage with traffic-light status, and checks 10 scope creep warning signals. - Use Case: A solo developer three weeks from a demo milestone asks whether a new multiplayer idea fits. The workflow inventories all features, scores them, reveals a negative buffer, and recommends specific cuts plus a change freeze date. ## Quick Start Ask the assistant to run a scope check on your current feature list and milestone deadline to get a Scope Assessment Report with recommended cuts.
