Instruction Packet Factory
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.
Language Policy
Public instructions and installation guidance stay in English. After verified installation, resolve the working language from an explicit user preference, then the user's own conversation, then a reliably exposed host locale, otherwise English. Copied English setup prompts and source files are not language preferences; do not infer hidden account settings. Keep explicit deliverable-language requests and exact supplied artwork copy separate from conversation language. Do not translate or rewrite public source files to localize a session.
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
- Confirm the packet belongs to a known role.
- Remove context the receiving role does not need.
- Put exclusions before the method so boundaries are visible.
- Define acceptance criteria and output schema before handoff.
- 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 tools, upload files, or run provider workflows.
- 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.
1---2name: instruction-packet-factory3description: Use this skill to create bounded instruction packets, research maps, internet mapping packets, review packets, and execution packets for role-based workflow agents.4metadata:5 source: https://skillmd.com/skills/framecoreworks/instruction-packet-factory6---78# Instruction Packet Factory910Use 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.1112## Language Policy1314Public instructions and installation guidance stay in English. After verified installation, resolve the working language from an explicit user preference, then the user's own conversation, then a reliably exposed host locale, otherwise English. Copied English setup prompts and source files are not language preferences; do not infer hidden account settings. Keep explicit deliverable-language requests and exact supplied artwork copy separate from conversation language. Do not translate or rewrite public source files to localize a session.1516## When To Use1718Use this skill when:1920- `workflow-orchestrator` needs to delegate a bounded task to a role.21- A research map, review packet, execution packet, or specialist instruction needs clear acceptance criteria.22- The next role should not reconstruct context from the entire conversation.2324Do not use this skill to replace orchestration, perform full research by default, or write final image or video prompt packs.2526## Inputs2728Required:2930- `target_role`: the role ID receiving the packet.31- `packet_type`: instruction, research map, review, or execution packet.32- `goal`: the concrete result the receiver must produce.33- `context`: only the context needed for that receiver.34- `exclusions`: what the receiver must avoid.3536Optional:3738- `source_rules`: allowed evidence, docs, or local files.39- `acceptance_criteria`: how the packet output will be checked.40- `output_schema`: required shape of the receiver's response or artifact.4142## Outputs4344Produce an Instruction Packet with:4546- packet ID and target role47- packet type and goal48- context summary and exclusions49- required inputs and method50- evidence or source rules51- acceptance criteria52- output schema53- handoff target5455## Process56571. Confirm the packet belongs to a known role.582. Remove context the receiving role does not need.593. Put exclusions before the method so boundaries are visible.604. Define acceptance criteria and output schema before handoff.615. Return the packet to orchestration or directly to the target role when routed.6263## Decision Rules6465- If the target role is unknown, route back to `workflow-orchestrator`.66- If the task needs deep research, create a research map rather than pretending the packet verifies facts.67- If execution is involved, require explicit approval and an execution manifest path.68- Prefer one packet per role and outcome.6970## Guardrails7172- Do not execute tools, upload files, or run provider workflows.73- Do not include private context, secrets, local paths, or unapproved source data.74- Do not write final prompts when prompt roles own that output.75- Do not make the packet broad enough to bypass review gates.7677## Handoff7879Review gate: `instruction_packet_fit`.8081Hand off with:8283- `packet_id`84- `target_role`85- `goal`86- `source_rules`87- `acceptance_criteria`88- `output_schema`89- `handoff_target`9091## QA Checklist9293- Target role and goal are unambiguous.94- Context is minimal and sufficient.95- Exclusions are explicit.96- Acceptance criteria are testable.97- Output schema is concrete.98- The packet does not replace specialist ownership or review gates.