adr-logger

Append structured Context, Decision, and Consequences entries to daily ADR files.

3|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/tomfordrumm/agent-skills --skill adr-logger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr-logger
Source: https://github.com/tomfordrumm/agent-skills/tree/main/adr-logger
Command: npx skills add https://github.com/tomfordrumm/agent-skills --skill adr-logger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents lost context by ensuring architectural decisions made during work are consistently recorded in an ADR directory, instead of being scattered across chat or ignored.

Core Features & Use Cases

  • Daily ADR logging: Appends exactly one decision entry per task into a daily file named ADR/adr_yyyy_mm_dd.md.
  • Consistent entry structure: Captures Context, Decision, and Consequences in a repeatable format suitable for later review.
  • Workflow enforcement: Creates the ADR directory when missing and uses local time to standardize timestamps for entries.

Use case: When you change an implementation approach while fixing a bug or selecting a design pattern, the skill ensures that the “why” and tradeoffs are preserved in the relevant daily ADR file for your team to audit later.

Quick Start

Ask your agent: "While completing this task, log the architectural decision to ADR/adr_yyyy_mm_dd.md with a single entry including Context, Decision, and Consequences."

Frequently Asked Questions about adr-logger

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

FAQPage Schema
How do I automatically log architectural decision records during software development?

To automatically log architectural decision records, you can use a skill that appends one structured entry per task into a daily ADR file. It automatically checks for or creates an ADR directory and uses local time for timestamping entries.

What is the standard format for capturing architectural decisions in daily files?

The standard format for capturing architectural decisions uses a daily file named adr_yyyy_mm_dd.md. Each entry must be structured with three sections: Context, Decision, and Consequences, ensuring consistent and reviewable records.

How do I prevent lost context when changing implementation approaches or selecting design patterns?

Preventing lost context requires logging architectural decisions in a dedicated ADR directory. By appending the rationale and tradeoffs for each task to a daily file, teams can audit the "why" behind implementation changes later.

What's the best way to enforce consistent ADR creation across every development task?

The best way to enforce consistent ADR creation is through workflow automation that captures decisions as you work. This approach standardizes timestamps using local time and ensures exactly one decision entry is appended per task.

Do I need to manually create an ADR directory before logging decision records?

No, you do not need to manually create an ADR directory. The logging process automatically checks for the directory and creates it when missing, ensuring the daily adr_yyyy_mm_dd.md files are always saved correctly.