What problem does it solve? Platform engagements stall on two questions — how many platforms to build and how to shape them — and answers are usually folklore rather than citable reasoning. This Skill turns those questions into a defensible platform-count heuristic, an environment topology, and a deployable Azure landing-zone design. ## Core Features & Use Cases - Platform-count heuristic: Applies a five-step, source-cited heuristic (CNCF Platforms whitepaper, Team Topologies, Microsoft CAF) to decide how many platforms an organization needs. - Radius environment ladder: Sizes topology across simple, application-centric, and enterprise rungs, including sovereignty-driven designs with one Radius environment per residency boundary. - Landing-zone design: Produces AVM-first landing-zone plans with subscription vending, foundation services, and central Azure Managed Grafana observability, plus ADRs for contested decisions. - Use Case: A platform lead asks how many platforms a multi-BU, multi-region organization needs; the Skill interviews for teams, stacks, and compliance splits, then emits an architecture spec, Mermaid topology diagram, and AVM-mapped deployment plan. ## Quick Start Ask the agent to recommend how many platforms your organization needs and design the Azure landing-zone topology for your teams, regions, and compliance boundaries.
