fanning-out-parallel-writers-with-verified-changeslisted
Install: claude install-skill sblattj/agent-chandlery
## More triggers
xx (old name)
# fanning-out-parallel-writers-with-verified-changes
Same engine as `fanning-out-a-verified-read-only-swarm` (`${SKILL_DIR:-~/.claude/skills/fanning-out-a-verified-read-only-swarm}/swarm.workflow.js`), run with `mode: "write"`. Usage: `/fanning-out-parallel-writers-with-verified-changes <goal> [--compare]`.
## Do this
1. **Scout inline** and split the work into units the same way as `fanning-out-a-verified-read-only-swarm`: the cheap tier by default, `sonnet` or `opus` only for units that can't be split.
2. **Declare the workspace before launching.** Pick one strategy:
- One git worktree per writer (for example a sibling dir like `../<repo>-<suffix>`), branched from the repo's integration branch. Take that branch from the repo's own rules or the user's agent instructions file (AGENTS.md / CLAUDE.md) if it names one; otherwise infer it from the cwd and git remote, or ask. Create the worktrees yourself, then pass `worktree: "<abs path>"`.
- Or one shared task worktree with non-overlapping `owns`.
- `isolate: true` asks the harness for a throwaway worktree. It's expensive, so use it only when you have nothing else.
3. **Give every unit `owns: [abs paths, including new tests]`.**
- The script gives each writer the full sibling ownership map plus the concurrent-edit notice.
- If any `owns` overlap, the script runs writers one at a time, on purpose.
- Shared files, lockfiles and generated outputs get a single owner.
4. **Run it*