name: adr-logger description: Enforce Architectural Decision Records (ADR) logging for every task. Use when a user asks to create, update, or enforce ADRs, or when a workflow requires logging decisions in an ADR directory with daily files named adr_yyyy_mm_dd.md.

Adr Logger

Overview

Ensure an ADR directory exists and log a decision entry for every task in a daily ADR file named adr_yyyy_mm_dd.md.

Workflow

•Locate the project root in the current workspace.
•Ensure an ADR/ directory exists at the root; create it if missing.
•Use today's local date to select the file name: ADR/adr_yyyy_mm_dd.md.
•If the file exists, append a new entry; if not, create it with a header and the first entry.
•Each task must produce exactly one entry.

Entry Format

Use this structure for each entry (append under the file header if the file already exists):

code

## HH:MM - <task title>

### Context
- <what prompted the decision or change>

### Decision
- <what was decided or done>

### Consequences
- <impact, tradeoffs, or follow-up>

Guidelines:

•Use local time for HH:MM.
•Keep entries concise and task-specific.
•If a task has no architectural impact, log a brief "No architectural impact" in Consequences.