worktree-guide

Explain Git worktree concepts and AI metadata workflows for parallel development.

7|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/poindexter12/waypoint --skill worktree-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-guide
Source: https://github.com/poindexter12/waypoint/tree/main/workflows/skills/working-tree
Command: npx skills add https://github.com/poindexter12/waypoint --skill worktree-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Git worktrees enable parallel development by allowing multiple branches to be checked out in separate directories, but without standardized AI metadata and templates teams can lose track of purpose, scope, and ownership. This Skill provides a structured guide for managing Git worktrees and their AI context, including templates, mode semantics, naming conventions, and best practices to improve discoverability, consistency, and safety.

Core Features & Use Cases

  • AI-context metadata templates and guidance for each worktree (e.g., .ai-context.json and README.working-tree.md) to document intent and history.
  • Mode semantics and naming conventions to influence AI behavior and team workflows across main, feature, bugfix, experiment, and review worktrees.
  • Comprehensive references and example workflows to accelerate adoption and ensure consistent practices across the repository.

Quick Start

Create a new feature worktree with a descriptive description by running /working-tree:new feature/<name> --mode feature --description 'Describe the feature'

Frequently Asked Questions about worktree-guide

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

FAQPage Schema
How do I manage AI context across multiple git worktrees?

Standardize git worktree management by defining mode semantics for feature, bugfix, experiment, and review branches. These modes influence AI behavior and enforce consistent naming conventions, ensuring parallel development workflows remain organized and predictable across the repository.

What is the best way to structure parallel development with git worktrees?

Structure parallel development with git worktrees by using provided templates and reference materials to establish ownership and scope. Applying standardized metadata workflows streamlines feature work and experiments, preventing teams from losing track of branch purpose across separate directories.

How do I create a new feature worktree with AI metadata?

Git worktree management requires a git environment and applies to teams using multiple checked-out branches for parallel development. It is suited for repositories needing structured AI context and standardized metadata workflows to maintain consistency across feature, bugfix, and review directories.

Why do I need metadata templates for git worktrees?

Metadata templates for git worktrees are needed to prevent teams from losing track of branch purpose, scope, and ownership. Without standardized AI context files, discoverability and safety suffer when multiple branches are checked out simultaneously in separate directories.

When should I avoid using git worktrees for parallel development?

Avoid using git worktrees for parallel development if your repository lacks standardized AI metadata practices. Without consistent naming conventions and context files, managing multiple working directories can lead to disorganized histories and lost AI awareness across complex workflows.