Bhaskar Pandey
Download résuméContactArticles
← All showcase projects

Open-source orchestration skill

lanes

The right model for every task. The same gates for every change. A Claude Code skill that turns one session into a token-efficient orchestrator: it audits unfinished work, triages tasks by complexity, and runs them in parallel git-worktree lanes with independent review before merge.

Visit project site ↗View public repository ↗

What it is

One Claude Code session becomes the orchestrator. It audits work already done, in progress, ready and blocked, then dispatches each task to an agent in its own git worktree. The orchestrator plans, merges and reports; lane agents do the coding.

What it is for

It helps finish or continue large software projects with several workstreams running at once while keeping the orchestrator's context small. On-demand lane status, durable job records, and pause-and-resume notes make the work visible across session restarts.

Why it was built

It grew out of running up to seven agents on a production codebase. Strong models were spending context and usage on routine work; one feature agent used more than 400,000 tokens. Early relay agents also wrote code themselves instead of handing it to the intended provider, so model identity had to be verified from actual usage data.

Complexity triage

T3 complex work starts with Claude Opus; T2 moderate work goes to Sonnet. DeepSeek is the primary T1 routine coder, with GLM 5.3 Flash for simple, bounded work. T0 mechanical tasks use haiku or a script. A task moves up a tier when it proves harder than expected or fails review twice.

How it works

External coders run as separate headless Claude Code processes through Anthropic-compatible provider APIs. A guarded relay blocks its small handoff agent from doing the coding itself. Each run records the model that actually ran, its exit code and output; full reports stay on disk while the orchestrator receives a short summary.

Quality gates

Codex handles routine independent reviews; Claude Opus reviews authority, security, money and migration code. Fix rounds continue until review is clean, then the branch merges with a no-fast-forward commit and is verified on main. Worker models stay in isolated worktrees, API keys stay in the user's shell, and pushes or deploys require approval.

How lanes works: a Claude Opus orchestrator triages work by complexity into separate git worktree lanes. T3 goes to Claude Opus, T2 to Claude Sonnet, T1 to DeepSeek or GLM 5.3 Flash, and T0 to haiku or a script. Each lane passes independent review, fix rounds and verification on main.
The public lanes workflow: triage, isolated worktrees, independent review, then verification on main.
Screenshot of the public lanes project site in its light theme, showing the headline and lanes-to-review-to-main diagram.
The public project site, captured at desktop width in its light theme.
Architecture schematic — not a product screenshot
Discovery→System design→Validated delivery

2026 · Designed and built; open-sourced

Claude Opus, Sonnet, DeepSeek, GLM 5.3 Flash and Codex

Open source under the MIT license