pickup

Resuming an engineering handoff without duplicating work requires loading the handoff file and running a mandatory git state reconciliation. This process verifies pending items against the git log and filters out tasks already shipped before proceeding with execution.

Handoff scope validation is a mandatory safety preflight that ensures workstream correctness before resuming execution. It commits only relevant workstream paths, avoids touching unrelated files, and confirms referenced paths and commits to prevent scope creep.

Preventing concurrent pickup claims is achieved through in-place frontmatter mutation. The system marks the handoff as consumed and records consumed_at and consumed_by metadata, guarding against race conditions when multiple sessions attempt to resume the same work.

Reconciling paused handoff items against git involves verifying pending items with git log, checking plan and stub Status fields, and confirming referenced paths and commits. This mandatory reconciliation filters out completed items before resuming workstream execution.

Yes, this handoff continuation workflow supports PM to EM delegation scenarios. It loads the specified handoff from the tasks directory and proceeds directly to execution without ceremony, satisfying the mandatory safety preflight required for session continuation.

Resuming a paused handoff requires a valid handoff file in the tasks directory with proper Status fields. If the frontmatter is already mutated and marked consumed by a concurrent session, the pickup is blocked to prevent duplicate execution of shipped work.