TROUBLESHOOTING

Worktree creation failures typically stem from submodule handling, environment copy issues, or policy violations. Identify the specific failure type, apply the remediation template provided in the troubleshooting guide, and use safe rollback steps to recover before retrying delegation to developer agents.

Git worktree conflicts arise from incomplete checkouts, stale references, or simultaneous access. The troubleshooting guide covers detection and recovery steps for each scenario, enabling you to safely remediate and resume skill execution without data loss.

Apply policy checks before worktree creation to prevent constraint violations during strategy execution. This qualifying step ensures your project's technology choices, task prioritization, and requirement analysis align with organizational standards before delegation.

Yes. The skill provides safe rollback and remediation guides that preserve your work during recovery. Follow the step-by-step recovery process to resolve the underlying issue—submodule handling, environment setup, or policy conflict—then retry worktree creation.

Environment copy failures occur when source state doesn't transfer correctly to new worktrees. Use the provided recovery steps to diagnose missing variables, dependency mismatches, or permission problems, then reapply the environment before resuming manager-ready directive generation.