scope-feature-prioritizer

What problem does it solve?

This Skill addresses the challenge of feature bloat and scope creep in game development by providing a structured framework for prioritizing features based on design pillars, risk, and dependencies, ensuring that development efforts are focused on what truly matters.

Core Features & Use Cases

• MoSCoW Prioritization: Categorize features as Must, Should, Could, or Won't, aligned with design pillars.
• Feature Dependency Mapping: Visualize and understand the order in which features must be built.
• Risk-Weighted Prioritization: Prioritize features based on design, technical, market, or audience risk.
• Minimum Viable Game (MVG) Definition: Clearly define the smallest playable version of the game that delivers the core fantasy.
• Cut List Maintenance: Document features removed from scope with clear reasoning for future reference.
• Use Case: A game studio is overwhelmed with ideas for their new RPG. They use this Skill to identify the core features essential for the MVG, map out dependencies for the development roadmap, and decide which "nice-to-have" features can be deferred to later releases, preventing scope creep and ensuring a focused development cycle.

Quick Start

Use the scope-feature-prioritizer skill to define the Minimum Viable Game for the 'Project Chimera' RPG, focusing on the 'Exploration' and 'Combat' pillars.