adr

Create Architecture Decision Records with context, reasoning, alternatives, and consequences.

1|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/hypeJunction/ai-assistant-starter --skill adr-hypejunction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/hypeJunction/ai-assistant-starter/tree/main/skills/adr
Command: npx skills add https://github.com/hypeJunction/ai-assistant-starter --skill adr-hypejunction

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps capture and document significant technical decisions made during a project, ensuring that the reasoning, context, and alternatives considered are preserved for future reference.

Core Features & Use Cases

  • Record Architecture Decisions: Create formal Architecture Decision Records (ADRs) for key technical choices.
  • Document Context and Rationale: Capture the 'why' behind decisions, including alternatives considered and their consequences.
  • Use Case: When deciding on a new state management library for a web application, use this Skill to document the chosen library, why it was selected over others (like Redux or Zustand), and the expected impact on the project.

Quick Start

Use the adr skill to capture an architecture decision for the new API authentication strategy.

Frequently Asked Questions about adr

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

FAQPage Schema
How do I document technical decisions and architecture rationale for my project?

You can document technical decisions by capturing Architecture Decision Records (ADRs) that preserve the context, reasoning, alternatives considered, and consequences of significant technical choices. This ensures the rationale behind architecture decisions is saved for future reference.

What is an Architecture Decision Record and when should I create one?

An Architecture Decision Record (ADR) is a formal document capturing significant technical decisions, including the context, alternatives, and consequences. You should create an ADR when making key technical choices, such as selecting a new state management library or API authentication strategy.

How do I manage changes and supersede existing architecture decisions?

You can manage changes by superseding existing Architecture Decision Records and linking related decisions within your project. This functionality supports updating technical decisions over time while maintaining the historical context of previous architecture choices.

Where are architecture decision records stored in my project directory?

Architecture Decision Records are stored and linked within your project's `.ai-project/decisions/` directory. This centralized location ensures technical decisions and their accompanying rationale remain accessible directly alongside your project files.

Can I document alternatives and consequences when recording a technical decision?

Yes, recording a technical decision allows you to capture the alternatives considered and their expected consequences. For example, you can document why a specific state management library was selected over others and its anticipated impact on the project.