- name
- mirage-parallel-build
- description
- Lead several agents building one Mirage world at the same time, one module each - the coordination contract (site plan as single source of truth, file ownership, anchors, append-only NOTES.md requests, merge order, conflict rules), how to launch workers in Claude Code (background sub-agents), Codex or Cursor, and how to integrate and verify. Use when a Mirage world has three or more modules to write, or the user says "build in parallel", "use sub-agents", "split the world", "fan out", "team of agents".
Parallel build (lead)
The lead plans, launches, integrates and verifies; workers each write one module (mirage-module). It works
because nobody needs anybody else's code: positions come from plan.js, connections are anchors, and talk goes
through NOTES.md.
0. Before launching (lead)
BRIEF.mdwith one module brief per module (mirage-brief-to-plan),plan.jscomplete for this round.- Anchor contract fixed in the briefs: every key, who offers it, what
posis exactly, who consumes it. - Lead files exist:
main.js,modules/index.jslisting every module, a stubmodules/<name>.jsper module (export default { name: '<name>', build() {} }),modules/materials.js, NOTES.md with a## <name>header per module,scenarios/playtest.json.npx vite build && npm run playtestpasses on the stubs.