adr

Create Architecture Decision Records as markdown files with context and rationale.

9|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/0xrafasec/ai-workflow --skill adr-0xrafasec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/0xrafasec/ai-workflow/tree/main/skills/adr
Command: npx skills add https://github.com/0xrafasec/ai-workflow --skill adr-0xrafasec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill aids in creating Architecture Decision Records (ADRs) to systematically capture design decisions, reducing ambiguity and aiding knowledge transfer within a team.

Core Features & Use Cases

  • Structured ADRs: Guides users in creating ADRs with a clear format, ensuring all relevant information is included.
  • Decision Documentation: Helps to document the context, options considered, and the rationale behind design choices.
  • Use Case: Use this Skill to capture a decision about an architectural change in your project, ensuring it's well-documented and easily accessible for future reference.

Quick Start

Create an Architecture Decision Record for a new feature with the command: /adr "Feature ADR: Implement New API Endpoints."

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 why do I need one for my software project?

An Architecture Decision Record (ADR) systematically captures design decisions, including context, options, and rationale, to reduce ambiguity and aid knowledge transfer within your software development team.

How do I document software architecture decisions using a structured format?

You can document architecture decisions by providing the decision details as input, which the skill structures into a markdown file covering context, options considered, and the rationale behind the chosen solution.

Can I generate an ADR for implementing new API endpoints in markdown?

Yes, you can generate a markdown ADR for new API endpoints by providing the specific feature details, which produces a structured document for future reference and team alignment.

What should be included in architecture decision documentation to ensure clarity?

Architecture decision documentation should include the context of the decision, the options considered, and the rationale behind the chosen solution to ensure structured and precise records.

When should I create an ADR instead of general design documentation?

You should create an ADR when you need to capture a specific architectural change or design choice, ensuring the decision is well-documented and easily accessible for future reference.