Initialize a new feature workflow with git worktree. Use when the user wants to start a new feature, create an isolated development branch, says "init worktree", or needs to set up a feature branch for compounder workflow.
Creates an isolated git worktree for parallel feature development. Use when starting new features or when user says "init worktree" to set up a separate branch without affecting main codebase.
/plugin marketplace add jero2rome/compounder/plugin install compounder@jero2rome-compounderThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Initializes an isolated git worktree for feature development, enabling parallel work without affecting the main branch.
# Via skill (if permissions are configured)
/compounder:init "my-feature"
# Direct script call (always works)
scripts/init-worktree.sh "my-feature"
| Item | Location | Description |
|---|---|---|
| Worktree | ../compounder-{feature} | Sibling directory to main repo |
| Branch | feat/{feature} | Based on current HEAD |
Skill: compounder:init
Args: "feature-name"
Note: This may fail with permission error if bash command isn't pre-approved.
/path/to/scripts/init-worktree.sh "feature-name"
The script is located at:
$CLAUDE_PLUGIN_ROOT/scripts/init-worktree.sh
Or in cached plugins:
~/.claude/plugins/cache/jero2rome-compounder/compounder/*/scripts/init-worktree.sh
This section documents the trial-and-error process that led to successful invocation:
Tool: Skill
skill: "compounder:init"
Result: FAILED
Error: Bash command permission check failed for pattern...
This command requires approval
Lesson: The Skill tool internally runs a bash script that wasn't in the allowed permissions list.
Tool: AskUserQuestion
questions: [{"question": "What feature?", "options": [{"label": "Enter custom"}]}]
Result: FAILED
Error: Array must contain at least 2 element(s)
Lesson: AskUserQuestion requires at least 2 options. Can't use it for single free-text input.
Tool: Bash
command: /path/to/scripts/init-worktree.sh
Result: FAILED
Error: Feature name required
Usage: /compounder:init "my-feature"
Lesson: The script requires a positional argument for the feature name.
Tool: Bash
command: /path/to/scripts/init-worktree.sh "test-comp"
Result: SUCCESS
Creating worktree and branch...
HEAD is now at ad08615 ...
Worktree created: ../compounder-test-comp
Branch created: feat/test-comp
$CLAUDE_PLUGIN_ROOT/scripts/init-worktree.sh or cached pathTo auto-approve the init script, add to .claude/settings.json:
{
"permissions": {
"allow": [
"Bash(*/scripts/init-worktree.sh:*)"
]
}
}
Switch to worktree:
cd ../compounder-{feature} && claude
Start workflow:
Cleanup after merge:
git worktree remove ../compounder-{feature}
After init completes, guide user to:
ideate skill for the featureThis skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.