Capture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.
SkillScore95Maintained
Automatic
◆Doc Ops pack
Last verified 8/22/2026
What it changes
Passed 21 of 22 test cases with the skill, and 12 of 22 without it.
Without skill55%
With skill95%
Checks it passed that the model alone missed
The draft includes the section header ## Consequences.
The draft includes the section header ## Alternatives Considered.
The sub-headings under Consequences are Positive, Negative, and Risks.
and 10 more in the full report
9 fixed12 passed either way1 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+63%
Agent turns
0%
Response time
-42%
Model gemini-3.6-flashMeasured 8/22/2026v621 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
In the lightweight ADR format, what exact three sub-headings must appear under the `## Consequences` section?
What was checked, without and with the skill
Checked
Without skill
With skill
The sub-headings under Consequences are Positive, Negative, and Risks.
Missed
Passed
case-22 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md180 linessingle file
Architecture Decision Records
Capture architectural decisions as they happen during coding sessions. Instead of decisions living only in Slack threads, PR comments, or someone's memory, this skill produces structured ADR documents that live alongside the code.
When to Activate
User explicitly says "let's record this decision" or "ADR this"
User chooses between significant alternatives (framework, library, pattern, database, API design)
User says "we decided to..." or "the reason we're doing X instead of Y is..."
User asks "why did we choose X?" (read existing ADRs)
During planning phases when architectural trade-offs are discussed
ADR Format
Use the lightweight ADR format proposed by Michael Nygard, adapted for AI-assisted development:
# ADR-NNNN: [Decision Title]
**Date**: YYYY-MM-DD
**Status**: proposed | accepted | deprecated | superseded by ADR-NNNN
**Deciders**: [who was involved]
## Context
What is the issue that we're seeing that is motivating this decision or change?
[2-5 sentences describing the situation, constraints, and forces at play]
## Decision
What is the change that we're proposing and/or doing?
[1-3 sentences stating the decision clearly]
## Alternatives Considered
### Alternative 1: [Name]
- **Pros**: [benefits]
- **Cons**: [drawbacks]