# Mission: Use Git Worktrees for Parallel Coding Safely

## Why
Work on more than one branch without stashing, recloning, or losing the state of an unfinished task. The practical outcome is a repeatable workflow for isolated coding, review, testing, integration, and cleanup in one repository.

## Success looks like
- Explain what a linked worktree shares with the main worktree and what it keeps separate.
- Create a task worktree on a clearly named branch and inspect it before making destructive decisions.
- Integrate a finished branch through merge or cherry-pick, with a deliberate verification point.
- Remove clean worktrees, recover from a moved or missing path, and recognize when a lock is appropriate.
- Run two small tasks in parallel without checking the same branch out twice or discarding uncommitted work.

## Constraints
- Use the official Git documentation as the primary source.
- Prefer a sibling-directory layout so every task path is obvious.
- Treat force, branch deletion, and manual folder removal as decisions that require inspection first.
- Keep lessons short, interactive, and useful for a real repository.

## Out of scope
- Replacing the repository's contribution, review, or release process.
- Repairing damaged Git object databases.
- Making submodule-heavy repositories a default worktree workflow.