adr

Creates structured Architecture Decision Records with context, options, and consequences.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/LGugui/cerebro-template --skill adr-lgugui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/LGugui/cerebro-template/tree/main/.claude/skills/adr
Command: npx skills add https://github.com/LGugui/cerebro-template --skill adr-lgugui

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the creation and documentation of Architecture Decision Records (ADR), ensuring technical and architectural decisions are properly documented and tracked.

Core Features & Use Cases

  • ADR Creation: Facilitates the creation of ADRs with a structured template, capturing context, options, and consequences.
  • Vault-Level and Project-Level: Supports ADRs for both the entire vault and specific projects.
  • Documentation: Helps in maintaining a comprehensive record of decisions for future reference and analysis.

Quick Start

To create a new ADR, use the command: /adr

Frequently Asked Questions about adr

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

FAQPage Schema
How do I create an Architecture Decision Record for a software project?

You can create an Architecture Decision Record by triggering the automated generation process, which structures technical decisions into standardized sections capturing context, options, and consequences for future reference.

What is the best way to track software architecture decisions in technical documentation?

Tracking software architecture decisions is best handled by generating structured Architecture Decision Records that document context, available options, and consequences, ensuring technical choices are properly recorded for future analysis.

Can I document architectural decisions for both specific projects and my entire vault?

Yes, you can document architectural decisions at both the project level and the vault level, allowing you to maintain decision tracking structures for individual software components and broader architectural contexts.

What sections are included in a standard Architecture Decision Record template?

A standard Architecture Decision Record template includes structured sections for context, available options, and consequences, ensuring critical aspects of technical and architectural decisions are properly documented.

Do I need to provide specific inputs when generating technical documentation for architectural decisions?

Yes, you must provide specific decision details as input when generating technical documentation, allowing the system to automate creation of the Architecture Decision Record with the required context and consequences.