oma-architecture

Analyzes software architecture decisions and produces tradeoff comparisons, risk analyses, and ADR records.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/javiruu/viru-air --skill oma-architecture-javiruu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oma-architecture
Source: https://github.com/javiruu/viru-air/tree/main/.agents/skills/oma-architecture
Command: npx skills add https://github.com/javiruu/viru-air --skill oma-architecture-javiruu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It turns vague architecture pain points and open design questions into explicit, documented decisions with stated assumptions, tradeoffs, risks, and validation steps, instead of ad-hoc choices that harden into the codebase. ## Core Features & Use Cases - Method routing: Selects the lightest suitable method per request, including Diagnostic, Recommendation, Design-Twice, ATAM-style risk analysis, CBAM-style prioritization, and ADR modes. - Tradeoff and risk analysis: Compares at least two materially different options for material decisions, weighing implementation cost, operational cost, and future change cost. - Durable artifacts: Writes recommendations, reviews, and ADRs to .agents/results/architecture/ using structured output templates. - Use Case: When asked whether a notifications subsystem should become a separate service, it frames the problem, compares monolith-module versus dedicated-service options, and delivers a recommendation with risks and validation steps. ## Quick Start Ask the agent to review whether a specific module should be split into a separate service and to produce an ADR with the tradeoffs and recommendation.

Frequently Asked Questions about oma-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compare two software architecture options before committing?▼

Use the Design-Twice mode, which forces at least two materially different decompositions rather than superficial variations. The agent compares them on boundary clarity, quality attributes, implementation cost, operational cost, and future change cost before recommending one.

How to write an ADR for an architecture decision?▼

Use the ADR mode after the analysis is complete. It produces a concise record with context, decision, alternatives considered, consequences, and follow-up validation, saved under .agents/results/architecture/.

What is ATAM-style architecture risk analysis?▼

ATAM-style analysis evaluates an architecture against quality attribute scenarios such as reliability, performance, and modifiability. It surfaces sensitivity points, tradeoff points, risks, and non-risks, then prioritizes architectural concerns by impact.

When should I not use an architecture analysis skill?▼

Do not use it for visual or UI design, feature planning and task decomposition, Terraform infrastructure implementation, bug fixing, or security and performance verification. Those concerns route to dedicated design, PM, infra, debug, or QA skills.

How do I prioritize which architecture refactor to invest in first?▼

Use the CBAM-style mode, which compares candidate investments by estimated benefit, implementation cost, operational impact, and sequencing value. It outputs a priority ranking and a recommended investment sequence.