adr-eligibility-gate

You need to write an architectural decision record only for genuine open questions with real trade-offs. This Skill evaluates candidate architectural choices using a 5-question checklist to ensure they warrant an ADR before drafting begins.

To prevent ADR over-production, you can apply a pre-draft gate to filter out non-decisions. This Skill evaluates architectural choices based on baseline enforcement, complexity, raised questions, and trade-offs before any draft is written.

Before creating an ADR draft, ask questions related to baseline enforcement, complexity, raised questions, and trade-offs. This Skill provides a 5-question checklist to evaluate the eligibility of a candidate architectural choice.

Yes, the ADR eligibility gate requires the `architecture-decisions` and `architecture-patterns` skills to provide context. It integrates as a pre-draft filter preceding the `architecture-decisions` skill to eliminate non-decisions.

You should not use an ADR when an architectural choice lacks real trade-offs or genuine open questions. This Skill acts as a constraint filter to prevent drafting records for non-decisions that do not meet baseline complexity requirements.