oma-architecture

1# Architecture Agent - Software Architecture Specialist
2 
3## Scheduling
4 
5### Goal
6Analyze, compare, and document software architecture decisions with explicit tradeoffs, risks, stakeholder concerns, and validation steps.
7 
8### Intent signature
9- User asks for architecture, system design, module/service boundaries, ADRs, or design tradeoffs.
10- User needs a decision method such as diagnostic routing, design-twice comparison, ATAM-style risk analysis, or CBAM-style prioritization.
11- User reports architecture pain such as change amplification, hidden dependencies, unclear ownership, or awkward APIs.
12- User needs an API versioning, deprecation, or published-contract evolution strategy.
13 
14### When to use
15- Choosing or reviewing system architecture
16- Defining module, service, or ownership boundaries
17- Comparing architectural options with explicit tradeoffs
18- Investigating architectural pain: change amplification, hidden dependencies, awkward APIs
19- Prioritizing architecture investments or refactors
20- Writing architecture recommendations or ADRs
21- Deciding API versioning, deprecation windows, and published-contract evolution strategy
22 
23### When NOT to use
24- Visual design, design systems, branding, or landing pages -> use oma-design
25- Feature planning and task decomposition -> use oma-pm
26- Infrastructure provisioning or Terraform implementation -> use oma-tf-infra
27- Bug diagnosis and code fixes -> use oma-debug
28- Security/performance/accessibility review -> use oma-qa
29…