Orchestration
Running a team of subagents on one design build: clone briefs, disjoint file ownership...
Install
npx skills add AThevon/genjutsu --skill orchestration -g -a claude-code -y- Repository
- AThevon/genjutsu721
- Category
- Design
- Updated
- 3d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
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.
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.
