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>
ALZ-F01 Discovery: individual agents
The ALZ-F01 Discovery Feature (ADO 3214441) as eight separate agents with no orchestrator, one per story, in KAB's declarative agent shape (agent.yaml, prompt.md, schemas/, eval/) on the KAB agent runtime. It follows cp4-agents: the same folder rules and the same workflow export format.
This is one of two patterns for CP1 Discovery, and which one is adopted hasn't been decided.
- This folder: separate agents, chained by the KAB workflow.
- The sub-agent pattern: one orchestrator agent, with the eight stories as its sub-agents.
The two patterns are kept apart so they can be compared, and each records its own decisions (docs/adr/).
| Step | Agent | Story | Takes from earlier steps |
|---|---|---|---|
| s1 | cp1-discovery-planner-agent |
ALZ-DSC-01 | — |
| s2 | cp1-estate-scan-executor-agent |
ALZ-DSC-02 | tasks |
| s3 | cp1-asset-inventory-normalisation-agent |
ALZ-DSC-03 | findings |
| s4 | cp1-cmdb-itsm-reconciliation-agent |
ALZ-DSC-04 | tasks, records |
| s5 | cp1-data-classification-agent |
ALZ-DSC-05 | records |
| s6 | cp1-network-discovery-assessment-agent |
ALZ-DSC-07 | tasks, records (runs alongside s5) |
| s7 | cp1-dependency-mapping-agent |
ALZ-DSC-06 | records, drift_items, flows |
| s8 | cp1-discovery-critic-agent |
ALZ-DSC-08 | everything, then the Engagement Lead's approval |
Layout
| Path | What it is |
|---|---|
cp1-*-agent/ |
An agent. README.md and docs/ are for people; CLAUDE.md and .agents/ are for coding agents. |
workflows/ |
This Feature's KAB workflow export |
scripts/ |
build_workflow.py (writes workflows/) and scaffold_from_stories.py (generated the agent folders) |
docs/ |
This pattern's ADRs |
These are shared with the other pattern and live at the repository root:
- the MCP server
alz-discovery-sample(../../mcp-servers/); - the check, render and import scripts (
../../scripts/); - the deploy profile and the deployment guide.
Files and artifacts in a run
The workflow can start with two KAB activity steps (ADR 0011):
- Parse Assessment Files: the run form's upload field.
- Artifacts: project artifacts fixed by id.
Their extracted text reaches the planner and the inventory agent as source_documents and reference_documents.
To build the workflow and apply it to KAB, run from the repository root:
python3 scripts/kab_import_workflow.py "individual-agents/ALZ-F01: Discovery Workflow Agent" --project-id <id> # validate only
python3 scripts/kab_import_workflow.py "individual-agents/ALZ-F01: Discovery Workflow Agent" --project-id <id> --apply # import as a draft
The script reads your KAB access token from ~/.kab_token. Importing needs the Editor role.
Run an agent locally
docker build -t <agent>:local <agent>/
docker run --rm -p 8080:8080 -e LITELLM_MODEL=gpt-5.6-sol -e LITELLM_PROXY_BASE=<gateway> \
-e LITELLM_MASTER_KEY=<key> -e MCP_GATEWAY_URL=<mcp gateway> -e MCP_AGENT_API_KEY=<key> <agent>:local
Deploying to the cluster is described in docs/deployment.md at the repository root.