architecture-decision

Architecture decision records capture technical choices, context, and consequences for future reuse. This Skill guides ADR authoring with consistent sections, engine compatibility checks, and dependency tracking to ensure durable documentation.

Retrofit mode detects missing required sections in existing ADRs and adds only the absent content. It never modifies existing sections, preserving original rationale while bringing legacy records up to current completeness standards.

Engine-context verification loads engine reference material and flags post-cutoff knowledge risk during ADR authoring. When configured, it validates engine-specific correctness through specialist review to ensure technical decisions align with engine constraints.

GDD sync checks scan referenced game design documents before write approval to warn if names or interfaces would mismatch what the ADR introduces. This prevents architectural decisions from creating inconsistencies with established design specifications.

Architecture registry updates are optional and gated, requiring explicit approval before any changes are applied. The Skill proposes new stances and asks for confirmation, ensuring team consensus on registry modifications.

ADRs require YAML frontmatter-driven metadata to enforce section completeness and standardize documentation. This structured metadata ensures consistent capture of technical decisions, dependencies, and validation criteria across all records.