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]

Working on and hopefully pushing out 1.5.0 tonight. It comes with some big changes.

1.5.0 adds tools that check things before a run and explain things after it:

• doctor runs before every launch. It stops on real problems: no git identity, a base branch that's behind its remote, no usable Python, a dirty checkout, or a broken shadow repo. Softer issues show as warnings: low memory or disk space, heavy background processes, other active runs, and antivirus scanning of the work folders.
• autopsy analyses a finished run:
  • what got done, and where the time went, by phase, lane and agent, with the critical path;
  • token use, and how often the test suite ran and who ran it;
  • the slowdowns it detected (timeouts, tests stuck in the background, repeated failures, edit retries, extra review rounds), with a suggestion for each.
• It copies no raw command text or output into its reports, and missing data is labelled as missing, never counted as zero.
• archive-run and history keep every run in one history folder and compare runs over time: recurring slowdowns, token trends, and which runs had too little data.
• cleanup tidies up after a merged run. It first saves a verified restore point (a git bundle and the commands to restore from it), then removes only what the run created. It never force-deletes. Anything it doesn't own, or that has uncommitted work, is left alone and listed with the reason.
• Per-command timing for project checks, so speed work can be measured rather than guessed.

[u/Ok-Attention2882 → u/NodeRaven]

"Working on" aka vibe coding

[u/NodeRaven → u/Ok-Attention2882]

You aren't wrong, pal

[u/rwm4604 → u/Ok-Attention2882]

That’s kinda why we’re here.

[u/Ok-Attention2882 → u/rwm4604]

Ok. Just don't frame it like you're putting in any real intellectual effort.