You have ten simple-ish things in your head you want to add to your codebase. How are you turning that into working code as fast as possible? Do we have any opinionated workflows? My workflow is essentially: I have a folder features/ containing one markdown per thing to implement (be it features or bugs) and a folder completed/ I have a features/CLAUDE.md that says When you have completed a feature, move it to completed/ I have a features/backlog.md where I write, in free text, what features to implement To execute, I run a new claude code session and say something like Implement all features in features/backlog.md - one at a time. Commit after every feature. ultracode It does work, and I can just leave it running for a few hours, but… It’s hard to keep track of what features are currently being implemented Only one feature is implemented at a Settings this up manually for every project takes some time, and I haven’t really bothered to make a template for it because I’m just not happy enough with the flow yet. Sure, there’s claude -w to create a worktree and then you can manually tell each session to start a separate feature, but… claude -w just creates a git branch in a separate folder - when I implement features I often want to run the application (often one or more webservers, so, they need to be configured to run at different ports to be able to run concurrently), have a separate .env file for each tree etc. and claude -w does nothing like that out of box, and I haven’t really found a good solution. There’s cmux, conductor, superset and stuff like that, but… they just seem like shitty GUI alternatives to tmux and most are mac-only (I run on both linux and mac). I already heavily use tmux, what I want is issue tracking + automatic merge agents + agent orchestration, not a claude code multiplexer. Something like Gas Town, but much less bloated. It’s a shame nobody is doing that. submitted by /u/Ran4
Originally posted by u/Ran4 on r/ClaudeCode
You must log in or # to comment.