What problem does it solve? Choosing the right software architecture is hard: teams often over-engineer simple projects or under-design systems that later need to scale. This Skill provides a structured framework for analyzing requirements, evaluating trade-offs, and documenting decisions as Architecture Decision Records (ADRs). ## 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 documenting each decision with options considered, rationale, trade-offs accepted, and revisit triggers. - Use Case: A team starting a SaaS product with 5-10 developers can use the framework to justify a modular monolith with NestJS and PostgreSQL, document the decision in an ADR, and define migration triggers for future microservices extraction. ## Quick Start Ask the architecture skill to help decide between a monolith and microservices for a new SaaS product with a small team.