Agent Decision Record
- 42 repo stars
- Updated July 23, 2026
- me2resh/agent-decision-record
agent-decision-record is a Claude Code plugin marketplace that enforces Agent Decision Records (AgDR) documenting AI agent technical choices with required metadata in docs/agdr/.
About
agent-decision-record is a Claude Code marketplace plugin implementing Agent Decision Records (AgDR), an ADR-inspired standard for documenting technical decisions made by AI agents. When agents choose libraries, patterns, or architecture, AgDR requires structured markdown in docs/agdr/ with six required metadata fields: id, timestamp, agent, model, trigger, and status, plus a Y-statement summary and options table. Install via /plugin marketplace add me2resh/agent-decision-record and invoke /agent-decision-record:decide. Integrations ship for Claude Code, Codex, Cursor, GitHub Copilot, Windsurf, system prompts, and git pre-commit hooks. Developers reach for it when agent-made decisions are invisible across sessions, unauditable in PRs, or lost during onboarding. Version 1.1.0 under CC BY 4.0.
- /agent-decision-record:decide creates structured AgDR markdown in docs/agdr/
- 6 required metadata fields: id, timestamp, agent, model, trigger, status
- Y-statement one-line summary plus options-considered comparison table
- integrations for Claude Code, Codex, Cursor, Copilot, Windsurf, git hooks
- extends ADR format with real-time agent decision triggers
Agent Decision Record by the numbers
- Data as of Jul 24, 2026 (Skillselion catalog sync)
/plugin marketplace add me2resh/agent-decision-recordAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| repo stars | ★ 42 |
|---|---|
| Last updated | July 23, 2026 |
| Repository | me2resh/agent-decision-record ↗ |
How do you document AI agent technical decisions in code?
Run /agent-decision-record:decide, generate AgDR markdown in docs/agdr/ with options table and Y-statement for library or architecture choices
Who is it for?
Development teams using AI coding agents who need auditable, structured decision records with agent and model metadata living alongside the codebase.
Skip if: Skip agent-decision-record when decisions are purely human-driven and already covered by a manual ADR process without agent-authored records.
What you get
Numbered AgDR markdown files in docs/agdr/ with context, options table, decision rationale, and agent metadata.
- docs/agdr/ markdown records
- Structured decision template
By the numbers
- Marketplace manifest version 1.1.0
- AgDR template requires 6 frontmatter fields: id, timestamp, agent, model, trigger, status
Plugins in this marketplace
1 plugin - install individually after you add the marketplace.
Recommended Marketplaces
How it compares
Use agent-decision-record for agent-authored decision traceability; use human ADR templates when architects document decisions outside agent sessions.
FAQ
What is an Agent Decision Record in Agent Decision Record?
An Agent Decision Record (AgDR) in Agent Decision Record is a structured markdown document capturing technical choices made by AI coding agents, stored in docs/agdr/ with required metadata including agent name, model identifier, timestamp, and decision status.
How does AgDR differ from a traditional ADR?
AgDR differs from ADR by requiring agent and model metadata, triggering on detected decision patterns during coding rather than design meetings, and supporting automated enforcement via Claude Code hooks and skills at version 1.1.0.
How do you create an AgDR with the plugin?
Developers create an AgDR by installing Agent Decision Record via /plugin marketplace add me2resh/Agent Decision Record and running /Agent Decision Record:decide with the decision topic, such as which testing framework to use.