treetopia

Treetopia

Create an isolated OpenCode worktree whenever the user explicitly wants branch isolation, parallel feature work, or protection from branch collisions.

Trigger Rules

Use this skill only when the user explicitly says one of these intents:

• Create a worktree.
• Use a worktree.
• Use an isolated worktree.
• Create a parallel feature branch.
• Avoid branch collision.
• Keep two agents or two features from sharing one branch.

Do not use this skill merely because the user asks for normal implementation, refactor, testing, or feature work. Ordinary feature work stays in the current checkout unless the user explicitly requests isolation.

Purpose

Prevent two primary agents or two active features from sharing the same branch and overwriting or colliding with each other's changes.

Start Workflow

When triggered:

1. Derive a concise branch name from the user's task.
   • Use lowercase words separated by hyphens.
   • Prefer a short prefix such as feature/, fix/, or chore/ when obvious.
   • Keep the name specific enough to identify the task.
2. Determine the base branch.
   • If the user names a base branch, use that branch.
   • Otherwise, default to the current branch.
3. Immediately call worktree_create.
   • Pass the derived branch name.
   • Pass the base branch only when the user named one or the tool requires it.
4. Continue development inside the new worktree/session created by the tool.

Example tool intent:

worktree_create(branch: "feature/customer-import", baseBranch: "main")

If no base branch was named:

worktree_create(branch: "fix/login-timeout")

Development Guidance Inside Worktree

• Treat the worktree as the isolated task workspace.
• Follow normal project instructions, architecture rules, and verification gates.
• Do not assume the original checkout has your worktree changes.
• Avoid cross-worktree edits unless the user explicitly asks.
• Preserve the verification gate before proposing teardown, merge, or cleanup.