retry-worktree

To resume git worktree implementation after context exhaustion, provide the paths to the original plan file and the pre-existing worktree. The skill assesses prior progress and continues development seamlessly without redundant setup.

The best way to continue a cut-short git worktree session is to use a resumption skill that reads the existing worktree state and original plan. This avoids data loss and prevents starting the implementation over from scratch.

Yes, you need the original plan file path to resume work in an existing git worktree. The plan file is required to accurately assess progress and ensure continuity by leveraging existing work without redundant exploration.

You can pick up implementation exactly where the AI left off without starting over by targeting the pre-existing worktree. This specifically addresses context exhaustion issues from prior sessions to prevent wasted effort.

Resuming a git worktree task avoids redundant exploration because it leverages the existing work already completed in the worktree. By reading the original plan and current state, it ensures continuity and skips unnecessary setup steps.