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."