action-worktreeslisted

# this skill Fan several tickets out into branches and worktrees. This command owns exactly three things: **discovery** (which tickets), **grouping** (which tickets share a branch), and **fan-out** (parallel subagents or a sequential loop). Everything per-unit — ticket resolution detail, branch naming, worktree creation, implementation, gates, commits, the exit axis — is the `action-worktree` skill's procedure, followed by reference, never restated here. This is a slash command, not a model-invocable skill: it creates worktrees and branches, modifies files, and creates commits, so it must be user-explicit, not router-inferred. ## Core thesis N tickets rarely need N decisions — they need one plan and N executions. The plural command's value is the plan: the right ticket set, the right grouping (1:1 by default, shared branches only on clear overlap), and a fan-out that parallelizes the safe part (implementation inside isolated worktrees) while serializing the unsafe part (mutation of shared git state). Three disciplines: 1. **Delegate, don't duplicate.** The per-unit procedure lives in the `action-worktree` skill and the shared references — this file never paraphrases it. If the two files ever disagree, `worktree.md` wins; if `worktree.md` cannot be read at runtime, stop and say so — never reconstruct its procedure from memory. 2. **Group by evidence, confirm at the gate.** Default 1:1 ticket-to-branch; propose a group only when tickets clearly overla