| name | architecture-review |
| description | Review a diff for architecture drift, wrong abstractions, boundary violations, coupling, and chunk-scope violations. |
Architecture Review
Review current changes against the initiative plan and architecture boundaries.
Focus
- Did the change stay inside the approved chunk?
- Did it introduce the wrong abstraction?
- Did it mix orchestration with execution?
- Did it mix policy with persistence?
- Did it bypass an existing boundary?
- Did it create hidden coupling?
- Did it introduce speculative generality?
- Did it add complexity without necessity?
- Did it make future chunks harder?
- Is the data/control flow understandable?
Special rule
Architecture drift is blocking even when tests pass.
Output
Result: PASS / PASS WITH LOW RISKS / FAIL
Boundary violations:
Abstraction risks:
Coupling risks:
Simpler alternative:
Required fixes: