enforces engineering-governance checks before code changes that may be unnecessary, risky, architectural, or scope-widening. use when the user asks whether to refactor, clean up, redesign, choose a next development step, review a proposed implementation, evaluate architectural consistency, review a pull request, or prevent development drift. do not use as the primary implementation skill for routine debugging, bug fixes, feature coding, or language-specific coding unless a no-op, minimal-diff, or architecture-conflict judgment is needed.
98
100%
Does it follow best practices?
Impact
96%
1.33xAverage score across 5 eval scenarios
Passed
No known issues
The platform team is considering a second service that writes directly to analytics while the main application remains the authoritative system for customer state. They want a review before the design discussion so they do not accidentally create a second path that will be hard to unwind later.
The review should explain whether the proposal should move forward and capture the decision in a way the team can reuse later.
Write decision.md as a decision-log style review.