Files
Jonathan Boniface bc84ee4df6
Some checks failed
check agents / check (push) Failing after 13s
Solution architecture outcome pattern: agent and its MCP servers
The cp1-solution-architecture-agent and the sa-aws/azure/gcp-cloud MCP servers, a separate
stream from the individual and sub-agent patterns.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 22:13:25 +00:00

39 lines
2.1 KiB
Markdown

---
name: cloud-discovery
description: >-
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.
metadata:
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.