gcp_solution_architecture_agent/CONTEXT.md

Cloud Solution Architecture

Turns a request for a cloud workload into a reviewed solution architecture: requirements, a target design with diagram and infrastructure-as-code, validation results, and a packaged guide. Google Cloud is the first Cloud provider.

Language

Running the workflow

Workflow request: The free-text description of the workload a caller wants architected; the opening input to an Execution. Avoid: prompt, query, request summary

Execution: One solution-architecture engagement for a single Workflow request. It lasts from the first request to an approved Solution guide, and may span many user turns. Avoid: run, job, workflow execution

Session: A caller-supplied grouping of Executions. A Session never feeds earlier outputs into a later Execution; each Execution starts clean. Avoid: conversation, context

Phase: A named grouping of Deliverables: requirements discovery, solution architecture, solution validation, or packaging. A Phase is complete when all its Deliverables are submitted and the user has granted the Phase's Approval. Avoid: step, node, stage, pipeline

Approval: A user's explicit acceptance of a Phase's Deliverables, required before work that depends on them may start. An Execution is interactive by default. A pre-approved Execution treats its Approvals as already granted. Avoid: sign-off, confirmation, gate (in prose)

Revision: Reopening a Deliverable because validation found a problem or the user asked for a change. It returns that Deliverable and everything that depends on it to draft, and withdraws any Approval that covered them. Revisions per Deliverable are limited, and past the limit the user decides. Avoid: review round, retry, loop iteration

Agents

Orchestrator: The top-level agent of an Execution, and the only agent that talks to the user. It reasons about which Deliverables are ready to produce, delegates them to Specialists, and asks the user for Approvals. Avoid: supervisor, manager, root agent, router

Specialist: An agent responsible for producing one kind of Deliverable, such as the product selector or the diagrammer. A Specialist may delegate independent parts of its work to further Specialists. Avoid: sub-agent, worker, phase agent, node

Portability

Skill: A self-contained package of domain guidance: instructions plus optional references, assets and scripts, in the Agent Skills format. It is the portable unit of the agent's behaviour and is loaded on demand. Avoid: prompt template, instructions, playbook

Cloud provider: The hyperscaler a solution architecture targets, such as Google Cloud. Each Cloud provider brings its own Skills, plus the MCP servers it hosts for discovering a user's current environment and grounding recommendations in its documentation. Avoid: hyperscaler, cloud, platform, target

Outputs

Deliverable: A document an Execution produces: requirements, technical decomposition, product selection, architecture diagram, architecture description, design recommendations, deployment guidance, validation results, or the Solution guide. Each Deliverable depends on others being approved first. Avoid: artifact, output file

Dependency: The relationship between two Deliverables in which one can only be produced once the other has been accepted, for example an architecture diagram depending on the product selection. Within a Phase, a submitted Deliverable counts as accepted. Across Phases, only the earlier Phase's Approval does. Avoid: prerequisite, edge, upstream

Solution guide: The packaged Deliverable that assembles every other Deliverable into the Cloud provider's solution architecture template. Avoid: final report, package