# Change Impact Analysis Profile

```yaml
roles:
  - role: analyser
    min: 2
    recommended: 3
    max: 5
    duty: analysis-worker
  - role: report-writer
    min: 1
    recommended: 1
    max: 1
    duty: report-writer
  - role: verifier
    min: 0
    recommended: 0
    max: 0
    duty: reverification-worker
    dynamic: true
```

- Purpose: assess the read-only impact of a proposed change, including preserved behavior, affected dependencies, and constraints that a later planning phase must resolve
- Required workers:
  - claude
  - codex
  - report-writer
- Optional workers (opt-in via `--workers`):
  - antigravity
  - grok — optional adversarial analyser/critic through the Grok CLI wrapper
  - kimi — optional long-context analyser/critic through the Kimi CLI wrapper
{{INCLUDE:_common-contract.md}}
- Phase 1.5 questions:
  - What user intent and preserved behavior define the proposed change boundary?
  - Which direct and transitive dependencies need impact analysis?
  - Which constraints or open decisions must be passed to implementation-planning?
- Required report blocks:
  - preserved behavior and impacted items
  - dependency propagation with test and operational impact
  - constraints and open decisions for implementation-planning
- Cross-verification mode:
  - Phase 5.5 convergence runs in adversarial mode (`convergence.adversarial=true`).
- Non-goals:
  - source or configuration edits
  - tests, builds, migrations, or deployments
  - implementation alternatives, file change specifications, or execution plans