implementation-handoff

name	implementation-handoff
description	Hand a validated solution to implementation/customer-success owners with architecture, configuration, acceptance evidence, gaps, dependencies, and unresolved risks.

Implementation Handoff

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using PoC evidence, solution brief, customer commitments, product constraints, dependencies, and support model. Do not fill material gaps with assumptions when they can change the result.
3. Reconcile PoC versus production requirements, capture exact artifacts and decisions, list owner-by-owner actions, and identify what must be revalidated at production scale.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

The receiving team can begin implementation without repeating discovery or inheriting hidden promises.