adr

Create and track Architecture Decision Records that gate implementation.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/javierhbr/agnostic-agent-loop --skill adr-javierhbr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/javierhbr/agnostic-agent-loop/tree/main/internal/skills/packs/sdd/adr
Command: npx skills add https://github.com/javierhbr/agnostic-agent-loop --skill adr-javierhbr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the chaos of AI-driven development by ensuring critical architectural decisions are documented, tracked, and resolved before implementation, preventing scope creep and ensuring alignment.

Core Features & Use Cases

  • ADR Creation & Management: Facilitates the drafting, linking, and resolution of Architecture Decision Records (ADRs).
  • Decision Gating: ADRs act as mandatory gates, blocking spec implementation until they are approved.
  • Scope Determination: Helps differentiate between Global (Platform Repo) and Local (Component Repo) ADRs.
  • Use Case: When a new feature requires a decision about how to handle cross-cutting concerns like authentication, use this Skill to create an ADR, get it reviewed, and ensure all dependent specs are updated upon its approval.

Quick Start

Use the adr skill to create a new ADR for an idempotency strategy decision.

Frequently Asked Questions about adr

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?

Architecture Decision Records (ADRs) are first-class artifacts that document, track, and resolve critical architectural choices to prevent scope creep. You need them when a new feature requires decisions about cross-cutting concerns like authentication or idempotency before implementation begins.

How do I create an Architecture Decision Record for an idempotency strategy?

You create an Architecture Decision Record by drafting the idempotency strategy decision, submitting it for review, and ensuring dependent specs are updated upon approval. The ADR acts as a mandatory gate that blocks spec implementation until the architectural decision is finalized.

Does decision gating block software implementation until ADRs are approved?

Yes, decision gating blocks spec implementation until Architecture Decision Records are approved. ADRs act as mandatory gates within the software development lifecycle to govern architectural choices and prevent unreviewed technical decisions from proceeding.

How do I differentiate between global and local Architecture Decision Records?

You differentiate by scope determination: Global ADRs belong in the Platform Repo, while Local ADRs reside in the Component Repo. This separation ensures architectural governance matches the impact level of the technical decision being tracked.

Why use ADRs to manage technical debt and governance in software engineering?

Using ADRs manages technical debt by ensuring architectural decisions are documented and resolved before implementation. This governance approach prevents the chaos of undocumented choices, ensuring alignment and blocking development progress until decisions are finalized.