I find that claude’s normal planning tools are just super reckless, you say do X and it goes into these wild coding session to produce thousands lines of code, half of it is based on a random decision it took, without asking you, even if you’ve asked to ask the user!!! There are some solutions, and good workflows to tackle this I’ve tried this, but none of them really hitting the sweet spot for me: OOO
https://github.com/potentialInc/claude-ooo (full project ralph loop kind of approach - surprisingly works but even with x20 account, your tokens usage limit lasts 2 days), and more akin to go build this, make it high quality but whatever. Great for experimental work that you want to leave overnight. Native Planning: Just does random shit, super quick though GSD
https://github.com/gsd-build/get-shit-done : This is generally good shit but so slow, too detailed for me (I know there are options), not a big fan for exploratory phase, great if you want small execution but done really well. Big con: No integrated worktree kind parallel execution support or subagent use OpenSpec
https://github.com/Fission-AI/OpenSpec/ : I’m currently testing this, it’s quick, still good enough planning (but not great, a bit limited), I don’t think review and extra goodness like double checking with subagents etc. added, but almost at the sweet spot. Straight forward spec format, simple, not bloated. Superpowers (official skill repo)
I feel like this is still the best maybe, writing plans, execution, brainstorming and especially easy git worktree execution makes this very straight forward. Uses subagents, makes everything polished and fast. Though I feel like planning could’ve been better and results sometimes seems inconsistent (like half the UI makes sense other half uses another convention)
I also tried things like Github speckit, they are extremely overengineered for solo devs.
I know there are so many options out there, this is stuff I’m looking for :
Must have:
Reasonable token burn (should be usable with x20 account)
Extra prompt goodness, just good prompts built-in like, don’t DRY, and even better if it’s injected based on the context of the work (UI, Security, react etc.). It just makes quality better across the board
Good and meaningful flow of things (plan > revise > build > test). OOO even though an outlier in this list for example has a super weird flow, very intuitive as opposed to something like Openspec, which is as straight forward as it gets.
Nice to have:
Codebase mapping / Project Source of truth / Memory Management
Integrated Git worktree support
Integrated sub agent driven parallel dev
Not some big roleplay stuff with tons of weird terminology
Simple things that works well:
After completing a task with anything just ask review, simplify, double check UX, check test coverage
Literally ask the same thing twice and it’ll find new things, it’s just matter of giving claude a nudge to do, sometimes I simply say check again, or dig deeper and it just reveals bunch of new issues, or just bug fixes stuff.
Codex review, just ask $20 codex subsc to review the last commit, pending code, XYZ feature
Also I’m starting to wonder with 1M token, maybe all I need is just bunch of good prompts, baked them into my own skills and just let it rip.
What is your poison for workflow in Claude Code today?
submitted by
/u/_fboy41
Originally posted by u/_fboy41 on r/ClaudeCode