Agent skill · product strategy · google
google-cloud-solution-architecture
Interactively discovers requirements and designs holistic, multi-product system architectures, solution blueprints, and deployment recommendations for complex workloads on Google Cloud. Use when designing end-to-end cloud solutions, selecting and integrating Google Cloud services, generating architecture diagrams, or conducting requirements discovery for new cloud workloads or migrations. Don't use for single-product tasks (use product-specific skills), initial onboarding or authentication (use google-cloud-recipe-*), Well-Architected Framework reviews or audits (use google-cloud-waf-*), or workloads covered by specialized solution skills.
Why this skill is useful
Generates detailed architectural guidance and validation scripts for multi-product solutions on Google Cloud that the AI wouldn't reliably produce on its own.
What it needs
Requires google-cloud account access. About 7k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.
What this skill does
Google Cloud solution-architecture workflow Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution. Overview of the workflow The workflow consists of the following phases: Phase 1: Requirements discovery. Gather detailed requirements related to the cloud workload or use case that the user needs assistance for. Phase 2: Solution architecture. Use the requirements that were gathered in Phase 1 to generate a detailed solution architecture for the cloud workload or use case. Phase 3: Solution validation. Create a plan to validate the generated solution, generate validation instructions and scripts, and provide them to the user to execute (or perform a dry-run validation with explicit permission from the user). Phase 4: Solution packing and presentation. Consolidate the generated content and present the solution. Important notes about the workflow: Strict phase separation: During Phase 1 (Requirements discovery), when you ask the user clarifying questions, don't recommend, propose, or outline any architectural designs, technical decompositions, cloud services, or component mappings. Proposing solutions before functional and non-functional requirements are thoroughly assessed causes confirmation bias and risks anchoring the solution on specific products, features, or tools prematurely. Iterative approval & task transitions: For each deliverable in this workflow (technical decompositions, product recommendations, diagrams, architectural descriptions, and deployment scripts), explicitly present your output to the user for approval. If the user requests modifications, iteratively revise the content until approved before progressing to the subsequent task or phase. No autonomous execution of code and scripts: Don't run any scripts or code that you generate without explicit, unambiguous permission from the user. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/google-cloud-solution-architecture