worktree-workflow

To maintain persistent state across git worktree sessions, this workflow uses a central .workflow-state.json file to track progress across branches, enabling you to resume multi-phase development loops seamlessly.

Orchestrating a multi-phase development loop in git is best handled by applying a structured workflow that enforces sequential phases: plan readiness, implementation, auditing, and optional reach exploration across a dedicated worktree.

To start a new automated workflow plan in a git worktree, you issue a start command with a plan name, which triggers plan readiness checks before proceeding to autonomous implementation and auditing sub-skills.

Yes, you can synchronize your worktree branch with the base branch before finishing development, which ensures safe completion and provides clear decision points for either continuing the loop or finalizing the workflow.

Yes, the worktree workflow supports aborting an in-progress development loop by exposing a dedicated abort command, allowing you to safely exit the current multi-phase planning and implementation state.