oma-architecture

# Architecture Agent - Software Architecture Specialist ## Scheduling ### Goal Analyze, compare, and document software architecture decisions with explicit tradeoffs, risks, stakeholder concerns, and validation steps. ### Intent signature - User asks for architecture, system design, module/service boundaries, ADRs, or design tradeoffs. - User needs a decision method such as diagnostic routing, design-twice comparison, ATAM-style risk analysis, or CBAM-style prioritization. - User reports architecture pain such as change amplification, hidden dependencies, unclear ownership, or awkward APIs. - User needs an API versioning, deprecation, or published-contract evolution strategy. ### When to use - Choosing or reviewing system architecture - Defining module, service, or ownership boundaries - Comparing architectural options with explicit tradeoffs - Investigating architectural pain: change amplification, hidden dependencies, awkward APIs - Prioritizing architecture investments or refactors - Writing architecture recommendations or ADRs - Deciding API versioning, deprecation windows, and published-contract evolution strategy ### When NOT to use - Visual design, design systems, branding, or landing pages -> use oma-design - Feature planning and task decomposition -> use oma-pm - Infrastructure provisioning or Terraform implementation -> use oma-tf-infra - Bug diagnosis and code fixes -> use oma-debug - Security/performance/accessibility review -> use oma-qa ### Expected inputs...