documentation-adrs

Capture architecture decisions as ADR entries with YAML frontmatter.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/Saturate/agents --skill documentation-adrs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-adrs
Source: https://github.com/Saturate/agents/tree/main/skills/documentation-adrs
Command: npx skills add https://github.com/Saturate/agents --skill documentation-adrs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documents architecture decisions and rationale so teams can understand why a choice was made, preserving context beyond code.

Core Features & Use Cases

  • Lightweight ADR format with sections for context, decision, alternatives, and consequences
  • Stores decisions to memory provider for easy retrieval during future work
  • Useful for capturing decisions about dependencies, patterns, infrastructure, and security

Quick Start

Record an architecture decision as an ADR entry with the problem, decision, alternatives, and consequences.

Frequently Asked Questions about documentation-adrs

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

FAQPage Schema
How do I record architecture decisions for future reference?

To record architecture decisions, you capture the problem, final decision, alternatives, and consequences into an ADR entry with lightweight YAML frontmatter, which is then stored to a memory provider for easy retrieval during future software work.

What is an ADR and when do I need to document one?

An ADR is an Architecture Decision Record that documents why a specific choice was made. You need an ADR when making decisions about dependencies, patterns, infrastructure, and security to preserve context beyond the code for teams.

How do I store ADRs to a memory provider for my software project?

You store ADRs to a memory provider by applying a clear storage directive within the ADR entry. This directive ensures the lightweight YAML frontmatter and decision rationale are saved for quick retrieval during future work.

What sections do I need to include when writing architecture documentation?

When writing architecture documentation, you need to include a concise Decision section, an Alternatives considered section, and lightweight YAML frontmatter. This structure captures the context, decision, alternatives, and consequences effectively.

Can I use ADRs for infrastructure and security decisions across any software project?

Yes, you can use ADRs for infrastructure and security decisions across software projects. The format applies broadly to capturing decisions about dependencies and patterns, ensuring the rationale is preserved in memory regardless of the specific project.