worktree
Git Worktree Management
Iron Law
NEVER MODIFY FILES IN A WORKTREE YOU DID NOT CREATE
Operations
1. Create
Create a new worktree for isolated parallel development.
git worktree add <path> -b <branch-name>
- Always use a descriptive branch name matching the worktree purpose
- Place worktrees in a consistent location (e.g.,
/tmp/<repo>-worktrees/<name>) - Verify the worktree was created successfully before proceeding
- Initialize any required workspace files (progress.txt, CLAUDE.md, prd.json)
More from scando1993/sugar
ralph
Convert PRDs to prd.json format for the Ralph autonomous agent system. Use when you have an existing PRD and need to convert it to Ralph's JSON format. Triggers on: convert this prd, turn this into ralph format, create prd.json, ralph json.
12respond-review
Guidance for receiving and responding to code review feedback. Use when addressing PR review comments, incorporating reviewer suggestions, or managing review discussions.
12tdd
Test-driven development with strict RED-GREEN-REFACTOR enforcement. Enforces: write failing test first, minimal implementation, then refactor. Use when adding new features or fixing bugs.
11debug
Systematic debugging with hypothesis-driven investigation. Use when diagnosing bugs, errors, or unexpected behavior. Phases: Reproduce, Hypothesize, Investigate, Fix, Verify, Regression.
11prd
Generate a Product Requirements Document for a feature. Use when planning a feature, starting a project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
11finish
Branch finishing and PR preparation. Use when completing a feature branch, preparing a pull request, or cleaning up commit history.
11