Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sentenz/adr
Creates and maintains Architecture Decision Records (ADRs) following a structured format with State, Context, Decision, Considered, Consequences, Implementation, and References sections. Supports single-option decisions, multi-option decisions within one decision scope, multiple complementary decisions, and deferred decisions.
Passed 20 of 23 test cases with the skill, and 15 of 23 without it.
and 8 more in the full report
7 fixed13 passed either way1 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to create an architecture record for adopting a central Git hooks manager across all development workflows. There are currently 15 existing records in `docs/decisions/`. What is the target repository file path and filename for this record?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies filename as 016-adr-git-hooks-manager.md without scope segment or trailing dash. | Missed | Passed |
| Places file in the docs/decisions directory. | Passed | Passed |
The instructions your model reads when the skill loads.
Instructions for AI agents on creating and maintaining Architecture Decision Records (ADRs) to document significant architectural and technical decisions within a project.
Traceability
ADRs provide a historical record of architectural decisions, enabling teams to understand why specific choices were made, reducing the risk of revisiting resolved problems.
Knowledge Sharing
Documenting decisions and their rationale helps onboard new team members quickly and ensures shared understanding across the organization.
Accountability
Clearly identifying authors, dates, and decision status creates ownership and transparency around architectural choices.
Informed Alternatives Review
Recording considered alternatives with their pros and cons enables future reviewers to evaluate whether circumstances have changed enough to revisit a decision.
Consequence Awareness
Explicitly documenting positive and negative consequences of a decision helps teams prepare mitigations and set realistic expectations.
test cases passed, vs 15 / 23 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.