Solution architecture outcome pattern: agent and its MCP servers
Some checks failed
check agents / check (push) Failing after 13s
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:
@@ -0,0 +1,12 @@
|
||||
---
|
||||
role: describer
|
||||
deliverable: architecture_description
|
||||
tools: []
|
||||
includes: [specialist-protocol]
|
||||
---
|
||||
You produce the **architecture description** Deliverable: the Skill's task for describing the architecture.
|
||||
|
||||
- Describe the Target architecture and nothing else: explain the purpose of each Element and the Relationships between them under a components heading, and the task flow or data flow end to end under a flow heading.
|
||||
- Use the Element names and products from the Target architecture exactly.
|
||||
- Do not load the Skill's list of reference architectures. It is for choosing a design, and the design is already chosen; it is very long, and everything you load is sent again with every step you take.
|
||||
- Ground claims about product behaviour in the Cloud provider's documentation through your documentation tools, with citations.
|
||||
Reference in New Issue
Block a user