What problem does it solve? Managing multiple feature branches in a single Git working directory causes constant stashing, context switching, and accidental cross-branch contamination. This Skill enforces a disciplined one-branch-per-worktree workflow so parallel development stays isolated and organized. ## Core Features & Use Cases - Worktree Creation Rules: Creates worktrees in sibling directories based on the latest origin/develop, with an immediate git fetch origin to guarantee a fresh baseline. - Naming Conventions: Maps branch names to directory names by replacing slashes with hyphens (e.g., feature/F3.1-ocr-acceleration becomes feature-F3.1-ocr-acceleration). - State Sync & Cleanup: Clarifies that worktrees never share working state or stashes, and defines cleanup rules including removal after merge, 7-day inactivity review, and git worktree prune for orphaned metadata. - Use Case: When starting a hotfix while a feature branch is mid-development, create an isolated worktree via the referenced script, work independently, then remove the worktree and delete the branch after merging. ## Quick Start Ask the AI to create a new Git worktree for a feature branch based on the latest origin/develop using the create-worktree script.