Assessment

Auto review

Inventory what's being migrated, identify risks and dependencies

Hats
2
Review Agents
1
Review
Auto
Unit Types
Assessment
Inputs
None

Hat Sequence

1

Migration Analyst

Focus: Inventory every artifact in scope — schemas, data stores, services, integrations, jobs, and configuration. Produce a complete catalog with size estimates, ownership, and inter-system dependencies. Nothing can be migrated safely if it isn't inventoried first.

Produces: Migration inventory with artifact catalog, dependency graph, and size/volume estimates.

Reads: Intent problem statement, source system documentation, existing architecture diagrams.

Anti-patterns (RFC 2119):

  • The agent MUST NOT declare the inventory complete without verifying against the live system
  • The agent MUST NOT ignore ancillary systems (cron jobs, caches, queues) that depend on the source
  • The agent MUST NOT list artifacts without documenting their relationships
  • The agent MUST NOT assume the documentation matches the actual deployed state
  • The agent MUST NOT skip volume estimates that affect migration strategy (bulk vs. incremental)
2

Risk Assessor

Focus: Identify what can go wrong — data loss vectors, downtime windows, compatibility gaps, and blast radius. Assign severity and likelihood to each risk and propose concrete mitigations. Surface ordering constraints that determine which parts must migrate first.

Produces: Risk register with categorized risks, severity/likelihood ratings, mitigation strategies, and migration ordering constraints.

Reads: Migration inventory from the migration-analyst, source and target platform constraints.

Anti-patterns (RFC 2119):

  • The agent MUST NOT list risks without mitigation strategies
  • The agent MUST NOT treat all risks as equal severity
  • The agent MUST NOT ignore the human/process risks (team readiness, tribal knowledge, manual steps)
  • The agent MUST NOT assume rollback is always possible without verifying
  • The agent MUST NOT overlook data in transit during the migration window

Review Agents

Risk Coverage

Mandate: The agent MUST verify all migration risks and dependencies are identified.

Check:

  • The agent MUST verify that every system, data store, and integration in the migration scope is inventoried
  • The agent MUST verify that dependencies between migrated components are mapped (migration order matters)
  • The agent MUST verify that risk assessment covers data loss, downtime, and functional regression scenarios
  • The agent MUST verify that rollback feasibility is assessed for each component

Assessment

Criteria Guidance

Good criteria examples:

  • "Inventory covers all source tables/services with row counts and dependency mappings"
  • "Risk register identifies at least 3 categories (data loss, downtime, compatibility) with severity ratings"
  • "Dependency graph shows which systems must migrate in sequence vs. parallel"

Bad criteria examples:

  • "Assessment is complete"
  • "Risks are documented"
  • "Systems are inventoried"

Completion Signal (RFC 2119)

Migration inventory MUST exist with a complete catalog of source artifacts (schemas, services, data stores, integrations). Risk register identifies each risk with severity, likelihood, and mitigation strategy. Dependency graph shows migration ordering constraints and parallel opportunities.