What problem does it solve? Starting feature work directly in your main checkout risks polluting your current branch, mixing unrelated changes, and losing track of experimental edits. This Skill ensures every implementation task begins in a verified isolated workspace, with a clean test baseline, before any code changes happen. ## Core Features & Use Cases - Isolation Detection: Checks whether you are already inside a linked git worktree (with a submodule guard) before creating anything, preventing nested worktrees. - Native-Tool-First Strategy: Prefers platform-native isolation such as a clean subagent context (e.g. sessions_spawn) and falls back to git worktree add only when filesystem-level isolation is required. - Safe Worktree Creation: Selects the worktree directory by priority (explicit preference > existing .worktrees/ or worktrees/ > default), verifies it is git-ignored, and handles sandbox permission errors gracefully. - Baseline Verification: Auto-detects the project type (Node, Rust, Python, Go), installs dependencies, and runs the test suite to confirm a clean starting point. - Use Case: Before implementing a new checkout feature, run this Skill to spin up an isolated workspace on a fresh branch, install dependencies, and confirm all existing tests pass. ## Quick Start Set up an isolated workspace for my new feature branch and verify the test baseline is clean before I start implementing.
