architecture-decisions

Capture and govern architectural decisions with a five-phase ADR process.

Updated Feb 24, 2026

Search Tags:#architecture #adr #governance #trade-offs #traceability #decision-record #phased-gates

Ready to run

npx skills add https://github.com/AymanKastali/pydentity --skill architecture-decisions-aymankastali

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decisions
Source: https://github.com/AymanKastali/pydentity/tree/main/.claude/skills/architecture-decisions
Command: npx skills add https://github.com/AymanKastali/pydentity --skill architecture-decisions-aymankastali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and govern architectural decisions to prevent knowledge loss and inconsistent design.

Core Features & Use Cases

Enforces a structured ADR process (Identification, Context, Options, Decision, Governance)
Guides teams to create clear, citable architectural decisions
Supports governance with cross-references, decision logs, and supersession tracking

Quick Start

Execute the ADR workflow to identify a decision, document context, compare options, finalize the rationale, and add it to the decision log.

Frequently Asked Questions about architecture-decisions

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

FAQPage Schema

What is an architectural decision record and when do I need one?▼

To document architectural decisions, follow a five-phase ADR workflow: identify the decision, document context, compare options, finalize the rationale, and add the record to an auditable decision log. This enforces clear, citable governance with cross-references and supersession tracking.

How do I track superseded architecture decisions and maintain traceability?▼

Yes, a structured ADR process applies to both system-wide architecture decisions and component-level choices. It enforces governance by applying mandatory phased gates to capture trade-offs and rationale regardless of the architectural scope.

What is the best way to govern architectural trade-offs across multiple teams?▼

The ADR process enforces governance by requiring mandatory phased gates across identification, context, options, decision, and governance phases. It prevents inconsistent design by capturing trade-offs in an auditable decision log with cross-references and supersession tracking.

Why does my team lose context on past architecture decisions over time?▼

Your team loses context on past architecture decisions because rationale is not captured and governed in an auditable log. Implementing a structured ADR process with cross-references preserves traceability and prevents knowledge loss across the software lifecycle.