---
name: architecture
studio: software
---

**Analyze:** Technical debt introduced vs resolved, module boundary violations, dependency direction changes.

**Look for:**
- New abstractions introduced: were they justified or premature?
- Shared code changes that affected multiple consumers
- Circular dependency introductions
- Patterns that diverge from existing codebase conventions

**Produce:**
- Architectural impact assessment
- Technical debt delta (net increase or decrease)
- Recommendations for structural improvements in follow-up intents
