# Individual agents: ALZ-F02 Assessment & Disposition CP1 Assessment as six separate declarative KAB agents chained by the workflow, cp4-agents style, behind a code-only intake step (ADR 0008). Its counterpart, `../../sub-agents/ALZ-F02: Assessment & Disposition Workflow Agent/`, is the sub-agent pattern (not built yet). **Keep the two patterns apart:** never copy `app/`, sub-agents or workspace code into this folder, and never merge their ADRs. @.agents/CONTEXT.md @.agents/PLAN.md Each agent folder has its own `CLAUDE.md` and `.agents/CONTEXT.md`. Repository-wide rules are in `../../CLAUDE.md`. ## Commands (from this folder) ```sh python3 scripts/scaffold_from_stories.py # regenerate the six agent folders from the v1.1 story files python3 scripts/build_workflow.py # after any schemas/ change; it asserts every from_steps field exists python3 ../../scripts/check_agents.py --runtime-image cruciblecoredevacr.azurecr.io/kab/agent-runtime-adk:0.35.7 cp1-*/ (cd ../.. && python3 scripts/render_k8s.py deploy/crucible-kab-dev.yaml && kustomize build build/crucible-kab-dev/) ``` ## Rules - **Declarative agents only:** no `app/`, functions or hooks. Scoring, confidence and TCO are prompt rules that the critic recalculates (ADR 0001). Don't add a scoring tool or an MCP server for them. **The one exception is `cp1-assessment-intake-agent`** (ADR 0008): code only, not generated by the scaffold, and it only checks the Discovery package. Keep scoring out of it. - **Existing MCP servers only.** ALZ-ASM-02 and ALZ-ASM-05 use `azure-discovery`, `aws-discovery` and `gcp-discovery`. ALZ-ASM-05's guidance comes from `_search_well_architected` on the same servers (Azure and GCP; none on AWS yet). Read-only tools only. - **The agent folders are generated** by `scripts/scaffold_from_stories.py` from the story files in the engineering hub workspace. Change the script and regenerate; regenerating rewrites whole folders, so review the diff. - **Discovery's outputs arrive as one package, as text,** through `a1` (Artifacts) and `p1` (parse) (ADRs 0002, 0008), and the intake `s0` checks it before the planner runs. Never wire an agent to `a1` directly: its only output, `artifacts`, holds base64 records. - **Keep `repo: cp1-agents-individual`** on these agents in `../../deploy/`. - **A change to an original requirement** needs an ADR in `docs/adr/`, a link to it from each affected agent's `docs/adr/README.md` (in `ADRS_FOR` in the scaffold), and a step in `.agents/PLAN.md`. - **No pattern detail on ADO tickets.** Record pattern decisions here, not on the board.