docs-adr

Create Architecture Decision Records with Context, Decision, and Consequences sections.

Updated Mar 2, 2026

Search Tags:#architecture #decision making #documentation #software design #adr #technical decisions

Ready to run

npx skills add https://github.com/Genuineh/fus --skill docs-adr-genuineh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs-adr
Source: https://github.com/Genuineh/fus/tree/main/skills/docs-adr
Command: npx skills add https://github.com/Genuineh/fus --skill docs-adr-genuineh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of documenting significant technical decisions, ensuring clarity, consistency, and a traceable history of architectural choices.

Core Features & Use Cases

ADR Creation: Guides users through creating Architecture Decision Records with essential sections like Context, Decision, and Consequences.
Decision Tracking: Helps maintain a clear record of what was decided, why, and what alternatives were considered.
Use Case: When your team decides to adopt a new database technology, use this skill to formally document the decision, including the rationale and any alternatives that were rejected.

Quick Start

Use the docs-adr skill to create a new Architecture Decision Record for the decision to implement a new caching strategy.

Frequently Asked Questions about docs-adr

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

FAQPage Schema

How do I document architectural decisions for my software project?▼

Architecture Decision Records document significant technical choices by providing a structured template to capture context, decisions, alternatives, and consequences. This ensures clarity, consistency, and a traceable history for software architecture.

What should be included in an Architecture Decision Record?▼

An Architecture Decision Record should include essential sections like Context, Decision, and Consequences. It must document what was decided, the rationale behind it, and what alternatives were considered and rejected.

When do I need to create an ADR for technical decisions?▼

Create an Architecture Decision Record when your team makes significant software design choices, such as adopting a new database technology or implementing a new caching strategy, to formally document the rationale and alternatives.

How do I track software design alternatives that were rejected?▼

Architecture Decision Records track rejected software design alternatives by guiding you to document the context and consequences of each option. This maintains a clear record of what was decided and why alternatives were not chosen.

Does this ADR template require any specific dependencies to work?▼

Creating Architecture Decision Records with this template requires no external dependencies. You only need to adhere to the defined ADR template and metadata structure for tracking technical decisions.

What is the best way to maintain a traceable history of architectural choices?▼

The best way to maintain a traceable history of architectural choices is using Architecture Decision Records. They provide structured documentation of decisions, alternatives, and consequences, ensuring consistent tracking over time.