All checks were successful
check agents / check (push) Successful in 10s
ALZ-F01 Discovery as a sub-agent orchestrator (sub-agents/) and as eight individual declarative agents (individual-agents/), with their KAB workflow exports. Shared check, render and import scripts, the alz-discovery-sample MCP server, the crucible-kab-dev deploy profile, deployment docs, platform issue reports and the source material. Agent steps time out at 20 minutes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
Sub-agent pattern: ALZ-F01 Discovery
One orchestrator agent with the eight ALZ-DSC stories as sub-agents. Its counterpart, ../../individual-agents/ALZ-F01: Discovery Workflow Agent/, is the individual-agents pattern. Keep the two patterns apart: never merge their ADRs or copy code between them.
The agent's context and plan are in cp1-alz-discovery-orchestrator-agent/CLAUDE.md and its .agents/. Read them before changing it. Repository-wide rules are in ../../CLAUDE.md.
Commands (from this folder)
python3 ../../scripts/check_agents.py --runtime-image cruciblecoredevacr.azurecr.io/kab/agent-runtime-adk:0.35.7 cp1-alz-discovery-orchestrator-agent
python3 scripts/dry_run.py cp1-alz-discovery-orchestrator-agent "$(mktemp -d)" # the agent's code, with no model or MCP server
python3 scripts/build_workflow.py # after any schemas/ change
Feature folder rules
- The next Feature (ALZ-F02 …) gets its own Feature folder with the same layout: the agent,
workflows/, andscripts/build_workflow.py. Keep the shared pieces in../../scripts/. scripts/here holds only what is specific to this Feature. Anything two Features need goes to../../scripts/.