feature

Creates isolated Git worktrees branched from origin/main for parallel agent tasks.

1|Updated Sep 16, 2026
One-click install
npx skills add https://github.com/dsatpm/factory-skills --skill feature-dsatpm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/dsatpm/factory-skills/tree/main/plugins/feature/skills/feature
Command: npx skills add https://github.com/dsatpm/factory-skills --skill feature-dsatpm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple agents or developers work on the same repository simultaneously, they risk branch conflicts, duplicated work, and clobbering each other's changes. This Skill enforces a disciplined workflow where every task gets its own Git worktree and branch created from the latest origin/main, so parallel work never collides. ## Core Features & Use Cases - Isolated Worktree Creation: Creates a dedicated worktree and uniquely named branch from origin/main for every new task, with naming conventions and collision handling. - Scope Conflict Detection: Checks open PRs via gh pr list and their changed files before starting, stopping work if another PR touches the same files. - Harness-Aware Behavior: Adapts steps for Claude Code and Cursor-managed worktrees, skipping manual worktree commands when the harness manages them. - Use Case: An agent assigned to add user authentication runs this Skill first, gets a fresh worktree on branch agent/user-auth-0816a, verifies no open PR touches auth files, installs dependencies, and begins coding without interfering with other agents. ## Quick Start Start a new task by creating an isolated Git worktree branched from origin/main before writing any code.

Frequently Asked Questions about feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run multiple AI agents on the same Git repo without conflicts?▼

Give each agent its own Git worktree and branch created from the latest origin/main. Worktrees provide separate working directories sharing one repository, so agents never overwrite each other's files or commits.

How to create a Git worktree from origin/main for a new task?▼

Run git fetch origin, then git worktree add <dir>/<task-name> -b <prefix>/<task-name> origin/main. Use a gitignored directory for worktrees and verify with git branch --show-current that you are on the new branch.

Does this work with Claude Code or Cursor managed worktrees?▼

Yes. Claude Code creates and manages worktrees itself under .claude/worktrees/, so you skip the manual git worktree add and remove steps. Cursor-managed worktrees named worktree-* similarly keep their assigned branch.

Why does git branch -d fail after a squash merge?▼

After a squash or rebase merge, Git does not recognize the branch as merged, so -d refuses to delete it. Use git branch -D to force deletion; the work is safely merged even though Git cannot detect it.

Do Git worktrees share node_modules and dev servers?▼

No. Worktrees do not share node_modules or virtualenvs, so dependencies must be installed fresh in each worktree. Dev-server ports, shared databases, and lockfiles remain global and require manual coordination.