action-worktreelisted
Install: claude install-skill tony/ai-workflow-plugins
# this skill
Take one or more tickets to a working branch in its own git worktree.
Resolve the ticket(s) read-only, name the branch the way the team
actually names branches, create the worktree beside the repo (or in a
temp root), implement, and land gated commits — pushing or opening a
PR only when asked.
One worktree, one branch, one deliverable — carrying one ticket by
default, and several when they genuinely share a change. Crosscutting
is first-class, not an error.
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. To land review findings
on the *current* branch, use the `review-address` skill; this command starts
ticket work on a *new* branch.
the `action-worktrees` skill delegates to this file's phases by name and
number. When renaming, renumbering, or reordering phases here, update
that file's references in the same change; on any disagreement
between the two files, this one wins.
## Core thesis
A ticket describes an outcome; a branch is the unit of delivery. This
command is the plumbing between the two, done the way the tracker and
the team already expect: the branch name carries the ticket ID so
linking happens server-side, the worktree keeps the main checkout
untouched, and the gates keep every commit green.
Three disciplines:
1. **Tickets are read-only.** Resolution pulls title, description,
acceptance criteria, and the branch-nam