design-system

Guided CDD authoring orchestrates module drafting by reading existing design docs and module indexes, walking through each section collaboratively while checking dependencies, and writing incrementally with explicit approvals. It aligns decisions with existing constraints before making auditable file edits.

Incremental design documentation drafting loads dependency CDDs and registry data to tailor sections for your domain. It prompts for decisions per section and applies controlled edits, ensuring safe changes by requiring explicit user approval before writing skeleton structures or content.

Yes, guided CDD authoring supports both game-oriented and generic product domains. It maintains domain-specific section names and structures while gathering context from design docs to align with the specific constraints of your game or product module.

CDD governance handles dependency checks by loading referenced dependency CDDs during the collaborative walkthrough. It cross-references these dependencies against the current module's design decisions, ensuring alignment before prompting for explicit user approval to write sections.

Existing design docs, module indexes, and registries are read by the CDD authoring process to gather context and tailor sections. While it uses these inputs to align decisions with current constraints, the workflow can also generate skeletons and prompt for decisions directly.

Explicit approval before writing to file ensures safe, auditable changes during CDD authoring. The controlled edit mechanism prevents unintended modifications by requiring user confirmation for each incremental section write, maintaining governance over the module documentation workflow.