# Orchestration

Running a team of subagents on one design build: clone briefs, disjoint file ownership...

- Repository: https://github.com/AThevon/genjutsu (721 stars)
- Category: Design
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add AThevon/genjutsu --skill orchestration -g -a claude-code -y`
Codex: `npx skills add AThevon/genjutsu --skill orchestration -g -a codex -y`
Cursor: `npx skills add AThevon/genjutsu --skill orchestration -g -a cursor -y`
Gemini CLI: `npx skills add AThevon/genjutsu --skill orchestration -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add AThevon/genjutsu`

## Description

Running a team of subagents on one design build: clone briefs, disjoint file ownership, isolated builds, the evidence packet, review lenses, the fix plan, verdicts, cold eyes and the stop rule, with the workflow templates bunshin runs.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

> **Version-sensitive.** The workflow tool contract (`scriptPath`, `args`, `agent`, `parallel`,
> `phase`) and the Impeccable verbs named here were checked on **2026-10-31**. What against is
> in `_jutsu/VERSIONS.md`, section "Orchestration". If that date is old, re-check before relying
> on a verb.

# Orchestration

> Loaded by `/genjutsu:bunshin`. One art director, many clones. This module is how the clones
> are briefed, fenced, checked and stopped, so that ten agents in parallel produce one site and
> not ten opinions.

A clone is a subagent. It starts from nothing: no conversation, no memory of the thesis, no idea
which files its siblings are editing. Everything it knows is in its brief. Everything that goes
wrong in a fan-out goes wrong because a brief left something out.

---

## The five templates

Each phase that fans out has a template under `workflows/`, next to this file. Each one is a
workflow script: a pure `meta` literal, then a body that calls `agent()`, `parallel()` and
`phase()`, parameterised entirely by `args`. `scripts/check-workflows.mjs` runs every template
against stubs in CI: to the end with every agent answering, and again with every agent
answering null, where a template must end or stop on its own named error (`research.js` and
`review.js` do, with nothing to synthesise or plan), never crash. `build.js` and `refine.js`
share one isolated-build block, which the check holds identical in both.

The rest: https://github.com/AThevon/genjutsu/blob/HEAD/skills/_jutsu/orchestration/SKILL.md