sporkwace/guv
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
task.mdevals/scenario-4/
Checkout Next Step
Problem / Feature Description
The checkout flow is still incomplete, and the product lead wants advice on whether the next sprint should stabilize the current release path or start a UI overhaul. The team needs a recommendation that is grounded in the current state of the project rather than in abstract design preferences.
Write a short recommendation memo that makes the tradeoffs explicit and states the next step.
Output Specification
Write decision.md with your recommendation memo.