worktree-workflow

Name: worktree-workflow
Availability: InStock
Author: brmatola

Orchestrate multi-phase development loops across a git worktree with persistent state.

Updated Jan 17, 2026

Search Tags:#automation #git #workflow #planning #development #worktree

Ready to run

npx skills add https://github.com/brmatola/gremlins --skill worktree-workflow-brmatola

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktree-workflow
Source: https://github.com/brmatola/gremlins/tree/main/skills/worktree-workflow
Command: npx skills add https://github.com/brmatola/gremlins --skill worktree-workflow-brmatola

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams orchestrate the full development loop across a git worktree, enabling multi-phase planning, implementing, reviewing, and optional reach exploration with persistent state.

Core Features & Use Cases

Stateful orchestration: track progress across sessions and branches with a central .workflow-state.json.
Phase-driven workflow: start with plan readiness, proceed to implement, audit, and optional reach exploration via sub-skills.
Safe completion: synchronize with the base branch before finishing and provide clear decision points for continuing or finishing.

Quick Start

Use the worktree-workflow skill to start a new plan named "feature-xyz" and follow the prompts to proceed through plan readiness, implementation, audit, and optional reach steps.

Frequently Asked Questions about worktree-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain persistent state across multiple git worktree sessions?▼

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.

What is the best way to orchestrate a multi-phase development loop in git?▼

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.

How do I start a new automated workflow plan in a git 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.

Can I synchronize my worktree branch with the base branch before finishing development?▼

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.

Does the worktree workflow support aborting an in-progress development loop?▼

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.