oma-architecture
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.
npx skills add first-fluke/oh-my-agent --skill oma-architecture --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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,
- Scheduling
- Goal
- Intent signature
- When to use
- When NOT to use
- Expected inputs
- Expected outputs
- Dependencies
- Control-flow features
- Structural Flow
- Entry
- Scenes
- Transitions
- Failure and recovery
ls .agents/results/architecture/ # prior decisions — read before deciding rg --files rg "ADR|architecture|boundary|service|module|dependency|owner|interface" .
What does the oma-architecture skill do?
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.
How do I install it?
Run `npx skills add first-fluke/oh-my-agent --skill oma-architecture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From first-fluke/oh-my-agent, a repository with 1,204 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.