architecture-decision

Creates and validates Architecture Decision Records for game development projects.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/sumilee-pcu/game2026 --skill architecture-decision-sumilee-pcu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/sumilee-pcu/game2026/tree/main/.claude/skills/architecture-decision
Command: npx skills add https://github.com/sumilee-pcu/game2026 --skill architecture-decision-sumilee-pcu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent or undocumented technical decision-making, ensuring that every major architectural choice is recorded, reviewed, and aligned with engine constraints.

Core Features & Use Cases

  • ADR Lifecycle Management: Automates the creation, retrofitting, and validation of Architecture Decision Records (ADRs).
  • Engine-Aware Validation: Cross-references decisions against engine-specific documentation, breaking changes, and deprecated APIs to prevent technical debt.
  • Collaborative Review: Integrates with Technical Directors and Engine Specialists to ensure architectural coherence and system-wide consistency.

Quick Start

Invoke the architecture-decision skill with a short title to begin documenting a new technical choice.

Frequently Asked Questions about architecture-decision

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

FAQPage Schema
What is the best way to standardize Architecture Decision Records across multiple projects?

Engine-aware validation cross-references technical decisions against engine-specific documentation, identifying breaking changes and deprecated APIs to prevent architectural drift and technical debt.

Can I check if a technical decision aligns with my engine's deprecated APIs?

Engine-aware validation cross-references technical decisions against engine-specific documentation, identifying breaking changes and deprecated APIs to prevent architectural drift and technical debt.

When should I not use an automated ADR workflow for technical decision-making?

Automated ADR workflows are not ideal for minor, reversible code changes or when engine documentation is unavailable, as the validation gates require clear architectural constraints to function effectively.

How do I retrofit undocumented architectural choices into a structured repository?

Retrofitting undocumented choices involves using ADR lifecycle management to reconstruct past decisions, validating them against current engine constraints and integrating them into the structured repository.