chainlisted

# Chain Orchestrates parallel execution of a dependency sub-DAG. Validates the head task(s), displays the scope tree, executes the head task(s) first, then spawns parallel background agents wave-by-wave for each frontier of ready tasks until the entire chain is complete. > Use `/create-task` for task creation — handles decomposition, deduplication, criteria, and deps. Use `tusk task-insert` only for bulk/automated inserts. ## Arguments Accepts one or more head task IDs and optional flags: `/chain <head_task_id1> [<head_task_id2> ...] [--on-failure skip|abort]` When multiple IDs are provided, all heads are treated as wave 0 (run in parallel), and subsequent waves use the union of their downstream sub-DAGs. ## Flags | Flag | Values | Description | |------|--------|-------------| | `--on-failure` | `skip`, `abort` | Unattended failure strategy applied when an agent finishes without completing its task. **skip** — log a warning and continue to the next wave. **abort** — stop the chain immediately and report all incomplete tasks. Omit for interactive mode (default). | ## Argument Parsing Before Step 1, extract flags from the skill arguments: - Parse `--on-failure <strategy>` from the argument string. Valid values: `skip`, `abort`. - If `--on-failure` is present with a valid value, store it as `on_failure_strategy`. - If `--on-failure` is absent or the value is invalid, `on_failure_strategy` is unset (interactive mode). - The remaining tokens (non-flag values) are the hea