architecture-decision

An Architecture Decision Record documents major technical decisions by capturing the context, alternatives, and consequences in a structured format. You can generate one by invoking the skill with a specific decision title.

Yes, you can update an existing Architecture Decision Record using retrofit mode. Retrofit mode analyzes existing records and automatically adds missing sections like context, alternatives, or consequences.

Yes, the Architecture Decision Record process supports collaborative review through multiple modes. You can select full, lean, or solo review modes to involve stakeholders and align decisions with architectural goals.

To create an aligned Architecture Decision Record, you need access to engine documentation and Game Design Documents (GDDs). The skill loads the engine environment to ensure technical decisions match architectural goals.

The best way to validate technical decisions is by generating an Architecture Decision Record. The process includes validation checks to ensure your chosen alternatives and consequences align with established architectural goals.

Use retrofit mode for an Architecture Decision Record when you have existing documentation that lacks structure. It updates records by adding missing sections, whereas standard creation builds a new ADR from scratch.