design-system

To write a conflict-free game system design document, you need a guided authoring workflow that automatically gathers context from existing game docs, entity registries, and dependency GDDs before starting. This ensures your new system GDD aligns with pre-existing design decisions and avoids implementation rework.

You can update an incomplete game design document using a retrofit mode that fills gaps section by section without overwriting established content. This allows you to update legacy GDDs incrementally while preserving prior design work and maintaining consistency.

The best way to map dependencies during GDD authoring is to use built-in cross-system validation that checks dependency interfaces and registry values. This detects conflicts early and ensures your game system design is implementable across the entire project.

This GDD authoring workflow supports specialist review by coordinating with design, balance, and QA agents. It satisfies requirements for validated GDD output by ensuring mandatory section coverage and testability checks are completed before finalizing the document.

You need a structured authoring workflow for game system design when your project requires validated GDD output with mandatory section coverage and dependency interface mapping. It is essential for preventing design contradictions and missed alignment with core game pillars.

To start designing a new system for your game, invoke the design-system skill with the name of the specific game system you want to build. This initiates a guided, section-by-section GDD authoring workflow that validates your design against existing registries.