Slash Command

/SKILL

Splits tasks into isolated git worktrees from parent commit, implements units with validation, commits per unit, merges sequentially back to parent branch, cleans up successful worktrees.

Git

Bash

git-workflow

automation

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

Details

Namespacefan-out-fan-in/

Prompt Preview

# 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

1. Read the plan from a file such as `scratch/plan.md` or from inline instructions.
2. Record the parent branch and commit with `git branch --show-current` and `git rev-parse HEAD`.
3. Stop if `git status --short` is not clean. Do not fan out from a dirty tree.
4. Scan recent history and existing worktrees with `git log --oneline -20` and `git worktree list` so you do not duplicate work.
5. Split the work into units that do not edit ...

Command Content

Other plugins with /SKILL

/sc-parallel-worktree-team

Decomposes specified work into parallel streams, creates isolated git worktrees per stream, symlinks dependencies, and spawns agent teams in tmux for simultaneous execution.

sc-skills

/worktree-tasks

Implements multiple tasks in parallel across git worktrees using opus subagents, then merges them sequentially into main. Takes tasks separated by | or numbered.

johnlindquist-claude

/loop-plan

Plans tasks via interactive interview, auto-parallelizes execution across git worktrees, runs loop, and merges results into a single branch.

8 tools

loophaus

/SKILL

512

Configures Git user identity and project commit scopes: verifies name/email, initializes git-agent, validates scopes from .git-agent/config.yml, generates .claude/git.local.md.

haiku7 tools

git

/SKILL

512

Launches isolated code-context researcher agent to fetch repo/library context via DeepWiki, Context7, Exa, git clone, or all methods. Accepts repo URL/name and optional --method flag.

code-context

/SKILL

512

Creates a GitHub pull request with automated quality validation, security scanning, issue linking, and compliance checks. Accepts optional description or issue reference.

3 tools

github

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 1. Read the plan from a file such as `scratch/plan.md` or from inline instructions. 2. Record the parent branch and commit with `git branch --show-current` and `git rev-parse HEAD`. 3. Stop if `git status --short` is not clean. Do not fan out from a dirty tree. 4. Scan recent history and existing worktrees with `git log --oneline -20` and `git worktree list` so you do not duplicate work. 5. Split the work into units that do not edit ...

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.