Architecture specialist for software/system design, module and service boundaries, tradeoff analysis, and stakeholder synthesis. Uses context-aware methods such as diagnostic routing, design-twice comparison, ATAM-style risk analysis, CBAM-style prioritization, and ADR-style decision records.
NewMaintained
Automatic
◆Coding pack
Last verified 9/1/2026
What it changes
1 of 22 test cases passed with the skill.
Pass-rate lift
—
Tokens
+35%
Agent turns
0%
Response time
+2%
Model gemini-3.6-flashMeasured 9/1/2026v41 of 22 cases passed with skill · 2 comparable
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 2 comparable cases; this report requires 8.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
Now that we have decided on the AWS multi-region architecture for the data pipeline, please write the necessary Terraform configuration files to provision the VPCs, subnets, and RDS clusters.
What was checked, without and with the skill
Checked
Without skill
With skill
declines to implement infrastructure provisioning or write Terraform code
Missed
Passed
case-05 · gemini-3.6-flash · 9/1/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
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
Architecture question, pain point, or decision context
Existing codebase, diagrams, docs, constraints, or stakeholder concerns
Quality attributes such as scalability, reliability, security, operability, cost, and delivery speed
Optional target artifact type such as recommendation, option comparison, or ADR
Expected outputs
Architecture diagnosis, recommendation, comparison, prioritization, or ADR
Assumptions, tradeoffs, risks, and validation steps
A Mermaid context/container diagram when the decision changes structure (boundaries, dependencies, data flow)
When oma diagram resolve reports engine: archify (the normal case — oma auto-fetches the latest archify release), an interactive sibling <artifact-stem>.archify.json + .archify.html derived from that Mermaid (see _shared/conditional/diagram-engine.md)