ralphi-worktree

Guide isolated git worktrees and shared state file updates in Ralphi.

6|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/fagnerjs/ralphi --skill ralphi-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralphi-worktree
Source: https://github.com/fagnerjs/ralphi/tree/main/skills/ralphi-worktree
Command: npx skills add https://github.com/fagnerjs/ralphi --skill ralphi-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of managing code modifications in dedicated worktrees while maintaining clear orchestration state in Ralphi, preventing conflicts and ensuring safe collaboration.

Core Features & Use Cases

  • Worktree Isolation: Guides users on working inside a dedicated git worktree associated with a specific PRD.
  • State Management: Provides instructions for handling shared files like runDir, prd.json, progress.txt, and backlog.json outside the worktree.
  • Use Case: Consider a scenario where a developer needs to implement features for a specific PRD without disrupting the main codebase; this Skill ensures best practices for branch and state management are followed.

Quick Start

Use the ralphi-worktree skill to get instructions for maintaining isolated and clean worktrees during PRD execution.

Frequently Asked Questions about ralphi-worktree

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

FAQPage Schema
How do I manage isolated git worktrees for specific PRD implementation?

To manage isolated git worktrees for PRD implementation, follow best practices for branch inspection and file editing restrictions to prevent conflicts. This ensures code modifications remain dedicated to a specific PRD without disrupting the main codebase.

What shared state files need updates outside of a git worktree?

Shared state files requiring updates outside the git worktree include runDir, prd.json, progress.txt, and backlog.json. Updating these shared files outside the isolated worktree maintains clear orchestration state and ensures safe collaboration.

Why should I avoid editing shared files directly inside a git worktree?

You should avoid editing shared files inside a git worktree because it disrupts orchestration state and causes conflicts. Shared files like prd.json and backlog.json must be updated outside the worktree to ensure consistency and safe collaboration across PRDs.

What is the best way to prevent code conflicts when working on multiple PRDs?

The best way to prevent code conflicts when working on multiple PRDs is using isolated git worktrees. By restricting file edits and managing shared state files separately, you maintain consistency and prevent cross-branch codebase disruptions.

Do I need git worktree isolation for safe code changes during PRD execution?

Yes, you need git worktree isolation for safe code changes during PRD execution. It provides a dedicated branch environment, preventing disruptions to the main codebase while ensuring orchestration state files remain consistent and safe.