Skip to content

gracefullight/pkgs / .agents/skills/oma-architecture

oma-architecture

Verified

Evaluate system boundaries and architectural tradeoffs. Use for architecture decisions, design reviews, and ADRs.

resources/checklist.md

View on GitHub
# Architecture Agent - Checklist

## Framing
- [ ] The architecture problem is stated explicitly
- [ ] Constraints and quality attributes are identified
- [ ] Non-goals are listed

## Consistency with Prior Decisions
- [ ] Prior artifacts in `.agents/results/architecture/` were reviewed
- [ ] Conflicts with prior ADRs are resolved by superseding (old ADR `Status` updated), not ignored

## Method Choice
- [ ] The chosen methodology matches the problem
- [ ] The analysis is not heavier than necessary
- [ ] Diagnostic routing was used when the initial problem was vague

## Tradeoffs
- [ ] At least two options were compared when the decision was material
- [ ] Tradeoffs are concrete, not generic
- [ ] Implementation cost is considered
- [ ] Operational cost is considered
- [ ] Team cognitive load / maintenance cost is considered

## Synthesis
- [ ] Stakeholder input was gathered only if justified by scope
- [ ] Agreements and tensions are separated clearly
- [ ] A recommendation is explicit
- [ ] Rejected options are documented when relevant

## Decision Quality
- [ ] Assumptions are listed
- [ ] Risks are listed
- [ ] Validation steps are listed, with an executable check (fitness function / dependency rule) where feasible
- [ ] A Mermaid diagram is included when the decision changes structure
- [ ] A transition plan is included when the decision restructures a live system
- [ ] Output artifact matches the selected mode
- [ ] Durable artifact saved and the `architecture.adr-complete` event emitted and verified

## Boundaries
- [ ] Visual/UI design concerns were not conflated with software architecture
- [ ] Terraform/IaC concerns were not allowed to take over system-design reasoning
- [ ] PM planning work was not duplicated
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall