Creates isolated git worktrees for feature work isolated from main workspace or before implementation plans, with smart directory selection, gitignore safety checks, auto project setup, and baseline tests.
npx claudepluginhub gadaalabs/claude-code-on-steroidsThis skill uses the workspace's default tool permissions.
**VAULT** — *A vault is a sealed, isolated chamber — what happens inside cannot contaminate what's outside.*
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
VAULT — A vault is a sealed, isolated chamber — what happens inside cannot contaminate what's outside. When invoked: creates an isolated git worktree so implementation work is completely separated from the main branch — parallel agents cannot corrupt each other's state, and breaking changes stay contained until verified.
Core principle: Systematic directory selection + safety verification = reliable isolation.
Announce at start: "Running VAULT to set up an isolated workspace."
Follow this priority order:
ls -d .worktrees 2>/dev/null # Preferred (hidden)
ls -d worktrees 2>/dev/null # Alternative
If found: use that directory. If both exist, .worktrees/ wins.
grep -i "worktree.*director" CLAUDE.md 2>/dev/null
If a preference is specified: use it without asking.
If no directory exists and no CLAUDE.md preference:
No worktree directory found. Where should I create worktrees?
1. .worktrees/ (project-local, hidden)
2. ~/.config/superpowers/worktrees/<project-name>/ (global)
Which would you prefer?
MUST verify the directory is gitignored before creating the worktree:
git check-ignore -q .worktrees 2>/dev/null || git check-ignore -q worktrees 2>/dev/null
If NOT ignored — fix immediately:
.gitignoreWhy critical: Prevents accidentally committing worktree contents to the repository.
No .gitignore verification needed — it's outside the project entirely.
project=$(basename "$(git rev-parse --show-toplevel)")
git worktree add "$path" -b "$BRANCH_NAME"
cd "$path"
if [ -f package.json ]; then npm install; fi
if [ -f Cargo.toml ]; then cargo build; fi
if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
if [ -f pyproject.toml ]; then poetry install; fi
if [ -f go.mod ]; then go mod download; fi
# Use the project's test command
npm test / cargo test / pytest / go test ./...
Worktree ready at <full-path>
Tests passing (<N> tests, 0 failures)
Ready to implement <feature-name>
| Situation | Action |
|---|---|
.worktrees/ exists | Use it (verify ignored) |
worktrees/ exists | Use it (verify ignored) |
| Both exist | Use .worktrees/ |
| Neither exists | Check CLAUDE.md → ask user |
| Directory not gitignored | Add to .gitignore + commit first |
| Tests fail at baseline | Report failures + ask before proceeding |
| No package.json / Cargo.toml | Skip dependency install |
Never:
Always:
Called by:
architect — required when design is approved and implementation followsphantom — required before executing any plan tasksexodus — required before executing any plan tasksPairs with:
seal — cleans up the worktree after work is complete