map-systems

To map dependencies and prioritize systems for a game design document, you decompose your game concept into explicit and inferred gameplay systems, build a dependency graph to flag bottlenecks, and assign priority tiers to establish a design order.

Systems decomposition in game design extracts explicit systems from a game concept, infers implicit supporting systems, and iterates with user approval until the gameplay set is complete and ready for dependency mapping.

Yes, you can use workflow orchestration to generate a systems index by reading your game concept documents, performing user-gated enumeration to extract systems, and writing the final catalog to design/gdd/systems-index.md.

You identify circular dependencies and bottlenecks in gameplay systems by building a layered dependency graph during mapping, which validates system ordering and flags structural issues for user review before finalizing the design.

Yes, systems decomposition requires director gate approvals, respecting review-mode settings to validate enumeration, dependencies, priorities, and explicit final approval before writing the resulting systems index file.

The best way to prepare a game concept for handoff to individual system GDD authoring is to determine a prioritized design order for all systems and update session state, ensuring downstream design tasks have a clear index.