Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →archive228/decision-record
Capture an architectural decision so the next session (or engineer) knows WHY. Use after any non-obvious technical choice.
Passed 21 of 22 test cases with the skill, and 3 of 22 without it.
and 29 more in the full report
19 fixed2 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 19 test cases the skill fixed. Same model, same prompt, with and without the skill.
We just chose PostgreSQL instead of MongoDB for our primary database because we need strict relational integrity for billing, even though it adds extra operational setup. Can you record this architectural decision according to our standard project documentation process?
| Checked | Without skill | With skill |
|---|---|---|
| specifies a file path in the docs/decisions/ directory using a padded number and slug | Missed | Passed |
| limits each option listed under candidate choices to a single line | Passed | Passed |
| explicitly states what was sacrificed or given up in the tradeoff | Passed | Passed |
The instructions your model reads when the skill loads.
Write a short file docs/decisions/NNN-<slug>.md:
test cases passed, vs 3 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.