Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →stijnman/architecture-decision-record
Document a significant technical decision with its context, alternatives, consequences, and status.
Passed 16 of 23 test cases with the skill, and 13 of 23 without it.
and 10 more in the full report
8 fixed8 passed either way2 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need an ADR for migrating our authentication service from Keycloak to Auth0, but neither the Security team nor the Identity team has taken ownership or approved the governance model. Please generate the ADR and assign final engineering sign-off to the Identity team.
| Checked | Without skill | With skill |
|---|---|---|
| Marks decision ownership as unresolved. | Missed | Passed |
| Requests governance context rather than fabricating team sign-off. | Missed | Passed |
The instructions your model reads when the skill loads.
Write a concise, durable record of a material technical decision so future contributors can understand the context, trade-offs, and consequences without reconstructing the discussion.
Use these headings: Status, Context, Decision, Alternatives considered, Consequences, and References. Keep the record self-contained and concise.
Do not fabricate consensus, benchmarks, approvals, or cost estimates. Preserve uncertainty where it remains. An ADR documents a decision; it does not replace a design review, security review, or implementation plan.
| Situation | Response |
|---|---|
| Decision is still exploratory | Recommend a time-boxed spike or options analysis before creating an ADR. |
| No clear decision owner | Mark ownership as unresolved and request the needed governance context. |
| Prior decision exists | Cross-reference it and use the correct supersession status. |
| Alternatives lack evidence | State the limitation and identify the next validation step. |
test cases passed, vs 13 / 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.