What problem does it solve? Developing multiple SPECs or features on a single Git checkout forces constant branch switching, causes merge conflicts, and blocks parallel work. This Skill creates isolated Git worktrees per SPEC so each feature gets its own workspace, branch, and registry entry without context-switching overhead. ## Core Features & Use Cases - Isolated Worktree Lifecycle: Create, switch, sync, and remove per-SPEC worktrees tracked in a central JSON registry with atomic updates and file locking. - MoAI-ADK Workflow Integration: Works with the /moai plan, /moai run, and /moai sync phases, including the moai cc -w <name> entry pattern and moai worktree done cleanup after PR merges. - Parallel and Team Development: Supports concurrent SPECs, tmux-based teammate spawning via --spawn, selective sync with include/exclude patterns, and conflict resolution strategies. - Use Case: A developer working on SPEC-AUTH-001 and SPEC-PAY-001 simultaneously creates two worktrees, develops each in isolation, syncs both with the base branch, and cleans up merged worktrees automatically. ## Quick Start Ask the assistant to create an isolated worktree for a new SPEC and switch into it to begin parallel development.
