adr-keeper

Create and maintain ADR files in docs/adrs with date-based filenames.

2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/jonmumm/skills --skill adr-keeper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr-keeper
Source: https://github.com/jonmumm/skills/tree/main/adr-keeper
Command: npx skills add https://github.com/jonmumm/skills --skill adr-keeper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architectural decisions often get lost in code history. ADR Keeper provides a structured, date-named record to justify why we chose a given direction and how it impacts the project over time.

Core Features & Use Cases

  • Create and maintain Architectural Decision Records in docs/adrs with date-based filenames.
  • Use an ADR template to capture Context, Decision, and Consequences, and keep a chronological index.
  • Reference existing ADR patterns to guide future decisions and on-boarding for new team members.

Quick Start

Create your first ADR using the template in references/adr-template.md and save it under docs/adrs with a YYYY-MM-DD naming format.

Frequently Asked Questions about adr-keeper

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

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

An architectural decision record (ADR) captures the why behind design choices like dependencies, patterns, and trade-offs. You need an ADR when recording a decision or maintaining architecture history to prevent context from getting lost in code history.

How do I create an ADR using a template?

To create an ADR, use the template in references to capture Context, Decision, and Consequences. Save the file under docs/adrs with a YYYY-MM-DD date-based filename, and update the chronological ADR index to maintain versioned tracking.

How do I organize architectural decision records across multiple projects?

Organize architectural decision records by placing ADR files in a dedicated docs/adrs directory within each project. Maintain a chronological index to track versioned decisions, ensuring architecture history and governance are documented consistently across teams.

What should be included in an ADR template for software architecture?

An ADR template for software architecture should include sections for Context, Decision, and Consequences. This structure justifies why a given direction was chosen and documents how the architectural trade-offs impact the project over time.

Can I use existing ADR patterns to guide future software architecture decisions?

Yes, you can reference existing ADR patterns to guide future software architecture decisions. Documenting dependencies and trade-offs in the ADR index helps onboard new team members and provides historical context for ongoing governance.

Does this approach to documentation work for teams maintaining architecture history?

This documentation approach works for teams by providing a structured, date-named record of architectural decisions. It places ADRs in docs/adrs with date-based filenames and updates the index, satisfying governance requirements for maintaining architecture history.