Dynamic Workflow Packets

Use this skill to coordinate big work without turning small tasks into process overhead.

Decision Rule

Use packet orchestration when at least two are true:

• The task has independent coding, research, data, UX, security, docs, review, sourcing, or verification tracks.
• A clear success contract would prevent drift.
• The task is risky, broad, expensive, external-facing, or long-running.
• Separate review would likely catch mistakes.
• The workflow pattern may be reused.
• The user explicitly asks for packets, swarm, subagents, dynamic workflow, or orchestration.

If the task is small, do it directly and mention that packet orchestration is unnecessary.

Operating Contract