Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

$pwd:

worktree-prd

Name: Worktree Prd
Author: vfarcic

// Create a git worktree for PRD work with a descriptive branch name. Infers PRD from context or asks user.

In Manus ausführen

$ git log --oneline --stat

stars:1

forks:0

updated:29. Januar 2026 um 02:05

Datei-Explorer

2 Dateien

SKILL.md

readonly

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

related-skills.json

gleiches Repository

request-dot-ai-feature.md

from "vfarcic/dot-ai-skills"

Generate a feature request prompt for another dot-ai project. Use when you need a feature implemented in a sibling project (MCP server, controller, etc.) to unblock work in the current project.

2026-01-291

changelog-fragment.md

from "vfarcic/dot-ai-skills"

Create changelog fragment for release notes. Invoke during /prd-done workflow during the first push to the PR.

2026-01-281

process-feature-request.md

from "vfarcic/dot-ai-skills"

Process a feature request or response from another dot-ai project. Reads from tmp directory, implements/integrates, and writes response if needed.

2026-01-281

query-dot-ai.md

from "vfarcic/dot-ai-skills"

Query sibling dot-ai projects to verify features are USABLE (not just defined). IMPORTANT: When calling this skill, explain HOW you plan to use the feature (e.g., 'I need to call X via REST API from the UI' or 'I need to import Y function'). This helps verify the full chain from definition to exposure.

2026-01-281

tag-release.md

from "vfarcic/dot-ai-skills"

Create a release tag based on accumulated changelog fragments. Run when ready to cut a release.

2026-01-281

package.json

"author": "vfarcic"

"repository": "vfarcic/dot-ai-skills"

GitHub-Repository öffnen Creator-Repositorys ansehen

$ install --global

$ download --local

In Manus ausführen

$ useful --forSOC

SoftwareentwicklerInformatik- und Mathematikberufe15-1252L4

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

worktree-prd

Create Git Worktree for PRD

Workflow

Step 1: Identify the PRD

Step 2: Get the PRD Title

Step 3: Generate Descriptive Branch Name

Step 4: Create the Worktree

Guidelines

Mehr aus diesem Repository

Mehr aus diesem Repository

Create Git Worktree for PRD

Workflow

Step 1: Identify the PRD

Step 2: Get the PRD Title

Step 3: Generate Descriptive Branch Name

Step 4: Create the Worktree

Guidelines