dot-ai-worktree-prd

Create a Git worktree with a PRD-derived branch name from main.

2|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/vfarcic/dot-ai-website --skill dot-ai-worktree-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dot-ai-worktree-prd
Source: https://github.com/vfarcic/dot-ai-website/tree/main/.claude/skills/dot-ai-worktree-prd
Command: npx skills add https://github.com/vfarcic/dot-ai-website --skill dot-ai-worktree-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating new Git worktrees by automatically generating descriptive branch names based on Product Requirement Documents (PRDs), ensuring clarity and consistency in feature development.

Core Features & Use Cases

  • Automated Branch Naming: Generates human-readable branch names derived from PRD titles.
  • Worktree Creation: Creates new Git worktrees branching from main.
  • Submodule Initialization: Automatically initializes submodules within the new worktree.
  • Use Case: When starting work on a new feature defined by PRD #353, "Update to Kimi K2.5 Model Support", this Skill will create a worktree with a branch named prd-353-kimi-k2.5-support.

Quick Start

Create a git worktree for PRD 353.

Frequently Asked Questions about dot-ai-worktree-prd

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

FAQPage Schema
How do I create a git worktree from a PRD?

You can create a git worktree from a PRD by providing the PRD number or context; the tool extracts the title, generates a descriptive branch name, validates paths, and adds the worktree branching from `main`.

How does automated branch naming work for feature development?

Automated branch naming extracts the PRD title and generates a standardized branch name, ensuring clarity and consistency across feature development workflows without manual naming.

Can I initialize git submodules when adding a new worktree?

Submodule initialization is handled automatically during worktree creation, ensuring dependencies are present in the new working directory immediately.

What is the best way to manage feature branches for product requirements?

Using git worktrees with descriptive names derived from PRD titles ensures isolated development environments and clear branch identification compared to standard branching.

Does git worktree creation validate existing branches before adding a new one?

The tool checks for existing branch names and worktree paths before creation to ensure no conflicts arise during the setup of the new working directory.

Do I need a Product Requirement Document to generate a worktree?

A PRD is required because the branch name is extracted from the document title; if not found in context, the tool will prompt you to provide it.