engineering-review

name	engineering-review
description	Use for architecture, system design, code review, debugging, refactoring, technical debt, data models, testing strategy, performance, reliability, or implementation quality. Do not use for business analysis without a technical decision.

Engineering Review

1. Inspect the current implementation and constraints.
2. Define boundaries, responsibilities, data ownership, and trust boundaries.
3. Identify failure modes, edge cases, performance risks, and operational dependencies.
4. Prefer the smallest architecture that safely supports the approved outcome.
5. Review correctness, security, maintainability, testability, observability, migration, and rollback.
6. Run deterministic checks before recommending completion.
7. Distinguish urgent defects from optional polish.

Do not refactor broadly without evidence of value and approval.