architecture-decision-records

Capture and maintain structured architectural decision records using a standard ADR template.

Updated Jun 22, 2026

Search Tags:#architecture #documentation #adr #best-practices #decision-making

Ready to run

npx skills add https://github.com/betaTrident/manta --skill architecture-decision-records-betatrident

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/betaTrident/manta/tree/main/.agents/skills/architecture-decision-records
Command: npx skills add https://github.com/betaTrident/manta --skill architecture-decision-records-betatrident

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of architectural knowledge loss by ensuring that critical design decisions are captured, contextualized, and stored alongside the codebase rather than being lost in ephemeral communication channels.

Core Features & Use Cases

Structured Documentation: Enforces a consistent ADR format including context, alternatives, and consequences.
Decision Tracking: Maintains an index of all project decisions for easy historical lookup.
Use Case: When a team debates whether to use a new state management library, this skill guides the developer through documenting the rationale and rejected alternatives, ensuring future team members understand the trade-offs made.

Quick Start

Ask the assistant to record a new architectural decision regarding the choice of a specific library or pattern for the current project.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema

How do I document architectural decisions to preserve design rationale in my codebase?▼

You can document architectural decisions by capturing structured records that include context, alternatives, and consequences directly within your project's directory structure. This ensures design rationale is preserved alongside the codebase for future team members.

What is an architectural decision record and when do I need one?▼

An architectural decision record is a structured document that captures technical trade-offs and design patterns requiring formal documentation. You need one when your team debates choices like adopting a new library and wants to prevent architectural knowledge loss.

How do I standardize architectural documentation format across a software development team?▼

You can standardize architectural documentation by enforcing a consistent ADR template across all recorded decisions and maintaining a historical index. This enforces a uniform format including context, alternatives, and consequences for every project decision.

Does this approach to decision tracking work without external dependencies?▼

Yes, this decision tracking approach requires no external dependencies. It relies solely on establishing a consistent directory structure within your codebase and adhering to the provided ADR template for all recorded decisions.

What is the best way to track rejected alternatives during software architecture debates?▼

The best way to track rejected alternatives is by documenting the rationale and trade-offs within a structured architectural decision record. This formalizes the decision-making process and ensures future team members understand why specific choices were rejected.

When should I not use formal architectural decision records?▼

You should avoid using formal architectural decision records for ephemeral communication or minor implementation details that do not involve significant technical trade-offs. They are specifically designed for formal documentation of major architectural choices and design patterns.