---
name: handoff-packet
description: Prepare detailed, execution-ready handoff documents that transfer work between project areas with clear scope, constraints, acceptance criteria, and next actions. Use when work must be passed from one skill/role/domain to another and the receiver needs a complete, traceable implementation brief.
---

# Handoff Packet

Produce a complete handoff artifact that another AI workflow can execute without guessing.

## Required Inputs
- `AGENTS.md`
- Source artifacts (analysis docs, decisions, tasks, research, specs)
- Target context path (where the next workflow will execute)
- Requested outcome for the receiving workflow

## Workflow
1. Define source scope and target scope explicitly.
2. Extract verified facts, decisions, and non-negotiable constraints from source artifacts.
3. Convert findings into actionable requirements for the receiving workflow.
4. Specify acceptance criteria, exclusions, and measurable success signals.
5. Add implementation guidance, risks, open questions, and validation steps.
6. Produce a final handoff document in a stable template format.

## Quality Gates
- Every requirement traces back to a source artifact.
- Facts are separated from assumptions/recommendations.
- Receiver can act without needing hidden context.
- Acceptance criteria are testable and unambiguous.

## Required Output
- A completed handoff file based on `project_templates/HANDOFF_PACKET.md`.
- A short execution prompt the next workflow can run directly.
- A residual-risk list for unresolved ambiguity.

## Handoff Contract
Include:
- Scope handled.
- Decisions made and why.
- Open risks/blockers.
- Exact handoff target (next skill + expected deliverable).

## Constraints
- Do not invent evidence.
- Do not include vague directives without concrete criteria.
- Keep the packet concise but complete.