architecture-decision

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in creating a structured Architecture Decision Record (ADR) to document and review significant technical decisions, ensuring clarity and traceability.

Core Features & Use Cases

  • ADR Creation: Document a technical decision, its context, alternatives, and consequences.
  • Review Modes: Supports full, lean, and solo review modes for flexibility.
  • Collaborative Decision Making: Guides a collaborative decision-making process with assumptions and dependencies.

Quick Start

Run the 'architecture-decision' skill to create a new ADR for a technical 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 when do I need one?

An Architecture Decision Record (ADR) documents a significant technical decision, capturing its context, alternatives, and consequences. You need an ADR to ensure clarity and traceability for system architecture changes.

How do I document technical decisions collaboratively using ADRs?

You can document technical decisions collaboratively by creating an ADR that guides the process, explicitly mapping out shared assumptions and dependencies to align your team on the technical requirements.

Can I use lean review modes for Architecture Decision Records?

Yes, you can use full, lean, or solo review modes when creating an Architecture Decision Record, allowing flexible documentation and validation of technical decisions based on your team's needs.

What context do I need to provide to create an Architecture Decision Record?

To create an Architecture Decision Record, you must provide knowledge of your system architecture and technical requirements, which the skill uses to document the decision's context and consequences.

What is the best way to maintain traceability for system architecture decisions?

The best way to maintain traceability is to create structured Architecture Decision Records that consistently document the context, alternatives, and consequences of each significant technical decision.

Why document alternatives and consequences in technical documentation?

Documenting alternatives and consequences in technical documentation ensures clarity and traceability, preventing knowledge loss by recording why a specific architecture decision was made over other options.