What problem does it solve?
Game development teams often struggle to translate high-level game concepts into a clear, actionable list of required systems, leading to missed requirements, misaligned build order, and wasted development time on non-essential features early in production.
Core Features & Use Cases
- Full Systems Decomposition: Extracts both explicitly mentioned and implicitly required systems from game concept documents, with clear categorization and descriptions for each.
- Dependency Mapping: Identifies inter-system dependencies, detects circular dependencies, and sorts systems into layered build order to eliminate bottlenecks.
- Milestone-Based Prioritization: Assigns systems to priority tiers (MVP, Vertical Slice, Alpha, Full Vision) aligned with project milestones and core game pillars.
- Use Case: For a 90s F1 racing game like Overdrive, this skill would identify required systems including car physics, track rendering, lap timing, and audio, map that lap timing depends on physics data, and prioritize physics for the MVP milestone.
Quick Start
Invoke the map-systems skill with your game concept document to generate a complete systems index with dependency maps and prioritized design order.
