architecture-decision

Author and validate Architecture Decision Records against engine and GDD requirements.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill architecture-decision-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/architecture-decision
Command: npx skills add https://github.com/MichaelSolati/mkai --skill architecture-decision-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of incomplete, inconsistent, or conflicting Architecture Decision Records (ADRs) that fail to align with existing project architecture, engine constraints, and game design requirements, which can lead to technical debt and implementation errors.

Core Features & Use Cases

  • New ADR Authoring: Guides users through a structured, validated workflow to create fully compliant ADRs with all required sections, including engine compatibility checks and GDD requirement mapping.
  • Existing ADR Retrofitting: Automatically identifies missing mandatory sections in legacy ADRs and appends them without modifying existing content, ensuring all records meet current standards.
  • Architecture Conflict Detection: Validates proposed decisions against the project's architecture registry to surface contradictions with existing stances before work begins.
  • Use Case: A game development team documenting a new physics system decision can use this Skill to ensure the ADR aligns with existing state ownership rules, uses supported engine APIs, and maps to relevant GDD requirements.

Quick Start

Use the architecture-decision skill to document a new decision for the game's event system architecture, including all required validation and alignment checks.

Frequently Asked Questions about architecture-decision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an Architecture Decision Record that complies with engine constraints and game design requirements?

An Architecture Decision Record (ADR) documents major technical decisions by capturing context, decision drivers, and consequences, while validating against existing project architecture and engine constraints to prevent implementation inconsistencies.

How do I update legacy ADRs that are missing mandatory template sections?

To update legacy ADRs, the retrofitting process automatically identifies missing mandatory sections and appends them without modifying existing content, ensuring all records meet current architecture registry standards.

How does ADR conflict detection work with a project's architecture registry?

ADR conflict detection works by validating proposed decisions against the project's architecture registry to surface contradictions with existing stances, preventing conflicting technical decisions before implementation begins.

Can I use this for game development workflows that require GDD sync validation?

Yes, this supports game development workflows by performing GDD sync validation, ensuring architecture decisions map to relevant game design document requirements to prevent implementation inconsistencies.

What happens if my technical decision contradicts existing engine compatibility rules?

If a technical decision contradicts engine compatibility rules, the validation process surfaces these conflicts during authoring, ensuring the ADR aligns with supported engine APIs before any implementation work begins.