recursive-worktree

To create an isolated git worktree, this skill bootstraps a feature-branch worktree in a prioritized directory like .worktrees/ to host Phase 0 work, ensuring your main or master branch remains protected from phase-specific changes.

Using a git worktree for recursive-mode branch management provides a clean baseline for your run, enforces a Phase 0 checklist, and records the baseline state in a 00-worktree.md artifact to prevent uncommitted changes from affecting subsequent phases.

You set up a recursive run baseline by applying this skill at the start of a run; it validates a clean baseline, verifies git-ignore rules are respected, and outputs routing readiness guidance to the canonical run directory.

Yes, you can protect your main branch automatically as the skill creates a feature-branch worktree, records the baseline state, and prepares worktree routing without requiring manual git worktree add commands or branch checkout.

If your baseline is not clean, the skill enforces a Phase 0 checklist to verify baseline cleanliness and ensure git-ignore rules are respected before proceeding, preventing uncommitted or untracked files from polluting the isolated worktree.

Yes, the skill outputs a ready 00-worktree.md artifact in the run directory that records the baseline state and provides guidance for subsequent phases, routing, and memory capture during your recursive-mode run.