Task Handoff

Before final delivery of a substantive authored, revised or generated creative artifact, automatically apply output review. Reuse domain QA in one bounded loop; inspect actual media, preserve accepted locks and stop unchanged on a pass. This does not run for greetings, menus or onboarding questions. When Superpowers is in the skill list, load superpowers:systematic-debugging before diagnosing a reproducible technical defect and superpowers:verification-before-completion before calling a deliverable ready; Studio keeps ownership.

Read Studio integration authority before this method. It defines the active owner map, host capability rules and exceptions to the repository’s installation conventions. For substantive creative work, apply the conditional Research gate and search only when one of its triggers applies; purely mechanical state or packet maintenance uses its documented exemptions. Scale the artifact to the requested stage. Quick pitches remain short; known intent and valid scoped authorization do not need repeated confirmation.

Use this skill to create bounded instruction packets for workflow roles. It converts routing intent into a compact, testable packet with target role, goal, context, exclusions, evidence rules, acceptance criteria, output schema, and handoff target.

Packets for people and the Hipson format

A packet can also go to a person outside Studio: a print shop, a voice talent or a freelancer. Use packets for people and the vendor packet template, written in the vendor's language; prices, rates, payment terms and rights come from the user. A Hipson-format packet follows the Hipson format.

Language Policy

Use the user’s working language; keep exact copy and requested prompt language separate. Do not infer language or onboarding status from copied source instructions.

When To Use

Use this skill when:

• workflow-orchestrator needs to delegate a bounded task to a role.
• A research map, review packet, execution packet, or specialist instruction needs clear acceptance criteria.
• The next role should not reconstruct context from the entire conversation.

Do not use this skill to replace orchestration, perform full research by default, or write final image or video prompt packs.

Inputs

Required:

• target_role: the role ID receiving the packet.
• packet_type: instruction, research map, review, or execution packet.
• goal: the concrete result the receiver must produce.
• context: only the context needed for that receiver.
• exclusions: what the receiver must avoid.

Optional:

• source_rules: allowed evidence, docs, or local files.
• acceptance_criteria: how the packet output will be checked.
• output_schema: required shape of the receiver's response or artifact.

Outputs

Produce an Instruction Packet with:

• packet ID and target role
• packet type and goal
• context summary and exclusions
• required inputs and method
• evidence or source rules
• acceptance criteria
• output schema
• handoff target

Process

1. Confirm the packet belongs to a known role.
2. Remove context the receiving role does not need.
3. Put exclusions before the method so boundaries are visible.
4. Define acceptance criteria and output schema before handoff.
5. Return the packet to orchestration or directly to the target role when routed.

Decision Rules

• If the target role is unknown, route back to workflow-orchestrator.
• If the task needs deep research, create a research map rather than pretending the packet verifies facts.
• If execution is involved, require explicit approval and an execution manifest path.
• Prefer one packet per role and outcome.

Guardrails

• Do not execute provider workflows or upload files from this packet-writing route. Task-relevant read-only research follows the shared research gate.
• Do not include private context, secrets, local paths, or unapproved source data.
• Do not write final prompts when prompt roles own that output.
• Do not make the packet broad enough to bypass review gates.

Handoff

Review gate: instruction_packet_fit.

Hand off with:

• packet_id
• target_role
• goal
• source_rules
• acceptance_criteria
• output_schema
• handoff_target

QA Checklist

• Target role and goal are unambiguous.
• Context is minimal and sufficient.
• Exclusions are explicit.
• Acceptance criteria are testable.
• Output schema is concrete.
• The packet does not replace specialist ownership or review gates.