architecture-decision

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

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LordKuper/agentic-game-studio --skill architecture-decision-lordkuper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/LordKuper/agentic-game-studio/tree/main/.claude/skills/architecture-decision
Command: npx skills add https://github.com/LordKuper/agentic-game-studio --skill architecture-decision-lordkuper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions shape long-term maintainability. This ADR Skill helps teams document significant technical decisions, their context, the considered alternatives, and consequences to ensure traceability and governance across the project.

Core Features & Use Cases

  • Create Architecture Decision Records (ADRs) for major technical choices.
  • Provide context, alternatives, and consequences to inform future work and reviews.
  • Link ADRs to related GDDs and existing ADRs to maintain traceability.

Quick Start

Provide a short ADR title to begin documenting a key architectural decision.

Frequently Asked Questions about architecture-decision

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

FAQPage Schema
What is an architecture decision record and why do I need one?

An architecture decision record (ADR) captures a significant technical decision's problem, context, alternatives, and consequences to ensure long-term maintainability, traceability, and governance across your project.

How do I document a major software architecture choice?

To document software architecture choices, provide a short ADR title to trigger the workflow, which then coordinates inputs, checks required sections, and outputs a consistent draft recording status and dependencies.

How does an ADR link to existing architecture documentation for traceability?

For traceability, the ADR process associates your new decision record with related Game Design Documents (GDDs) and existing ADRs, maintaining governance across the engineering workflow.

What sections are required when creating an architecture decision record?

Creating an architecture decision record requires sections for the problem, context, considered alternatives, and consequences, while the coordinating workflow checks for these required fields before outputting a ready-to-write draft.

Can I track decision dependencies and status within engineering workflows?

Yes, the ADR output enforces a consistent format and explicitly records metadata including the decision's current status and dependencies, integrating directly into your engineering workflow for governance.