By name: handoff-ingestion description: Ingest handoff packets and convert cross-domain instructions into execution-ready engineering requirements, implementation plans, and validation criteria. Use when receiving work from strategy, operations, finance, growth, sales, legal, or research workflows that must be translated into concrete engineering tasks.
Handoff Ingestion
Convert incoming handoff artifacts into engineering-ready execution plans with no ambiguity.
Required Inputs
AGENTS.md- Incoming handoff packet (prefer
project_templates/HANDOFF_PACKET.mdformat) - Related project context (
project_templates/PROJECT_CONTEXT.md) - Applicable decisions, constraints, and learning entries
Workflow
- Parse handoff scope, target outcome, and non-negotiable constraints.
- Separate facts from assumptions and unresolved questions.
- Translate cross-domain requests into engineering requirements.
- Define implementation plan with milestones, owners, dependencies, and sequencing.
- Define test/validation criteria and go/no-go conditions.
- Publish execution artifacts and escalation questions.
Translation Rules
- Convert business goals into system behavior and measurable acceptance criteria.
- Map vague language into explicit constraints (performance, security, cost, reliability).
- Preserve intent while removing ambiguity.
- Flag conflicts between handoff requests and existing architecture/constraints.
Required Output
- Engineering interpretation summary
- Requirements list with traceability to handoff sources
- Implementation plan (phased)
- Validation and test plan
- Open questions and escalation items
Quality Gates
- Each engineering requirement traces to a source statement.
- Assumptions are explicit and minimal.
- Validation criteria are objective and testable.
- Risks and blockers include owner and next action.
Constraints
- Do not silently reinterpret critical requirements.
- Do not proceed with contradictory constraints; escalate.
- Do not remove compliance/safety constraints during translation.