My pipeline: - beads for task tracking. - one Claude Code session that runs few development lanes. Each lane is dynamic workflow that - takes a ready task - runs a designer agent if there are ui changes - runs implementation agent (on a git worktree) - runs review agent - loop to implementation once if it rejected - if approved creates a PR - when CI checks are green (tests, vulnurability audits etc) marks as lane-verified) - task can be marked as needed my attention (when it needs some decision, or manual configuration/action) - same session runs a lander, which - take lane-verified task - rebases on master - ensures master is green - merge - deploy - hand tasks back to pipeline if conflict resolution is complex or CI is red after rebase. - I don't look at the code - I don't verify individual tasks
- in the other session I review what needs my attention - that's actual bottleneck, sometimes questions are very stupid and can be saved by LLM directly. - I have dedicated sessions for planning/researching big feature/epics. - I review periodically how product is working, and submit bugs via my own tool (https://session-replay.com)
This delivers 50-100 PRs a day (depending on my ability to resolve questions) with a quite decent quality. Apart of my attention, CI is other bottleneck (had to install a dedicated server for CI).
Feel free to ask if you have questions.