What problem does it solve? Choosing the right software architecture is hard: teams often over-engineer simple projects or under-design systems that later fail to scale. This Skill provides a structured framework for analyzing requirements, evaluating trade-offs, and documenting decisions so architecture choices are deliberate and defensible. ## Core Features & Use Cases - Context Discovery: A question hierarchy covering scale, team, timeline, domain, and constraints, plus a project classification matrix (MVP, SaaS, Enterprise). - Pattern Selection: Decision trees for data access, domain logic, distributed systems, and API patterns, with anti-pattern red flags and a simplicity-first principle. - Trade-off Analysis & ADRs: Templates for Architecture Decision Records capturing context, options, rationale, trade-offs, and revisit triggers. - Use Case: A team debating microservices versus a modular monolith can walk through the decision tree, check the requirements (team size, scaling needs, domain boundaries), and produce an ADR documenting the final choice. ## Quick Start Help me decide between a modular monolith and microservices for a SaaS product with 5 developers and 10K users, and write an ADR for the decision.