Parallel Dev Worktrees

Use this skill for day-to-day parallel development in one repo. It is operational: create a feature worktree, run it at a named Portless URL, keep mutable state isolated, finish safely, and never damage unrelated work.

First Look

Before creating or merging worktrees:

1. Read repo instructions such as AGENTS.md, .agents/skills/*worktree*/SKILL.md, package.json scripts, and existing worktree docs.
2. Prefer repo-local scripts over generic commands. Look for wt:create, wt:list, wt:doctor, wt:runtime, wt:overlap, wt:finish, wt:clean, and wt:prune. If a repo-local worktree script exists for the operation, use it instead of the generic commands below unless the script is broken or the user explicitly asks for a manual fallback.
3. Check the current checkout status. Respect dirty files and assume they belong to the user or another agent.
4. If the repo lacks a worktree workflow, use the fallback guidance in generic-worktree-commands.md: create a sibling worktree from the explicit default integration branch, derive a safe branch slug, run setup/env isolation checks, use Portless for the runtime URL, and finish only from clean checkouts after overlap checks. Recommend adding project scripts later.

Project Onboarding

Skill installation and project initialization are separate steps. Installing this skill makes the workflow available to the agent; it does not automatically modify every repo or install project-local scripts.

Portless is a required companion for the intended workflow. During project initialization, check both: