implement-worktree

To execute an implementation plan in an isolated git worktree, you create a dedicated worktree from your current branch. This prevents changes to the main working directory while enabling safe, phased implementation with per-phase verification.

Validating a plan before modifying your main repository involves running a dry-walkthrough inside an isolated git worktree. This mechanism allows you to explore affected systems with subagents and apply strict prerequisites before actual implementation begins.

Setting up a phased workflow in a git worktree requires committing incremental changes after running per-phase verification tests. This approach supports squash-and-merge workflows by keeping your implementation history clean and isolated.

Yes, using a git worktree for plan implementation directly supports squash-friendly rebase workflows. It commits incremental changes per phase, ensuring your isolated branch is prepared for a clean squash and merge upon completion.

You can explore affected systems with subagents before implementing a plan by using an isolated worktree environment. This ensures your exploration and validation phases do not alter the main working directory during dry-walkthroughs.

You need an isolated git worktree for automation when a plan must be explored, validated, and implemented in phases without altering the main working directory. This is required for running strict prerequisites and per-phase tests safely.