architecture-decision-records

Create and manage Architecture Decision Records with status lifecycle and numbering.

28|3|Updated Feb 22, 2026

Search Tags:#architecture #decision making #documentation #adr #governance #infrastructure

Ready to run

npx skills add https://github.com/oborchers/fractional-cto --skill architecture-decision-records-oborchers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/oborchers/fractional-cto/tree/main/cloud-foundation-principles/skills/architecture-decision-records
Command: npx skills add https://github.com/oborchers/fractional-cto --skill architecture-decision-records-oborchers

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of lost institutional knowledge and repeated debates by providing a standardized, version-controlled method for documenting significant infrastructure decisions.

Core Features & Use Cases

Standardized Documentation: Enforces a simple, consistent format (Context, Decision, Consequences) for Architecture Decision Records (ADRs).
Decision Governance: Tracks the lifecycle of decisions (Proposed, Accepted, Superseded, Deprecated) and ensures immutability.
Use Case: When deciding on a new cloud provider, use this Skill to create an ADR that captures the rationale, the chosen provider, and the implications, ensuring this critical decision is documented for future reference and onboarding.

Quick Start

Create a new Architecture Decision Record for the decision to adopt ADRs.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema

What are Architecture Decision Records and when do I need them for infrastructure choices?▼

Architecture Decision Records (ADRs) are standardized documents capturing significant infrastructure choices. You need them to prevent lost institutional knowledge and repeated debates by providing a version-controlled method for documenting architectural decisions.

How do I document the lifecycle status of an infrastructure decision?▼

You document the lifecycle status of an infrastructure decision by tracking it through Proposed, Accepted, Superseded, and Deprecated states. This governance process ensures decision immutability while maintaining a clear historical record of architectural changes.

What format should I use to document infrastructure decisions?▼

You should use a standardized format consisting of Context, Decision, and Consequences to document infrastructure decisions. This structure ensures clarity and consistency when recording the rationale, chosen solution, and implications of significant architectural choices.

How do I manage architectural governance and prevent rework in cloud environments?▼

You manage architectural governance and prevent rework by implementing version-controlled ADRs with enforced immutability and numbering. This standardized documentation method ensures clear tracking of foundational decisions and exemptions, reducing repeated debates in cloud infrastructure.

Does this approach to documenting decisions work for cloud provider migrations?▼

Yes, this approach works for cloud provider migrations by creating an ADR that captures the rationale, the chosen provider, and the implications. Documenting this critical decision ensures future reference and smooth onboarding for new team members.

When should I not use immutable decision records for infrastructure governance?▼

You should not use immutable decision records when a decision requires frequent, undocumented changes, as the immutability rule prevents altering accepted records. Instead, changes are managed by superseding prior decisions to maintain a strict governance lifecycle.