What problem does it solve? Setting up isolated git worktrees for parallel development is repetitive and error-prone: fresh checkouts miss gitignored env files, dependencies, and runtime configuration, and doing it for several branches serially wastes time. ## Core Features & Use Cases - Parallel worktree provisioning: Fans out one setup subagent per branch so multiple worktrees are created, configured, and verified concurrently. - Repo-detected setup: Detects the package manager, gitignored env/config files, health-check command, and port assignments from the repository itself rather than hardcoding a stack. - Health verification and reporting: Runs a detected health check per worktree and reports a per-worktree summary with cleanup instructions. - Use Case: You need to run three PIV loops on separate feature branches at once; invoke the skill with the branch names and receive three ready-to-use worktrees, each with dependencies installed and a passing health check. ## Quick Start Ask the agent to set up worktrees for your feature branches, for example by saying "create worktrees for branches feature-a and feature-b".