Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dicklesworthstone/architecture-decision-records
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation.
Passed 20 of 22 test cases with the skill, and 19 of 22 without it.
2 fixed18 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
In the standard MADR (Markdown Architectural Decision Records) template, how is the Consequences section structured to evaluate outcomes comprehensively?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies documenting Positive consequences. | Passed | Passed |
| Specifies documenting Negative consequences. | Passed | Passed |
| Specifies documenting Risks and mitigations. | Missed | Passed |
The instructions your model reads when the skill loads.
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
An Architecture Decision Record captures:
| Write ADR | Skip ADR |
|---|---|
| New framework adoption | Minor version upgrades |
| Database technology choice | Bug fixes |
| API design patterns | Implementation details |
| Security architecture | Routine maintenance |
| Integration patterns | Configuration changes |
Proposed → Accepted → Deprecated → Superseded
↓
Rejected
test cases passed, vs 19 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.