Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows
docs(skills): make /wt-switch-create worktree creation unconditional (#3356)
Maximilian Roos552cc1be6c9e
diff --git a/skills/wt-switch-create/SKILL.md b/skills/wt-switch-create/SKILL.mdindex 5400ebb93..87828bcfc 100644--- a/skills/wt-switch-create/SKILL.md+++ b/skills/wt-switch-create/SKILL.md@@ -33,7 +33,9 @@ branch-shaped lead — all task).## What to do-Steps 1–3 come before any other work.+Steps 1–3 run on every invocation, before any other work. The invocation is+itself the explicit request to create the worktree; a research or read-only+task gets one all the same.<!-- Maintainers: rationale.md (same directory) covers the harness rules anddesign choices behind this — read it before re-adding guards or routes. -->@@ -99,6 +101,6 @@ entered by `path`, so removal is always `wt remove <branch>`.## Scope-This command authorizes creating/entering ONE worktree (in the named repo, if-one was given) and doing the requested task. Commits, pushes, and merges still-each require explicit user permission.+The command's mandate is ONE worktree (in the named repo, if one was given)+and the requested task inside it. Commits, pushes, and merges still each+require explicit user permission.diff --git a/skills/wt-switch-create/rationale.md b/skills/wt-switch-create/rationale.mdindex 9349225c0..3dbb2ebb4 100644--- a/skills/wt-switch-create/rationale.md+++ b/skills/wt-switch-create/rationale.md@@ -36,6 +36,17 @@ deliberately omitted — they re-minify every build.Two independent harness facts underlie this — re-root is repo-scoped, and `cd`persistence is working-directory-membership-scoped — detailed below.+## Why creation is unconditional++The recurring failure: handed a research or read-only task, the model decided+it didn't need isolation and skipped creation. Two wordings fed that. Scope's+"authorizes" read as permission, inviting a should-I test (user-level rules+that gate worktree creation behind an explicit request answer it "no"); an+ordering-only lead ("steps 1–3 come first") doesn't bind a model that decided+the steps don't apply. So the lead makes the invocation the explicit request+itself, and Scope states bounds rather than permission. Don't reintroduce+either wording.+## wt CLI and git behavior (all live-tested)- `wt switch --create <branch>` exits 1 with `✗ Branch <branch> already