design-review

Run a structured design review pass that scores the change against each principle in a fixed output grid: SOLID, DRY, KISS, SoC, YAGNI, cohesion/coupling, fail-fast, explicitness, and single source of truth. Each item gets a pass, pass-with-note, or fail verdict with a one-line justification.

A pre-done checklist covering simplicity, duplication, separation of concerns, cohesion, explicit behavior, single source of truth for business rules, typed actionable errors, no retries or try/catch bandages, no speculative abstractions, backward compatibility, and confidence at or above 0.9.

Skip it only for non-code outputs such as documentation, content, JQL, SQL reads, or plain explanations. All executable-code deliverables require the review block, or an explicit waiver line stating why it was waived.

A 5-item rubric assigns up to 0.20 each for passing tests, checked principles, no HIGH reviewer findings, passed domain gates, and no open assumptions. Scores are never rounded up, and 0.9 is the minimum gate for declaring work done.

Common anti-patterns include try/catch used to swallow errors, retry loops masking failures, generic Manager/Helper/Util naming, premature generic abstractions with one caller, unused configuration flags, and hidden side effects inside getters.