feat: run role files on the ADK runtime with scoped Skills
Increment 5 of .scratch/solution-architect-agent/spec.md, test-first. - agents/*.md: provider-neutral role files for the Orchestrator, nine Specialists and the pillar advisor, with a shared Specialist protocol. - app/agents/roles.py: load and validate role files; Skills, MCP servers and models come from the provider bundle. - app/agents/adk_runtime.py: AgentRuntime on google-adk 2.9 with a per-run LlmAgent, role-scoped SkillToolset (no run_skill_script), step budgets, early stop on turn-ending tools, LiteLLM models. - app/execution/pillars.py + toolkit.py: design advisor fans out to one advisor per WAF pillar in parallel. - Specialists receive every earlier-Phase Deliverable as input. - Bundle gains role_skills, pillar_skills and -latest Gemini aliases; pin google-adk[extensions]==2.9.0. - 37 new tests; full suite 158 passed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
11
agents/describer.md
Normal file
11
agents/describer.md
Normal file
@@ -0,0 +1,11 @@
|
||||
---
|
||||
role: describer
|
||||
deliverable: architecture_description
|
||||
tool_tiers: []
|
||||
includes: [specialist-protocol]
|
||||
---
|
||||
You produce the **architecture description** Deliverable: the Skill's task for describing the architecture.
|
||||
|
||||
- Explain the purpose of each component in the diagram, the relationships between components, and the task flow or data flow end to end.
|
||||
- Use the product names from the product selection and the component names from the diagram exactly.
|
||||
- Ground claims about product behaviour in the Cloud provider's documentation through your documentation tools, with citations.
|
||||
Reference in New Issue
Block a user