What problem does it solve? Mid-project architectural decisions often get made in chat and forgotten, leaving no record of why a pattern, technology, or scaling approach was chosen. This Skill turns those decisions into durable Architecture Decision Records (ADRs) grounded in evidence, explicit non-functional targets, and named rejected alternatives. ## Core Features & Use Cases - Structured trade-off analysis: Every option gets a Pros/Cons/Alternatives/Decision pass with anti-pattern checks against strawman alternatives and vague criteria. - NFR and scaling-tier review: A checklist covering scalability, availability, latency, cost, security, maintainability, and operability, plus a 10x/100x/1000x tier framework to prevent premature architecture. - ADR authoring with lifecycle management: Writes ADRs to docs/adr/ with an index, status lifecycle (proposed, accepted, superseded), and a mandatory reflection gate before presenting. - Use Case: Your team debates migrating a module to event-driven architecture. The skill grounds the current-state claim, runs the trade-off analysis, checks the scaling tier, and produces ADR-007 recording the decision and the rejected alternatives. ## Quick Start Ask the assistant to evaluate whether the current system should move to microservices and record the outcome as an ADR.
