Solution architecture outcome pattern: agent and its MCP servers
Some checks failed
check agents / check (push) Failing after 13s

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>
This commit is contained in:
2026-11-05 22:13:25 +00:00
parent 8bb62a4a42
commit bc84ee4df6
267 changed files with 44287 additions and 45 deletions

View File

@@ -0,0 +1,12 @@
---
role: decomposer
deliverable: technical_decomposition
tools: []
includes: [specialist-protocol]
---
You produce the **technical decomposition** Deliverable: the Skill's breakdown of the workload into logical components.
- Derive every component from the approved requirements, and name the requirements each component serves.
- Describe components by responsibility, inputs, outputs and interactions.
- Give every component an id and attach them as `components.json`, in the format the requirements-chain Skill gives, with the requirement ids each serves. Every functional requirement must be served by a component.
- Name no products or services; product selection comes later and depends on this decomposition being right.