map-systems

To decompose a product concept into modules, you read concept documents and design artifacts to enumerate modules, map dependency layers, and generate a prioritized design index for architecture planning.

The best way to plan early architecture is to map concept dependencies into layered modules and produce a prioritized design order. This highlights critical bottlenecks and generates a module index for planning and handoff.

You generate a module index with dependency layers by reading concept documents and design artifacts, decomposing the concept into modules, and mapping dependencies to output a prioritized design plan at module-index.md.

Yes, concept decomposition and dependency mapping applies to game design planning. It breaks down game concepts into modular components, maps dependencies, and generates a prioritized design index to guide implementation.

System decomposition does support optional assets directories. It reads concept documents and design artifacts while allowing you to include optional assets directories for references and artifacts during architecture planning.

You determine the recommended design order by mapping module dependencies to reveal layers and critical bottlenecks. This produces a prioritized design plan that guides the sequence of architecture and implementation tasks.