cloud-architecture-decider

What problem does it solve?

This Skill helps teams make a defensible cloud platform decision before naming provider services, preventing architecture-by-brochure and reducing costly rework.

Core Features & Use Cases

• Requirements-first decisioning: Collects compliance, residency, latency, availability, cost, operational maturity, existing estate, integration gravity, scale trajectory, and exit-cost tolerance before any provider choice.
• Provider-neutral architecture shaping: Defines the logical architecture in capability language so the cloud decision is based on real constraints, not vendor products.
• Hard filters and scored tradeoffs: Applies tenant isolation and compliance constraints as eliminators, then compares provider and deployment postures with explicit tradeoffs, lock-in, and exit costs.
• Managed vs self-hosted guidance: Decides per capability whether to use managed services or self-host, naming the reason and the operational bill accepted.
• Use Case: A SaaS team asks whether to choose Azure, AWS, multi-cloud, or stay put, and whether Kubernetes or PaaS is the right runtime posture.

Quick Start

Ask the cloud architecture decider to gather the nine-axis requirements, shape a provider-neutral logical architecture, and recommend the best provider and deployment posture with tradeoffs and exit costs.