handoff

Cross-functional task handoffs use a HANDOFF ENVELOPE template to capture a Context Pack with Goal, Scope, Constraints, Inputs, Decisions, Open Questions, DoD, and Output Format. This standardizes PM→UX, UX→ARCH, and ARCH→DEV transitions for traceability.

A context pack is a structured data set within a HANDOFF ENVELOPE that captures Goal, Scope, Constraints, Inputs, and Open Questions. You need it during cross-gate workflow transitions to transfer full task context and reduce miscommunication between teams.

Create a handoff envelope by applying the included template to the PM→UX transition, filling in the Context Pack fields such as Goal, Scope, Constraints, and DoD. Include a concrete Task with required Skills and Acceptance Criteria to complete the envelope.

Yes, the handoff template works for PM→UX, UX→ARCH, ARCH→DEV, and other cross-gate transitions. It standardizes communication by ensuring every envelope includes Decisions, Open Questions, Output Format, and concrete Tasks regardless of the workflow stage.

Cross-gate task handoffs should include a HANDOFF ENVELOPE with Goal, Scope, Constraints, Inputs, Decisions, Open Questions, DoD, Output Format, and a concrete Task with required Skills and Acceptance Criteria. This ensures full context transfer and traceability.