designing-workflow-skillslisted

# Designing Workflow Skills Put workflow control in executable orchestration. Keep core instructions focused on activation, inputs, invariants, safety boundaries, coordinator entry, and direct links to needed resources. ## When to Use Use this skill when creating or refactoring a reusable skill whose behavior needs one or more of: - Branching, bounded concurrency, retries, dependencies, loops, checkpoints, or resume. - Durable state or partial-failure recovery across multiple work items. - Approval immediately before destructive or irreversible actions. - Runtime-neutral setup and pre-flight checks, or adapters for events, external tools, delegated workers, commands, or layered settings. - Progressive disclosure across core instructions, references, scripts, examples, and output assets. - Packaging skills and components as a bundle a host discovers, loads, and distributes. - Merging or consolidating several skills, or folding an upstream skill into an existing one, without losing capability coverage. - Auditing or moving the files of a skill, bundle, or its repository when the current layout contradicts discovery, ownership, or packaging. ## When Not to Use Do not use this skill for: - A single direct task with no reusable workflow contract. - Simple instructions whose order does not branch, retry, resume, or coordinate independent work. - Generic skill copy-editing, one-time skill review, or host-specific syntax lookup without workflow design. - Application orchestrat