# Dot AI Worktree Prd > Create a git worktree for PRD work with a descriptive branch name. Infers PRD from context or asks user. Use when this capability is needed. - Skill: `tomevault-io/dot-ai-worktree-prd` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/dot-ai-worktree-prd` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/dot-ai-worktree-prd/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Product & Planning - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/dot-ai-worktree-prd --- # Create Git Worktree for PRD Create a git worktree with a descriptive branch name based on the PRD title. ## Workflow ### Step 1: Identify the PRD Infer the PRD number from the current conversation. Look for references like "PRD 353", "PRD #353", or "prd-353". If not found, ask the user: "Which PRD should I create a worktree for? (e.g., 353)" ### Step 2: Create the Worktree If the PRD title is already known from conversation context, pass both number and title: ```bash bash .claude/skills/dot-ai-worktree-prd/create.sh [number] "[title]" ``` Otherwise let the script look it up from `prds/`: ```bash bash .claude/skills/dot-ai-worktree-prd/create.sh [number] ``` ### Step 3: Handle Result - If `SUCCESS=true`: report the branch name, worktree path, and suggest `cd [worktree_path]` - If `ERROR=true`: show the errors to the user and ask how to proceed ## Guidelines - **Descriptive names**: Branch names describe the feature, not just the PRD number - **Base on main**: Always branches from `main` for new feature work - **Clean names**: The script keeps branch names concise and URL-safe --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/vfarcic) — claim your Tome and manage your conversions.