architecture-decision

Name: architecture-decision
Availability: InStock
Author: NuoYan

Document technical decisions as structured Architecture Decision Records with context and alternatives.

47|12|Updated Jun 14, 2026

Search Tags:#adr #technical design #system architecture #technical review #architecture decision record #engine compatibility #gdd traceability

Ready to run

npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill architecture-decision-nuoyanruoshui

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/architecture-decision
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill architecture-decision-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents important technical decisions from being lost, inconsistently implemented, or revisited without context by documenting them as structured Architecture Decision Records.

Core Features & Use Cases

ADR Authoring: Guides collaborative creation of ADRs covering context, constraints, requirements, decisions, alternatives, consequences, validation, and migration.
Architecture Validation: Checks engine compatibility, existing architectural stances, dependencies, GDD traceability, and strategic technical coherence.
Retrofit Support: Adds missing governance sections to existing ADRs without modifying their established content.
Use Case: Use it to document a Godot physics architecture choice, compare alternatives, validate engine-specific risks, obtain technical review, and register the resulting interface and ownership decisions.

Quick Start

Invoke the architecture-decision skill with a short decision title such as physics-engine-choice and an optional review mode.

Frequently Asked Questions about architecture-decision

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

FAQPage Schema

How do I document a system architecture decision as an Architecture Decision Record?▼

To document a system architecture decision, you create a structured ADR covering context, alternatives, consequences, and validation criteria. This prevents key technical choices from being lost or inconsistently implemented across your project lifecycle.

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

Validating engine compatibility requires checking your technical design against engine reference materials, existing architectural stances, and dependencies. This ensures the proposed system architecture maintains strategic technical coherence and avoids engine-specific risks.

How do I add governance sections to existing ADRs without changing their content?▼

You can retrofit existing ADRs by appending missing governance sections like validation criteria and ownership decisions without modifying their established content. This updates technical governance workflows while preserving the original architectural context.

When do I need an ADR for GDD-driven development?▼

You need an ADR for GDD-driven development when making significant technical choices that require GDD traceability and architectural consistency checks. This documents the decision context and validates engine-specific risks during system design.

Does this approach support technical review and architecture registry workflows?▼

Yes, the architecture decision process supports technical review workflows by validating engine compatibility and consistency, then registering the resulting interface and ownership decisions in architecture registries for durable technical governance.