Pre-Rotation Handoff Review

Problem Description

A backend engineer is rotating off a Kubernetes cluster migration project after completing the first two phases. They left a handoff document for the incoming engineer, who needs to pick up the work tomorrow morning. Before any work resumes, the team lead wants a thorough review of the handoff to confirm it's in good shape.

The incoming engineer has never seen the project before. If the handoff is incomplete or unclear, they'll be blocked immediately — so catching any problems now is critical. The review needs to assess whether the handoff is genuinely ready to act on, not just whether a file exists.

Output Specification

Produce a file named handoff-review.md containing a structured review of the handoff packet. The review must assess each relevant dimension of the handoff and conclude with an overall status and what (if anything) needs to be done before the incoming engineer can safely start.

Input Files

The following files are provided as inputs. Extract them before beginning.

=============== FILE: handoff.json =============== { "objective": "Complete Kubernetes cluster migration from v1.24 to v1.29 across all production namespaces", "completed": [ "Audited all existing workloads and resource quotas", "Upgraded dev and staging clusters to v1.28" ], "unresolved": [ "Production namespace 'payments' has a deprecated PodSecurityPolicy that must be migrated before upgrade" ], "assumptions": [], "next_action": "", "risks": [ "PodSecurityPolicy removal in v1.25 — replacement PSA labels not yet applied to all namespaces", "Rollback window is limited to 4 hours per the maintenance contract" ], "updated_at": "2025-11-04T09:15:00Z", "resume_token": "k8s-migrate-prod-v3-xK9mN2" }