Emdash worktree orchestrator

Skill riteshkew/yc-skills/skills/emdash-worktree-orchestrator

Catalog of all 198 YC Winter 2026 companies + 18 working Claude Code Skills inspired by the ones an open-source tool can replicate. Inspired by, not affiliated with.

Install

npx -y skills add riteshkew/yc-skills --skill emdash-worktree-orchestrator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Given a list of coding tasks and a repo base branch, produce a deterministic parallel-agent orchestration plan: git worktree setup commands (one isolated worktree and branch per agent), an assignment table, and teardown commands. Use this skill whenever you need to spin up multiple coding agents in parallel across isolated git worktrees and want a safe, reviewable plan before executing anything.

SKILL.md

2.8 KB, as published. Nobody here has run it

Workflow

When this skill triggers, follow these steps in order.

Step 1 — Locate the agents JSON file

Check whether the user has specified an agents JSON file path.

If a path is provided, confirm the file exists and is readable.
If no path is provided, ask: "Please provide the path to your agents JSON file. It must contain repo, baseBranch, worktreeRoot, and an agents array of { id, task } objects. See examples/agents.json for a working example."
If the user has no file ready, offer to generate one based on their described tasks before proceeding.

Step 2 — Verify the input shape

The engine validates these fields automatically, but confirm with the user that:

repo — absolute or relative path to the git repository root.
baseBranch — the branch each agent starts from (e.g. main).
worktreeRoot — directory where worktrees will be created (e.g. /tmp/worktrees).
agents — non-empty array; each entry must have a unique id (slug-safe) and a task description.

Duplicate agent ids will be rejected by the engine.

Step 3 — Run the engine

Execute the orchestration planner from the skill root:

node scripts/orchestrate.mjs <agentsFile>

The engine prints a Markdown plan to stdout with four sections:

Setup — one git worktree add block per agent.
Assignments — table mapping agent id → branch → worktree path → task.
Teardown — git worktree remove + git branch -D per agent.
Notes — reminders about parallel execution and sequential merging.

Capture stdout. If the process exits non-zero, surface the stderr message to the user and stop.

Step 4 — Present the plan

Show the full Markdown plan to the user. Remind them that:

The plan is read-only output — nothing has been executed yet.
They should review every setup command before running it.
Agents should be started in parallel (e.g. using tmux, separate terminals, or a CI matrix).
Merges back to baseBranch should be done sequentially to avoid conflicts.
Teardown commands remove both the worktree directory and the local branch.

Example

See examples/input.md for a worked four-agent scenario and examples/output.md for the plan produced by the engine.

Run the example yourself:

cd skills/emdash-worktree-orchestrator
bash examples/run.sh