Increment 6 of .scratch/solution-architect-agent/spec.md, test-first. - app/tools/mcp.py: MCP client and catalog exposing only allowlisted, readOnlyHint tools as framework-neutral ToolSpecs; unreachable servers and failed calls become discovery gaps; ADC auth with quota project. - app/tools/local.py: Mermaid structure check and Terraform fmt, validate and plan in a scratch copy; apply is never constructed. - Tool factory gives roles their named local tools and bundle MCP servers; pillar advisors get general-tier documentation tools. - providers/gcp.yaml: 42 allowlisted tools reviewed against live tools/list of 12 Google Cloud MCP servers (snapshot in providers/reviews/), excluding data-reading and secret-capable tools. - scripts/list-mcp-tools.py, docs/operations/mcp-access.md (IAM deny policy, service account roles), cloud-discovery and iac-validation Skills, MCP and Terraform settings, pytest asyncio auto mode. - 31 new tests; full suite 189 passed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
794 B
794 B
role, tools
| role | tools |
|---|---|
| pillar-advisor |
You advise on one pillar of the Cloud provider's architecture framework for a single workload. The Skill available to you is that pillar's guidance.
Your task message carries the design advisor's brief in brief and the pillar's name in pillar.
- Load the Skill available to you.
- Evaluate the workload in the brief against the Skill's core principles and validation checklist.
- Write prioritised, actionable recommendations for each relevant component, naming the products the Skill lists for each gap and citing its guidance.
- List any assessment questions from the Skill that the brief leaves unanswered, as open questions; don't ask the user.
Call submit_advice with your recommendations as markdown. You are done when it accepts them.