architecture-decision-records

Load canonical Architecture Decision Records guidance from the library.

3|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ldilov/harness-forge --skill architecture-decision-records-ldilov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/ldilov/harness-forge/tree/main/.agents/skills/architecture-decision-records
Command: npx skills add https://github.com/ldilov/harness-forge --skill architecture-decision-records-ldilov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auto-discovery access to the canonical Architecture Decision Records guidance stored in the library, enabling teams to quickly locate and load ADR resources without duplication.

Core Features & Use Cases

  • Auto-discovery of the canonical ADR guidance from the library.
  • Provides a wrapper surface to load deeper ADR guidance for architecture decisions.
  • Use case: a project team needs quick access to standardized ADR guidance before recording a decision.

Quick Start

Invoke the ADR wrapper to load the canonical Architecture Decision Records guidance from the library.

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 my project?

Architecture Decision Records provide durable documentation for architecture decisions across projects. Teams need ADRs to capture the context, decision, and consequences of significant architectural choices to maintain a consistent technical history.

How do I load canonical Architecture Decision Records guidance into my workflow?

You can load canonical Architecture Decision Records guidance by invoking the ADR wrapper, which provides auto-discovery access to standardized resources stored in the library without duplication.

Do I need any dependencies or specific setup to access ADR guidance from the library?

No specific dependencies are required to access ADR guidance from the library. The Skill operates independently to auto-discover and load the canonical SKILL.md along with validation materials.

What is the best way to standardize ADR documentation across multiple project teams?

The best way to standardize ADR documentation is using auto-discovery to load canonical guidance from a central library, ensuring all teams reference the same validation materials and provenance before recording decisions.

Are there limitations to using auto-discovery for architecture decision records?

Auto-discovery for architecture decision records focuses on loading the canonical SKILL.md and reference materials. It does not generate decision content itself, serving strictly as a guidance wrapper rather than an active documentation authoring tool.