gsd-build/get-shit-done

I've found the get-shit-done tool[1] to be quite useful for forcing me to properly plan the implementation and ensuring the context remains small and relevant at all times. It is slower than when I was just using Claude directly though. [1] https://github.com/gsd-build/get-shit-done

in the Claude Code realm I use GSD and it manages all that and keeps token use low. Plus it writes to a file so memory is stored so I can type /clear and the token count resets yet it still can remember where I left off for the next work. Check it out here: https://github.com/gsd-build/get-shit-done

CLAUDE.md isn't a silver bullet either, I've had it lose context a couple of questions deep. I do like GSD[1] though, it's been a great addition to the stack. I also use multiple, different LLMs as a judge for PRs, which captures a load of issues too. [1] https://github.com/gsd-build/get-shit-done

…compiler infers them. THE WORKFLOW Opus 4.6 didn't figure this out on its own. If I'd opened a chat and typed "build me a programming language," I'd have gotten a toy lexer and a lot of apologies. What made it work was GSD (github.com/gsd-build/get-shit-done), a spec-driven development system. Three files traveled with the project: PROJECT.md (tech stack, constraints), ROADMAP.md (every milestone and phase), and STATE.md (updated after every single commit, telling the AI exactly where we are and what's next). STATE.md was the leash. Without it, the model constantly tried to jump ahead. Every feature followed: Milestone -> Phase -> Plan -> Atomic Commit. 300 tests ran after every plan. Th…

I’ve had good luck using https://github.com/gsd-build/get-shit-done It will ask you questions, break down the project into smaller tasks, work through them one by one with UAT check points along the way. It also handles managing your context

The GSD tool (get-shit-done) automates a very similar process to this, and has been mind-blowing for larger projects and refactors. https://github.com/glittercowboy/get-shit-done You still need to know the hard parts: precisely what you want to build, all domain/business knowledge questions solved, but this tool automates the rest of the coding and documentation and testing. It's going to be a wild future for software development...

How is this different from GSD: https://github.com/glittercowboy/get-shit-done I've been using that and it's excellent

in addition to Compound Engineering, people in the comments in that thread also suggested the following planning tools to use with git worktrees: - https://github.com/gsd-build/get-shit-done - https://github.com/obra/superpowers - https://github.com/github/spec-kit I personally haven't used them, but I think any process like these + worktrees is the serious pro-tip/unlock.

The process that Get Shit Done forces is pretty good, with Claude Code as the interface. https://github.com/gsd-build/get-shit-done