implement-fanout
Installation
SKILL.md
Implement Fanout
The parallel sibling of /implement. /implement is deliberately one-ticket-per-context — a fresh
context keeps the model sharp, and worktrees are a harness concern, not a skill concern. This skill
keeps that principle (each ticket still gets its own isolated, fresh context) but automates the
fan-out across independent tickets so you aren't opening sessions by hand.
One-at-a-time is still the default. This is the exception for a genuine batch of siblings.
When to use vs /implement
/implement— one ticket, or a dependency chain (#N needs #N-1). A chain has no frontier to parallelize; run it serially, one ticket per fresh conversation./implement-fanout— 2+ ready tickets with no dependency edge between them.