worktrees

What problem does it solve? Managing parallel branches, risky refactors, or background agent work in a single Git checkout leads to context switching, half-committed states, and broken working environments. This Skill provides a safe, structured protocol for creating and managing Git worktrees as isolated coding lanes. ## Core Features & Use Cases - Isolated Lane Management: Creates worktrees under .slim/worktrees/<slug>/ with branch naming conventions and a .slim/worktrees.json manifest for tracking lane state, ownership, and status. - Safety Guardrails: Enforces pre-flight checks, mandatory user confirmation before destructive Git operations, and managed .gitignore/.ignore blocks to keep lane artifacts local. - Full Lifecycle Workflow: Covers planning, delegation to sub-agents, diff validation, integration, and cleanup across four defined phases. - Use Case: You need to refactor an authentication flow while keeping your main checkout stable. The Orchestrator creates a worktree lane, assigns a specialist agent to work inside it, validates the diff against the base branch, and merges only after your approval. ## Quick Start Ask the Orchestrator to create a worktree lane for your task, for example: set up an isolated worktree to refactor the authentication module on a new branch.