Split the work.Not the codebase.
Paste a repo and a feature request. Splitfire turns it into a collision-proof graph of tasks your coding agents can run at the same time — each with its own contract, context pack and acceptance checks.
Real plan · shadcn-ui/taxonomy · “Add OAuth login” · 2026-10-27
Planned by gemma-4-26b-a4b-it for shadcn-ui/taxonomy@298a885 · Open this plan → · numbers computed from the committed fixture in data/featured-plan.json
How it works
Read the real import graph
tree-sitter parses every import, so ownership is based on how your code actually connects — not a model's guess.
Contracts first, zero overlap
Shared types land first as a tiny contract task, so dependent work fans out in parallel. Every file has exactly one owner.
Hand it to your agents
One click copies Alan-ready prompts, each with its context pack, model, cost and the checks that prove it's done.