skills.rest
easonlao
easonlaoCOMMUNITY
Explore all skills by this author →
GitHub

architecture-decision

Generate Architecture Decision Records with engine compatibility and dependencies.

Updated Apr 25, 2026
Search Tags:#adr#godot#architecture decision records#engine compatibility#gdd sync#technical director review#retrofit documentation
One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill architecture-decision-easonlao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/architecture-decision
Command: npx skills add https://github.com/easonlao/jiazi-game --skill architecture-decision-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams capture and standardize major technical decisions by producing an Architecture Decision Record (ADR) with context, engine compatibility, dependencies, and consequences.

Core Features & Use Cases

  • Engine-aware ADR authoring: Loads engine version and domain-specific references (modules, breaking changes, deprecated APIs) and surfaces knowledge-gap warnings for higher-risk post-cutoff changes.
  • Conflict-safe collaboration: Checks the architecture registry for locked stances and blocks drafting if the proposed decision contradicts established interface contracts or forbidden patterns.
  • Retrofit without overwriting: In retrofit mode, reads an existing ADR, detects which required sections are missing, and appends only the absent sections while never modifying existing content.
  • End-to-end workflow with validation gates: Guides users through assumption confirmation, drafts the ADR, triggers engine specialist and technical director reviews (based on review mode), performs GDD sync checks, and optionally updates the architecture registry.

Quick Start

Run architecture-decision with a short ADR title to draft a new architecture decision record for your project, or run it in retrofit mode to append any missing required sections to an existing ADR file.

Frequently Asked Questions about architecture-decision

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

FAQPage Schema
How do I write an Architecture Decision Record that accounts for engine version compatibility?▼

To draft an Architecture Decision Record with engine compatibility, you need a tool that loads engine version references and surfaces breaking changes or deprecated APIs. This ensures your ADR captures version-specific risks and dependencies before finalizing the technical decision.

Can I append missing sections to an existing ADR without overwriting the original content?▼

You can safely retrofit an existing ADR by using a dedicated mode that detects missing required sections and appends only those absent parts. This preserves your original content while ensuring the document meets full architectural compliance standards.

What is an architecture registry and how does it prevent conflicts in ADRs?▼

An architecture registry stores locked technical stances and forbidden patterns for a project. By checking this registry before drafting, you can block proposals that contradict established interface contracts, ensuring new Architecture Decision Records remain consistent with the system.

How do I keep Architecture Decision Records synchronized with a Game Design Document?▼

To keep Architecture Decision Records synchronized with a Game Design Document, you need an automated GDD naming sync check. This validation gate verifies that technical decisions and design specifications share consistent naming conventions during the review process.

Does the ADR workflow support automated technical director reviews?▼

The ADR workflow supports automated technical director reviews through configurable review modes. After drafting, the process triggers engine specialist and technical director evaluations, validating the decision against domain rules before updating the architecture registry.

When should I use a formal ADR workflow for game engine architecture decisions?▼

You should use a formal ADR workflow for game engine architecture decisions when facing post-cutoff changes or domain-specific risks. It validates engine-reference context and enforces constraints, preventing undocumented breaking changes in complex software projects.

Related Skills

Explore More Software Engineering Skills→
striderZAstriderZA
72

architecture-decision

Create Architecture Decision Records with context, alternatives, and consequences.

Community
Advanced
polsegupolsegu

architecture-decision

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

Community
Advanced
DarkMonkDevDarkMonkDev
1

phase-1-validator

Validates requirements-phase documents against quality gates and structured section checks.

Community
Intermediate
XGanQAQXGanQAQ
1

architecture-decision

Creates ADRs with context, alternatives, and consequences for technical decisions.

Community
Advanced