Files
solution_architecture_agent/skills/cloud-discovery/SKILL.md
Jonathan Boniface c84dbdea20 feat: the solution architecture agent on the shared Execution engine
The reference agent's subject, cloud solution architecture, as an agent in
the operating model agent's pattern: the Execution engine (from
orchestration_engine) and one Workflow in app/solution_architecture,
built for the settings and provider bundle by assembly.workflow_for.

Copied from gcp_solution_architecture_agent at 8b397cd without its own
engine: its role files, Skills, provider bundle, ADRs, vocabulary, scripts
and evaluation datasets. The image takes the engine from a named build
context and installs Terraform. It is called through the Orchestration
engine, and its files are what the operating model agent digests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 19:49:28 +01:00

2.1 KiB

name, description, metadata
name description metadata
cloud-discovery Discovers and documents the current state of a workload's existing cloud environment through the Cloud provider's read-only MCP discovery tools. Use when requirements discovery needs the as-is architecture of resources that already run in the user's cloud project or account.
scope
requirements-discovery

Cloud discovery

Describe what actually exists, so requirements rest on facts rather than recollection.

Before you discover

Your discovery tools read the user's live cloud environment. The first call may pause the Execution to ask the user's permission. When permission is refused, work only from what the user tells you.

Ask the user which project, subscription or account and which regions hold the workload, unless the request already says. Discover only there.

Steps

  1. Inventory first. Use the broadest inventory tool available (an asset inventory or project search) to list the resource types and counts in scope.
  2. Detail what matters. For each resource type that belongs to the workload, call the product's list and get tools for configuration: sizes, regions and zones, scaling, networking, identities and their roles.
  3. Map relationships. Connect compute to its data stores, messaging, load balancers and identities, from configuration you have read, not from names alone.
  4. Record gaps. When a tool reports a discovery gap (a server that's unavailable, an API that isn't enabled, a permission that's missing), list it under Assumptions / discovery gaps with the resource type it leaves unknown.

Writing the current state

Under the Current state heading, give:

  • a component inventory table: component, resource type, location, key configuration
  • the relationships between components as a short list
  • observed operational signals, such as alert policies and dashboards, when discovered
  • Assumptions / discovery gaps

Report what exists, not what should change; recommendations belong to later Deliverables. Never include secrets, credentials, object contents or database rows, even when a tool returns them.