What problem does it solve? Starting feature work directly in your main checkout risks polluting your current branch and mixing unrelated changes. This Skill ensures every implementation task begins in an isolated workspace, using your platform's native worktree tools when available and falling back to manual git worktrees otherwise. ## Core Features & Use Cases - Isolation Detection: Checks whether you are already inside a linked worktree or a submodule before creating anything, avoiding duplicate or phantom workspaces. - Native Tool Preference with Git Fallback: Uses harness-provided worktree tools (e.g., EnterWorktree) first, and only runs git worktree add when no native tool exists, with sandbox permission-error fallback. - Safe Directory Selection: Picks .worktrees/ or worktrees/ based on existing conventions, verifies the directory is git-ignored, and commits a .gitignore fix if needed. - Use Case: Before implementing a new feature, the Skill sets up .worktrees/my-feature, installs dependencies (npm, cargo, pip, go), runs the test suite to confirm a clean baseline, and reports the workspace is ready. ## Quick Start Set up an isolated git worktree for my new feature branch and verify the project tests pass before I start implementing.
