Skill

fan-out-fan-in

Parallelizes development tasks by splitting into isolated git worktrees for non-overlapping file changes, implements each scope independently with validation, then merges sequentially into parent branch.

Git

Bash

Typescript

git-workflow

automation

npx claudepluginhub kaeawc/auto-mobile --plugin auto-mobile

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use this when the user explicitly wants parallel agent work or the task is naturally decomposable into independent file scopes.

SKILL.md

Similar Skills

worktree-split

Decomposes parallelizable tasks into bounded git branches with low file overlap and creates safe worktrees for independent subtasks. Use when changes are loosely coupled.

episteme

nbl.parallel-subagent-driven-development

Executes implementation plans by analyzing dependencies, grouping tasks by level, and dispatching parallel subagents in isolated git worktrees with TDD and reviews.

nbl.superpowers

git-worktrees

Creates isolated git worktrees for parallel feature development and executes identical plans across workspaces via subagents for concurrent experimentation and result comparison.

git-worktrees

Stats

Stars34

Forks0

Last CommitApr 2, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Fan Out Fan In

Use this when the user explicitly wants parallel agent work or the task is naturally decomposable into independent file scopes.

Workflow

Read the plan from a file such as scratch/plan.md or from inline instructions.

Record the parent branch and commit with git branch --show-current and git rev-parse HEAD.

Stop if git status --short is not clean. Do not fan out from a dirty tree.

Scan recent history and existing worktrees with git log --oneline -20 and git worktree list so you do not duplicate work.

Split the work into units that do not edit the same files. If two units need the same file, merge them or sequence them.

For each unit, create an isolated worktree from the parent commit with git worktree add ../worktree-unit-N -b fan-out-unit-N "$PARENT_COMMIT".

In each worktree, implement only the assigned scope, run the relevant validation, and commit with fan-out: [unit-name].

Merge unit branches back into the parent branch one at a time, validating after each merge and again at the end.

Remove successful worktrees and branches. Preserve failed ones for inspection.

Repo Rules

Prefer repo validations over generic ones:

TypeScript: bun run lint, bun run build, bun test
Fast repo checks: bash scripts/all_fast_validate_checks.sh
Android: (cd android && ./gradlew <task>)

Write logs that matter to scratch/ if they are too long to inspect inline.

Do not create PRs or push branches as part of fan-out work.

Do not proceed if the work cannot be partitioned cleanly.

Fan Out Fan In

Use this when the user explicitly wants parallel agent work or the task is naturally decomposable into independent file scopes.

Workflow

Read the plan from a file such as scratch/plan.md or from inline instructions.
Record the parent branch and commit with git branch --show-current and git rev-parse HEAD.
Stop if git status --short is not clean. Do not fan out from a dirty tree.
Scan recent history and existing worktrees with git log --oneline -20 and git worktree list so you do not duplicate work.
Split the work into units that do not edit the same files. If two units need the same file, merge them or sequence them.
For each unit, create an isolated worktree from the parent commit with git worktree add ../worktree-unit-N -b fan-out-unit-N "$PARENT_COMMIT".
In each worktree, implement only the assigned scope, run the relevant validation, and commit with fan-out: [unit-name].
Merge unit branches back into the parent branch one at a time, validating after each merge and again at the end.
Remove successful worktrees and branches. Preserve failed ones for inspection.

Repo Rules

Prefer repo validations over generic ones:
- TypeScript: bun run lint, bun run build, bun test
- Fast repo checks: bash scripts/all_fast_validate_checks.sh
- Android: (cd android && ./gradlew <task>)
Write logs that matter to scratch/ if they are too long to inspect inline.
Do not create PRs or push branches as part of fan-out work.
Do not proceed if the work cannot be partitioned cleanly.