Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →avizmarlon/adr-spec-gate
ADR + Spec mandatory gate before any project or feature development. Architecture Decision Records and Software Design Docs enforce design clarity.
Passed 21 of 22 test cases with the skill, and 13 of 22 without it.
and 6 more in the full report
8 fixed13 passed either way1 still failing0 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 are adding a payment retry module to our backend repo. A developer wants to put `docs/retry-v1-spec-final.md` and `docs/retries/design-notes.txt`. What is the recommended default location and file structure for storing this feature specification and associated ADRs?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies locating the spec under docs/<feature-name>-spec.md or appending to a living specification file. | Missed | Passed |
| The response specifies numbering ADRs sequentially under docs/adr/ or using a single consolidated architecture-decisions.md file. | Passed | Passed |
The instructions your model reads when the skill loads.
Every new project and every non-trivial feature must pass through a dual-gate entry point before any code is written. This skill enforces the discipline of explicit design documentation before implementation.
The two required artifacts:
This gate prevents common failures: discovering broken assumptions mid-build, remaking decisions that were already made weeks earlier, and projects that only "exist" in chat and dissolve when the conversation ends.
A specification is a document that fully describes a feature or system at the design level, sufficient for another engineer (or AI agent) to continue implementation without asking the original author questions.
# <Feature/System Name> Specification
## Objective
What problem does this solve? (1-2 sentences)
## Scope
What is IN scope?
- Explicit feature list
- Boundaries
What is OUT of scope?
- What will NOT be built now (and why)
## Requirements
- User-visible requirements
- Non-functional requirements (performance, security, scale)
- Constraints (regulatory, technical, business)
test cases passed, vs 13 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.