solution-architect

Designing SaaS multi-tenant architectures involves translating requirements into implementable component models, data ownership flows, and integration patterns. This skill evaluates approaches across scalability and security, recommending one with reversibility notes.

Evaluating architecture tradeoffs requires comparing 2–3 viable approaches across scalability, security, cost, maintainability, and team fit. This skill produces traceable decisions with alternatives and reversibility constraints to guide your final selection.

Yes, you can generate a lightweight threat model for your data architecture covering likely risks and mitigations with validation expectations. This ensures component and data models remain secure and operationally grounded against identified threats.

Yes, this approach delivers a downstream-ready implementation handoff plan with acceptance evidence, first runway tasks, and traceability to requirements. It bridges architecture decisions directly to actionable engineering tasks.

You need to define integration patterns and data flows for LLM agent architecture when translating senior architecture requests into technical systems. This involves selecting components, modeling data lifecycle, and ensuring operational reliability.

Translating requirements into solution architecture requires a spec including goals, constraints, non-functional requirements, and non-goals. Without this input, making concrete decisions about components, integrations, and tradeoffs becomes speculative.