implement-worktree

To implement a feature plan using an isolated git worktree, run the implement-worktree command with a plan file path like .swarm/plans/my-feature.md. This creates a dedicated worktree, derives branches, and runs validations to prevent cross-branch contamination during feature development.

Using isolated git worktrees is the best way to prevent cross-branch contamination during feature implementation. This approach creates separate working directories for each feature, ensuring parallel development and automated validation steps do not interfere with the main branch.

A worktree workflow handles E2E test scaffolding and code review by generating end-to-end test scaffolding automatically and enabling parallel review workflows. It tracks progress through phase-based checkpoints and updates a registry before merging feature changes.

Yes, you need plan files stored under the .swarm/plans directory to use a plan-driven worktree workflow. The system derives branch and worktree details from these plan files to update the .swarm/workstreams.json registry and manage phase-based progress.

Yes, you can run parallel reviews and checkpoints in a git worktree setup. The workflow applies automated validation steps and registry-backed plan tracking to ensure thorough code review and human-readable documentation are completed before merging changes.