design-system

To write a game design document for a single system without losing context, use a guided workflow that reads repository files, respects cross-system facts, and drafts sections incrementally. This approach gathers engine references and dependency GDDs before generating content.

The best way to retrofit an existing GDD with missing sections is using a retrofit mode that detects placeholders and fills gaps without overwriting existing content. This preserves your current design decisions while completing the document structure.

Yes, you can use specialist agents like art director and QA lead when authoring systems design documents. The workflow mandates delegation to specialist agents for Player Fantasy, Formulas, Edge Cases, Art/Audio, and QA validation depending on the section.

Yes, the GDD authoring process checks for entity registry conflicts. It performs registry conflict checks during the section-by-section writing flow to ensure new system designs do not duplicate or contradict existing repository facts.

A system game design document includes Overview, Detailed Design, Formulas, Edge Cases, Dependencies, Tuning Knobs, and Acceptance Criteria sections. These sections are drafted incrementally with immediate approval required before writing to the file.

To coordinate a creative director review for a system GDD, the workflow uses Creative Director gating for full reviews. This ensures that all specialist agent contributions and incremental file writes are validated before final approval.