google-cloud-solution-architecture
Interactively discovers requirements for a specific cloud workload and generates design recommendations and architectural guidance to build a multi-product solution in Google Cloud. Use this skill to generate holistic, end-to-end design recommendations and architectural guidance for complex, multi-product workloads on Google Cloud for specific use cases. Don't use this skill when other specialized skills (e.g., product-specific or google-cloud-recipe-*) directly address the user's workload or us
Security Assessment
About google-cloud-solution-architecture
This skill drives an interactive, phased workflow for designing multi-product solutions on Google Cloud. It solves the problem of producing holistic, end-to-end architecture recommendations for complex workloads without prematurely anchoring on specific products. The workflow has four phases: requirements discovery, solution architecture, solution validation, and solution packing and presentation, with strict guardrails between them.
The skill enforces disciplined behavior: during requirements discovery it must not propose any architecture, products, or technical decompositions until functional requirements, non-functional requirements (security, privacy, compliance, reliability, DR, cost, operations, performance, sustainability), current state, and dependencies are gathered, and it must surface and resolve ambiguities or contradictions before designing. Each deliverable, including technical decompositions, product recommendations, diagrams, architectural descriptions, and deployment scripts, is presented for explicit user approval before proceeding. Notably, it forbids autonomous execution of any generated scripts or code, requiring explicit user permission because running them could provision unintended cloud resources, incur costs, or mutate live infrastructure, and it grounds generated content against official Google Cloud guidance via the Google Developer Knowledge MCP server. Supporting references cover architecture guides, decision-making guides, best-practices guides, and an output template.
Target users are cloud architects, solution engineers, and technical teams planning complex, multi-product Google Cloud workloads. Typical use cases include structured requirements gathering, generating a technical decomposition, producing grounded architecture recommendations and validation plans, and packaging a complete solution guide, while deferring specialized product-specific skills when those directly address the workload.
FAQ
What are the phases of this workflow?
Four phases: requirements discovery, solution architecture, solution validation (creating validation plans, instructions, and scripts for the user to run), and solution packing and presentation.
Will it design an architecture immediately?
No. It enforces strict phase separation and must gather functional and non-functional requirements, current state, and dependencies, and resolve any ambiguities or contradictions, before proposing any architecture, products, or decomposition.
Does it run scripts or provision resources on its own?
No. It explicitly forbids autonomous execution of generated scripts or code, requiring unambiguous user permission, because execution could provision unintended cloud resources, incur costs, or mutate live infrastructure, and it always offers manual execution instead.
How does it keep recommendations accurate?
It grounds generated content against official Google Cloud guidance using the Google Developer Knowledge MCP server, and draws on bundled reference guides for architecture, decision-making, and best practices.
When should I not use this skill?
When a more specialized skill (a product-specific or google-cloud-recipe-* skill) directly addresses the user's workload or use case; this skill is for holistic, complex, multi-product solutions.
Install google-cloud-solution-architecture
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
google/skills