architecture-decision

This skill generates Architecture Decision Records (ADRs) that capture the context, decision, and consequences of significant technical choices. It guides you through gathering essential information, selecting from three formats (MADR, Nygard, or Y-Statement), and produces a structured document that preserves reasoning for future engineers.

Create and maintain Architecture Decision Records that capture the reasoning behind significant technical choices. This skill provides multiple templates—from standard MADR format to lightweight Y-statements—and guidance on when ADRs matter most, helping teams establish clear decision-making processes and onboard members through documented architectural history.

Architecture Decision helps you systematically evaluate design choices, document trade-offs, and select appropriate patterns for your context. It provides frameworks for creating Architecture Decision Records, assessing technical debt, and balancing quality attributes like performance, scalability, and maintainability.

Create Adr Spike walks you through a five-phase process—Research, Analysis, Decision, Documentation, and Memory Storage—to evaluate technical alternatives and formalize architectural choices. It manages ADR lifecycle with proper numbering, integrates external research tools, and persists decisions to a memory graph for future reference.

Architecture Designer guides you through system design from requirements to documented decisions. It creates architecture diagrams, evaluates technology trade-offs, and produces Architecture Decision Records for key choices. Use it to structure microservices, plan scalability, and validate designs with stakeholders.

Decision Analysis exposes assumptions, failure paths, and success conditions for high-stakes design choices. It uses premortem and backcast reasoning to rank options against constraints, reversibility, and evidence quality, then returns a risk-calibrated recommendation. The skill routes obligations and rationale to their authoritative destinations—RFC, ADR, Work Item, or verification—rather than creating artifacts itself.