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.
View on GitHubjero2rome/compounder
compounder
skills/init/SKILL.md
January 20, 2026
Select agents to install to:
npx add-skill https://github.com/jero2rome/compounder/blob/main/skills/init/SKILL.md -a claude-code --skill initInstallation paths:
.claude/skills/init/# Init Skill
Initializes an isolated git worktree for feature development, enabling parallel work without affecting the main branch.
## When to Use
- User says "initialize a worktree for X"
- User says "use compounder to init"
- User wants to start a new feature branch
- User needs isolated development environment
## Quick Start
```bash
# Via skill (if permissions are configured)
/compounder:init "my-feature"
# Direct script call (always works)
scripts/init-worktree.sh "my-feature"
```
## What Gets Created
| Item | Location | Description |
|------|----------|-------------|
| Worktree | `../compounder-{feature}` | Sibling directory to main repo |
| Branch | `feat/{feature}` | Based on current HEAD |
## Invocation Methods
### Method 1: Skill Tool (May Require Permission)
```
Skill: compounder:init
Args: "feature-name"
```
**Note:** This may fail with permission error if bash command isn't pre-approved.
### Method 2: Direct Script Call (Recommended)
```bash
/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
```
## Debugging Journey (Reference for Claude)
This section documents the trial-and-error process that led to successful invocation:
### Attempt 1: Skill Tool
```
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.
### Attempt 2: Ask User for Feature Name
```
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.
### Attempt 3: Dir