handoff-ingestion

name: handoff-ingestion description: Validate and operationalize incoming handoff packets into execution-ready plans by checking completeness, resolving ambiguities, mapping requirements to concrete tasks/files/tests, and producing blocker/risk reports with clear next actions.

Handoff Ingestion

Process inbound handoff packets before execution starts.

Required Inputs

• AGENTS.md
• Target PROJECT_CONTEXT.md
• Incoming handoff packet (prefer HANDOFF_PACKET.md)

Workflow

1. Confirm objective, in-scope boundaries, and out-of-scope exclusions.
2. Validate packet completeness and classify issues as blocker, warning, or info.
3. Detect contradictions across requirements, constraints, and acceptance criteria.
4. Convert validated requirements into an ordered execution plan.
5. Map each task to requirement IDs, owner role/skill, and verification steps.
6. Produce a receiver-ready prompt for the next lead skill.

Validation Checklist

• Objective is explicit and actionable.
• Source artifacts are listed and traceable.
• In-scope and out-of-scope boundaries are defined.
• Requirements include source and priority.
• Acceptance criteria are testable.
• Constraints and no-go changes are explicit.
• Risks, assumptions, and open questions are present.

Required Output

• Ingestion report containing:
  • Packet quality score (0-100) with rationale.
  • blocker/warning/info findings.
  • Requirement-to-task mapping table.
  • Recommended execution sequence.
  • Open questions that must be resolved pre-implementation.
• Ready-to-run prompt for next lead skill.

Handoff Contract

Include:

• Scope handled.
• Decisions made and why.
• Open risks/blockers.
• Exact handoff target (next skill + expected deliverable).

Constraints

• Do not invent missing facts.
• Do not implement features/code during ingestion.
• Keep every recommendation evidence-linked to packet content.