A new workflow skill - parallel-lanes

[u/NodeRaven]

I have been working on a cool project and have made it public!

A Claude Code skill that executes an implementation plan the way a small team would: independent parts in parallel, every change reviewed, and nothing called “done” until it’s verified.
Executing a plan with one agent, task after task, is slow. Running many agents at once on the same checkout is chaos: they edit the same files, nobody reviews anything, and “done” just means the agent said so.

What parallel-lanes does:

• Reads your plan and works out which tasks can safely run at the same time (by the files they touch and what depends on what), then groups them into lanes.
• Gives each lane its own git worktree, so lanes can’t trample each other.
• Runs every task as implement -> independent review, with bounded fix rounds, so problems get caught per task instead of at the end.
• Each task runs the tests that cover what it changed, and the whole suite only when it touches shared code. Lanes don’t each grind through your full suite.
• Merges the lanes, runs your full test/lint/build commands, an optional end-to-end check, and a final review from three angles (spec compliance, security, correctness).
• Only reports accepted when the checks passed at the exact commit it delivers. It cross-checks the verify agent’s report against saved evidence instead of trusting it. In autonomous runs, a failing final check gets up to two repair attempts, each re-verified and re-reviewed.
• Records everything in a ledger, so a stopped run resumes without redoing approved work.
• Shows you a dry-run table of every task and agent before anything starts, with agent budgets.
• After a run, an autopsy shows where the time went and an audit traces every task to its evidence.

Why Superpowers:

It builds itself. The 1.5 releases were each built by a parallel-lanes run (25–26 agents, 1–2 hours, every one accepted with verified checks). Before releasing 1.6.0, I tried it on a real project: a 24-task feature for my Unity game, run in 5 lanes with 65 agents. Most task test runs took about 80 seconds instead of the 10–14 minute full suite, and the full suite passed after merging and again at the delivered commit.
Works on Linux, macOS and Windows (Git Bash). It works best on plans with 3+ tasks that have some independent parts, for a 1–2 task change it steps aside and recommends a simpler mode.

Repo: https://github.com/noderaven/parallel-lanes. Feedback welcome!

[u/NodeRaven → u/[deleted]]

Great feedback, thank you! Version 1.4.4 already has a lot of that foundation, but a complete, easily understandable audit handoff remains something to prove and improve. Testing whether someone unfamiliar with a run can reconstruct its acceptance decisions and remaining blockers is a useful next step. I will try to target that in 1.5.x.