Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ganyuanran/recording-architecture-decisions
Use when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture decision, decision log, or baseline sync after architecture-changing work.
Passed 19 of 22 test cases with the skill, and 8 of 22 without it.
and 20 more in the full report
13 fixed6 passed either way1 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our team lead proposed switching our message broker from RabbitMQ to Apache Kafka next quarter, but no implementation work has been done and no final agreement was reached. Please assess this proposed change against our decision recording standards and outline the evaluation breakdown.
| Checked | Without skill | With skill |
|---|---|---|
| Classifies the retro memory filter as unexecuted idea | Missed | Passed |
| Recommends an ADR action of skip | Missed | Passed |
The instructions your model reads when the skill loads.
Record durable architecture decisions without losing the current-state baseline closure. An ADR records why a decision was made; a baseline records what the architecture is after that decision.
This skill is a lazy, task-specific workflow. It does not replace
verification-before-completion, does not grant completion authority, and does
not make authoritative GateDecision or PolicySnapshot outputs.
Before deciding or writing, read the smallest relevant excerpts from:
docs/adr/ADR-CREATION-GATE.mddocs/current/AEGIS_ADR_AUTO_BACKFILL.mdFor Aegis repository changes, use this repository's docs/adr/ and
docs/current/ authority order. For target projects with their own ADR system,
respect that project owner instead of duplicating the same decision into
docs/aegis/adr/.
Use this skill when the user asks to:
Do not use it for simple wording edits, ordinary README cleanup, tests-only coverage improvements, low-risk single-file changes, or bug fixes that only restore the existing baseline.
test cases passed, vs 8 / 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.