architecture-decision

Create Architecture Decision Records with engine compatibility validation and registry updates.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill architecture-decision-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/architecture-decision
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill architecture-decision-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes the creation and maintenance of Architecture Decision Records (ADRs) so that major technical choices are documented, engine-compatible, and traceable to GDD requirements and the architecture registry.

Core Features & Use Cases

  • Structured ADR authoring: Drafts complete ADRs with numbered filenames, Status, Date, Engine Compatibility, Alternatives, Consequences, and Validation Criteria.
  • Retrofit-safe edits & validation: Detects missing sections in existing ADRs, appends required fields without modifying existing content, and updates Date as needed.
  • Cross-checks and reviews: Loads engine reference docs, flags post-cutoff risks, spawns engine specialist and technical director reviews (per review mode), and proposes safe registry updates while surfacing GDD sync warnings.
  • Use Case: Choose between physics engines or networking approaches, generate ADR-0005 with engine checks, get specialist feedback, and append new stances to the architecture registry after approval.

Quick Start

Run the architecture-decision skill with a concise title like event-system-architecture to create a new ADR draft, validate engine compatibility, and prepare registry candidates.

Frequently Asked Questions about architecture-decision

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

FAQPage Schema
How do I document architecture decisions for engine compatibility?

To document architecture decisions for engine compatibility, create Architecture Decision Records that capture technical context, alternatives, and consequences, while validating choices against engine reference docs to ensure alignment.

How do I retrofit existing ADRs without overwriting previous content?

To retrofit existing ADRs without overwriting content, append missing required fields like Engine Compatibility and Validation Criteria to the records, updating only the Date field while preserving the original technical stances.

When do I need an Architecture Decision Record for my project?

You need an Architecture Decision Record when making significant technical choices like selecting physics engines or networking approaches, ensuring decisions are traceable to GDD requirements and the architecture registry.

Can I synchronize architecture registry updates with GDD requirements?

Yes, you can synchronize architecture registry updates with GDD requirements by proposing safe registry appends after ADR approval, while surfacing GDD sync warnings to catch any post-cutoff technical risks.

What is the best way to validate engine compatibility for technical design choices?

The best way to validate engine compatibility for technical design choices is to load engine reference docs, flag post-cutoff risks, and coordinate specialist and technical director reviews during the ADR process.