Design is now approved before any infrastructure code is written (ADR-0005). A new target-architect Specialist produces one graph of Elements, Relationships and Checks; the diagram is rendered from it, deployment guidance must account for every Check, and validation gives a verdict per Check. Requirements, components, products and recommendations carry ids in data files, and a submission with a gap in the Requirements chain is refused. Also in this commit: - Customer cases group Executions, with an intent history per case - lesson candidates are captured when an Execution ends - evaluation gains chain, verdict, judged and interactive checks, and per-case thresholds - Terraform providers are cached between checks - the requirements analyst proposes defaults instead of asking - the legacy-baseline case and the checks that only read it are removed - ADR-0006 (Change requests) accepted; ADR-0004 and ADR-0007 proposed - plans for iterations 4 to 7 under .agents/plans/ Unproven with a real model: no evaluation run has completed on this design. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3.5 KiB
Plan Map
Iteration: 4, learning and Skills
Intent: Make the agent a learning, adaptable solution through Skills. Fix the cheap defects the 2026-10-06 review found, then close the loop so each Execution can improve the next through a reviewed Skill change, then let new standards, clients and Cloud providers arrive as Skills and configuration.
Status: steps 1 to 8 and 15 built; no evaluation run has completed on them (see steps/step-8.md); step 9 drafted and awaiting the owner; steps 10 to 14 planned. Steps 1 to 6 are in commit 7ee49ab; 7, 8 and 15 are uncommitted.
Changed by iteration 6: docs/adr/0005-the-target-architecture-is-an-explicit-graph.md (accepted 2026-10-07) replaces the free-form findings.json of step 1 with a verdict per Check, remove the diagrammer, and add a Phase. Its plan is ../iter-06-target-architecture-graph/, which lists the effect on each step here and should be built before steps 10 to 14.
This directory covers: steps 1 to 16
Sources of truth
- Review report (2026-10-06): https://claude.ai/code/artifact/16b37169-1554-4eb7-bfcb-254315fa0518. Each step's
Report refnames its enhancement number there. The report uses pre-iteration-3 paths. iter-02-solution-architect-agent/steps/step-8.md: the evaluation figures quoted as evidence.docs/adr/0002-skills-are-the-portable-unit-of-behaviour.md: every step must keep behaviour in Skills and vendored Skills unmodified.CONTEXT.md: "every Execution starts clean". Learning arrives as a reviewed Skill change, never as memory carried between Executions.
Status
| Step | What | Group | Size | Status |
|---|---|---|---|---|
| 1 | Structured validator findings | A | S | replaced by iteration 6 step 9 (verdicts per Check) |
| 2 | Carry the draft through needs_input |
A | S | complete |
| 3 | Reuse pillar advice across Revisions | A | S | built; evaluation run outstanding |
| 4 | Single source for Deliverable contracts | A | S | complete |
| 5 | Cap parallel Specialists | A | S | complete |
| 6 | Orchestrator step order | A | S | built; seen working in one stopped run, no completed evaluation |
| 7 | Capture lesson candidates | B | M | complete |
| 8 | Evaluation that can see improvement | B | M | built; thresholds and a judged run outstanding |
| 9 | ADR: the lessons loop and overlay Skills | B | S | drafted as docs/adr/0004-lessons-and-overlays-arrive-as-skills.md, status proposed; awaits the owner |
| 10 | Lessons Skill and lesson curator | B | L | planned |
| 11 | IaC patterns Skill | B | M | planned |
| 12 | Overlay Skills and an organisation standards Skill | C | M | planned |
| 13 | Trim Specialist context | C | M | planned |
| 14 | Provider-owned contracts | C | M | planned |
| 15 | Group Executions by Customer case | added | S | complete |
| 16 | Cache Terraform providers between checks | added | S | complete |
Size: S under a day, M a few days, L a week or more. Group A is cheap fixes that also create signal. Group B is the learning loop. Group C is adaptability.
Dependency graph
- Steps 1 to 6: no dependencies; any order
- Step 7: depends on step 1
- Step 8: no dependencies
- Step 9: no dependencies
- Step 10: depends on step 7, step 8, step 9
- Step 11: depends on step 8
- Step 12: depends on step 9
- Step 13: depends on step 8
- Step 14: depends on step 4
- Step 15: no dependencies (added on 2026-10-06 at the owner's request)
- Step 16: no dependencies (added on 2026-10-07 at the owner's request)
Step 8 comes before steps 10, 11 and 13 so each of them can be shown to help: same quality, fewer Revisions, seconds or tokens.