Install any skill in seconds. Free to start, no credit card required.
Get Started Free →a5c-ai/decision-documentation
Create Architecture Decision Records (ADRs) documenting significant technical choices with context, options, consequences, and sequential numbering.
Passed 18 of 22 test cases with the skill, and 0 of 22 without it.
and 21 more in the full report
18 fixed0 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
We just decided to switch our microservice communication from REST to gRPC to improve latency. Can you draft an architectural decision record capturing why we made this choice, the competing approaches we evaluated, and the expected tradeoffs?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies or creates the output file path under docs/decisions/ with a sequential numeric prefix | Missed | Passed |
| Includes headers for Title, Status, Context, Options, Decision, and Consequences | Missed | Passed |
| Sets Status to a valid state such as Proposed, Accepted, Deprecated, or Superseded | Passed | Passed |
The instructions your model reads when the skill loads.
ADRs are written to docs/decisions/ with sequential numbering (e.g., 0001-use-typescript.md).
Invoke via babysitter process: methodologies/rpikit/rpikit-decision
test cases passed, vs 0 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.