Worktree Manager

Create and tear down git worktrees that follow Kanopi's branch conventions and stay isolated at the DDEV layer, so multiple tickets — and multiple AI sessions — can run side by side from a single clone.

Why this exists

A worktree checks out a second branch into its own directory while sharing one .git. That is the primitive that lets two Claude Code sessions (or one CLI session and one Claude Desktop "code" session) work different tickets at the same time without git checkout thrash or stepping on each other's files. It maps one-to-one onto Kanopi's "one branch per ticket" rule.

Usage

• /worktree-manager create <ticket-id> <short-desc> [--type feature|bug|hotfix] [--base main] — create a worktree + branch
• /worktree-manager list — show active worktrees and their DDEV status
• /worktree-manager remove <ticket-id> — tear down a worktree (destructive; requires confirmation)

If the user gives a Teamwork URL or task ID, parse the numeric ID from it (e.g. tw1234).

Naming convention

Branch (unchanged from Kanopi standards):