What problem does it solve? Teams often make architecture choices informally, without comparing alternatives or documenting trade-offs, which leads to inconsistent standards, over-engineering, and unrecoverable one-way-door mistakes. This Skill structures the decision process and records the outcome as an Architecture Decision Record (ADR). ## Core Features & Use Cases - Structured Option Comparison: Compares at least two candidate designs against requirements and NFRs, with explicit trade-offs and consequences. - ADR and C4 Documentation: Produces an ADR skeleton (context, options, decision, door type, rollback trigger) plus a C4 design doc for larger systems. - Decision Guardrails: Tags one-way versus two-way doors, detects over-engineering, challenges premature microservices splits, and enforces a human sign-off gate. - Use Case: A 5-person team proposes splitting into 4 microservices. The Skill asks the three scoping questions, recommends keeping a modular monolith with only payments split out, and records the ADR with a revisit trigger at 5x traffic. ## Quick Start Ask the agent to help you decide between two architecture options and write an ADR documenting the trade-offs and rollback trigger.
