Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
77
65%
Does it follow best practices?
Impact
99%
1.45xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/documentation-generation/skills/architecture-decision-records/SKILL.mdADR infrastructure setup and standard ADR authoring
Correct directory location
0%
100%
File naming convention
100%
100%
README index present
100%
100%
README index table
100%
100%
README creating instructions
100%
100%
README status definitions
0%
100%
Template file present
100%
100%
ADR status field
100%
100%
Decision Drivers section
62%
100%
Multiple options with pros/cons
100%
100%
Rationale section
100%
100%
Honest negative consequences
100%
100%
adr-tools usage
30%
100%
Related Decisions linked
0%
100%
RFC-style ADR for complex proposals
Summary section
100%
100%
Motivation section
100%
100%
Specific motivation items
100%
100%
Detailed Design section
83%
100%
Drawbacks section
62%
87%
Substantive drawbacks
75%
100%
Alternatives section
100%
100%
Unresolved Questions as checklist
12%
100%
Implementation Plan section
91%
100%
References section
0%
100%
ADR deprecation and supersession workflow
Original ADR not modified
100%
83%
New ADR created
100%
100%
New ADR file naming
100%
100%
Supersedes status format
33%
100%
Migration Plan present
0%
100%
Lessons Learned section
0%
100%
Negative consequences included
100%
100%
Old ADR status updated
100%
100%
README index updated
100%
100%
Context references original ADR
100%
100%
91fe43e
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.