Evaluating a Handoff Before Automated Resume

Problem Description

A development team uses an automated pipeline that resumes agent tasks using handoff packets. Before resuming, a pre-flight check is run to ensure the handoff can actually be acted on — not just that the fields are filled in, but that the documented state is coherent and the work can continue without confusion.

One handoff has been flagged for manual review before the automated system is allowed to proceed. The pipeline manager wants a full integrity assessment of the packet, particularly whether the documented state is clear enough for a new agent to confidently pick up the work.

Output Specification

Write your integrity assessment to integrity-report.md. The pipeline manager needs to know whether this session can be safely resumed and, if not, exactly what is wrong with the documented state.

Input Files

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

=============== FILE: handoff.json =============== { "objective": "Complete the OAuth2 integration for the mobile app authentication flow", "completed": [ "Completed full OAuth2 integration for mobile app", "All authentication endpoints live in production", "QA sign-off received on authentication flow" ], "unresolved": [ "No blockers — all work is complete" ], "assumptions": [ "Mobile app v4.2 is the target release" ], "next_action": "Begin OAuth2 integration — start with the authorization code flow endpoint", "risks": [ "Token refresh logic has not been tested under high concurrency" ], "updated_at": "2025-11-28T08:00:00Z", "resume_token": "oauth2-mobile-sess-9pQr4mV7" }