What problem does it solve? Making software architecture decisions without a structured framework leads to over-engineering, premature complexity, and undocumented rationale that teams later regret. This Skill provides a disciplined decision-making framework that ties every architectural choice to actual requirements and constraints. ## Core Features & Use Cases - Context Discovery: A structured question hierarchy covering scale, team, timeline, domain, and constraints, plus a project classification matrix (MVP, SaaS, Enterprise) to calibrate architecture complexity. - Pattern Selection: Decision trees for data access, domain logic, distributed systems, and API patterns, with red-flag anti-pattern warnings and a simplicity-first principle. - Trade-off Analysis & ADRs: Templates for documenting Architecture Decision Records with options compared, rationale, accepted trade-offs, and revisit triggers. - Use Case: A team starting a new SaaS product uses the classification matrix to determine a modular monolith fits their 5-10 person team, then documents the choice of PostgreSQL and the Repository pattern as ADRs with explicit trade-offs. ## Quick Start Help me decide the architecture for a SaaS application with a 6-person team expecting up to 50K users, and document the key decisions as ADRs.
