architecture-decision

Document architectural decisions with context, constraints, and trade-offs.

3|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill architecture-decision-negentropy-laby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/architecture-decision
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill architecture-decision-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADR authoring helps teams capture significant technical decisions, context, alternatives, and consequences to promote alignment and traceability across the system.

Core Features & Use Cases

  • Guides collaborative decision making for software architecture through standardized ADRs.
  • Maps context, constraints, alternatives, and consequences to ensure traceable decisions.
  • Supports both game-domain and general product domains with domain-aware sections and references.

Quick Start

Invoke the ADR skill with a short title using /architecture-decision [title] to begin drafting the ADR.

Frequently Asked Questions about architecture-decision

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

FAQPage Schema
How do I document architecture trade-offs and decisions for a software system?▼

Document architecture trade-offs by mapping context, constraints, alternatives, and consequences into a standardized Architecture Decision Record. This ensures traceable decisions and stakeholder alignment across the system.

What is the best way to draft an ADR quickly for a game or general product domain?▼

Drafting an ADR quickly involves using domain-aware sections and references to guide stakeholders through alternative options and consequences. This supports both game and general product domains for robust documentation.

How do I write an ADR that captures context, constraints, and consequences?▼

Write an ADR by identifying the architectural decision, then mapping the system context, technical constraints, evaluated alternatives, and resulting consequences. This promotes alignment and traceability for technical decisions.

Do I need design docs and templates to generate an architecture decision record?▼

Yes, generating and validating an ADR draft requires access to design docs, ADR templates, and CDD references. These inputs ensure the architecture decision accurately reflects system constraints and trade-offs.

Can I use an ADR to guide collaborative decision making for software architecture?▼

Yes, ADRs guide collaborative decision making by documenting significant technical decisions and mapping alternatives. This structure helps stakeholders evaluate trade-offs and reach traceable alignment on architecture governance.

What should I include in an architecture decision record to ensure traceable decisions?▼

Include the system context, technical constraints, alternative options considered, and resulting consequences in your architecture decision record. This documentation ensures traceable decisions and promotes stakeholder alignment.