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

2.1 KiB

name, description, metadata
name description metadata
example-organisation-standards An example of an organisation's cloud standards as an overlay Skill: naming, mandatory labels, approved regions and a short list of things never to do. Use on any Deliverable of an Execution that names this overlay, to apply the organisation's standards on top of the Cloud provider's guidance.
scope overlay
every Deliverable organisation standards (example)

Organisation standards (example)

This is an example. Copy it, replace every rule with your organisation's own, and name the copy when you start an Execution. Nothing here is a real organisation's policy.

An overlay adds to the Cloud provider's guidance. Where the two disagree, this Skill wins; where a requirement the user stated disagrees with this Skill, say so in your Deliverable and follow the user's requirement.

Naming

  • Every resource is named <workload>-<environment>-<purpose>, lower case, with hyphens: orders-prod-ingest.
  • <environment> is one of dev, test, prod, and comes from a variable.

Labels

Every resource that accepts labels carries all four:

Label Value
workload the workload's short name
environment dev, test or prod
owner the owning team's short name
cost-centre the cost centre code, from a variable

Regions

  • Deploy only to europe-west1 or europe-west4.
  • Data at rest stays in the European Union.

Never

  • No public IP address on a database.
  • No service account key files; workloads use attached identities.
  • No resource without deletion protection in prod, where the resource type has it.

What each Specialist does with this

  • Requirements: record each standard above that applies as a non-functional requirement, with this Skill as its source, so it is traced like any other.
  • Design recommendations and Target architecture: a standard that applies becomes a Check on every Element it constrains.
  • Infrastructure code: follow the naming and label rules exactly.
  • Validation: the standards are verified through the Checks that came from them.