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
{
"context": "Checks whether the agent performs an architecture review using the decision-log structure and surfaces boundary conflicts before endorsing a new write path.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Context",
"description": "Includes the Context section from the decision log template",
"max_score": 10
},
{
"name": "Decision",
"description": "Includes the Decision section from the decision log template",
"max_score": 10
},
{
"name": "Alternatives",
"description": "Includes the Alternatives Rejected section from the decision log template",
"max_score": 10
},
{
"name": "Constraints",
"description": "Includes the Constraints Added or Changed section from the decision log template",
"max_score": 10
},
{
"name": "Consequences",
"description": "Includes the Consequences section from the decision log template",
"max_score": 10
},
{
"name": "Acceptance test",
"description": "Includes the Acceptance Test section from the decision log template",
"max_score": 10
},
{
"name": "Source of truth",
"description": "Checks whether the proposal changes or duplicates the source of truth",
"max_score": 10
},
{
"name": "Write boundary",
"description": "Checks whether the proposal adds a new write path or bypasses a runtime boundary",
"max_score": 10
},
{
"name": "Duplication risk",
"description": "Checks for duplicated capability or a second way to perform the same operation",
"max_score": 10
},
{
"name": "Traceability",
"description": "Checks audit history, ownership, fuzzy matching, phase gates, or ADR constraints and surfaces any conflict before implementation",
"max_score": 10
}
]
}