agentleFS
vfarcicvfarcic/dot-ai/.claude/skills/dot-ai-worktree-prd/SKILL.md

dot-ai-worktree-prd

Skill336 starsChanged 10 months agoMITView on GitHub

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

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a git worktree with a descriptive branch name based on the PRD title.

    line 9
  2. Distinctive:

    If not found, ask the user: "Which PRD should I create a worktree for?

    line 17
  3. Distinctive:

    If the PRD title is already known from conversation context, pass both number and title:

    line 21
  4. Distinctive:

    If the source file doesn't exist, skip this step silently.

    line 38
  5. Very specific:

    If SUCCESS=true: report the branch name, worktree path, and suggest cd [worktree_path]

    line 42
  6. Very specific:

    If ERROR=true: show the errors to the user and ask how to proceed

    line 43
  7. Distinctive:

    Base on main: Always branches from main for new feature work

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 .claude/skills/dot-ai-worktree-prd/create.sh [number] "[title]"

Otherwise let the script look it up from prds/:

bash .claude/skills/dot-ai-worktree-prd/create.sh [number]

Step 3: Copy Local Settings

Copy .claude/settings.local.json from the main repo to the new worktree so local settings (which are not tracked in git) are available:

cp .claude/settings.local.json [worktree_path]/.claude/settings.local.json

If the source file doesn't exist, skip this step silently.

Step 4: 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.