New ADR

Generate Architecture Decision Records with sequential numbering and related item links.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/beekeeper-lab/repomirrorkit --skill new-adr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: New ADR
Source: https://github.com/beekeeper-lab/repomirrorkit/tree/main/.claude/skills/new-adr
Command: npx skills add https://github.com/beekeeper-lab/repomirrorkit --skill new-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of Architecture Decision Records (ADRs), ensuring that significant architectural choices are consistently documented, discoverable, and justified.

Core Features & Use Cases

  • Structured ADR Creation: Guides users through capturing context, decision drivers, options, rationale, and consequences.
  • Automated Numbering: Assigns sequential, gapless ADR numbers.
  • Related Item Linking: Connects ADRs to relevant tasks or issues.
  • Use Case: When deciding on a new database technology, use this skill to formally record the decision, the options considered (e.g., PostgreSQL vs. MySQL), the rationale, and the expected impact.

Quick Start

Create a new Architecture Decision Record for the title "Use PostgreSQL for primary datastore" with the context "Our current relational database is nearing its scalability limits and we need a more robust solution.".

Frequently Asked Questions about New 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?

To document architectural decisions, you need an Architecture Decision Record (ADR) that captures the context, options with tradeoffs, chosen rationale, and consequences. This skill structures and automates that documentation process for you.

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

An Architecture Decision Record (ADR) is a formal document capturing significant software design choices. You should create one when making architectural decisions like selecting a database technology to ensure choices are justified and discoverable.

How do I create an ADR that links to related work items?

You create an ADR by providing a decision title and context, optionally including considered options and related items. The skill assigns a sequential number and writes the record to your specified directory with links to relevant tasks.

Can I use this to record technical debt and software design tradeoffs?

Yes, you can use this to record software design tradeoffs and document technical debt. By capturing considered options and rationale, the ADR provides a structured history of why specific architectural choices were made over alternatives.

What is the best way to manage ADR numbering for software documentation?

The best way to manage ADR numbering is through automated sequential assignment. This skill enforces ADR discipline by generating gapless sequential numbers for each new record, ensuring consistent and traceable architecture documentation.

Does this ADR tool require specific dependencies to document decision making?

No, this ADR tool requires no specific dependencies to document decision making. It operates independently to capture context, options, and rationale, writing the finalized architecture documentation directly to a directory you specify.