| name | worktree-prd |
| description | Create a git worktree for PRD work with a descriptive branch name. Infers PRD from context or asks user. |
Create Git Worktree for PRD
Create a git worktree with a descriptive branch name based on the PRD title. This ensures feature branches have human-readable names that describe what the work is about.
Workflow
Step 1: Identify the PRD
Try to infer the PRD number from the current conversation. Look for PRD references like "PRD 353", "PRD #353", or "prd-353".
If not found in context, ask the user: "Which PRD should I create a worktree for? (e.g., 353)"
Step 2: Get the PRD Title
If the PRD content is already in the conversation context, extract the title from there.
Otherwise, read the PRD file. PRD files are in the prds/ directory with naming pattern [number]-[slug].md:
ls prds/ | grep "^[PRD_NUMBER]-"
The title is on the first line in format: # PRD #[number]: [Title]
Step 3: Generate Descriptive Branch Name
Convert the PRD title to a branch-friendly name:
- Start with
prd-[number]-
- Extract the title after the colon (e.g., "Update to Kimi K2.5 Model Support")
- Convert to lowercase
- Replace spaces with hyphens
- Remove special characters except hyphens and dots
- Keep it concise (truncate if very long)
Examples:
- "PRD #353: Update to Kimi K2.5 Model Support" →
prd-353-kimi-k2.5-support
- "PRD #290: Skills Distribution System" →
prd-290-skills-distribution
- "PRD #264: GitOps Tool ArgoCD Integration" →
prd-264-gitops-argocd-integration
Step 4: Create the Worktree
Run the create-worktree.sh script from this skill's directory:
.claude/skills/worktree-prd/create-worktree.sh [branch-name]
The script will:
- Check if the branch or worktree already exists (exits with error if so)
- Get the repository name dynamically
- Create the worktree at
../${repo_name}-${branch-name}
- Initialize submodules in the new worktree
- Output the path and instructions for the user
If the script fails due to existing branch/worktree, inform the user and ask how to proceed.
Guidelines
- Descriptive names: Branch names should describe the feature, not just the PRD number
- Consistent format: Always prefix worktree directory with the repository name
- Base on main: Always branch from
main for new feature work
- Clean names: Keep branch names concise but descriptive
