get-shit-done

Wondering if this is attempting what github.com/gsd-build/get-shit-done has done: plan your milestones, discuss them, execute them, review them. It can also review the plans by another agent before execution... Everything documented and checked in.

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

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.

Try https://github.com/gsd-build/get-shit-done. It's been a game changer for me.

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

Great idea, and some of the tools are already somewhat covering it, e.g. GSD or spec-kit. https://github.com/gsd-build/get-shit-done https://github.com/github/spec-kit

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

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

Your task is certainly doable though. You can ask AI to focus on the functional aspects and create a design-only document. It can do that in chunks. You don't need to know about COBOL best practices now, that's an implementation detail. Is the plan to modernize the COBOL codebase or to rewrite in a different language? See what this skill does in Claude Code, you want something similar: https://github.com/glittercowboy/get-shit-done/blob/main/get...

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...

You should check out the PAL MCP and then also use this process, its super solid: https://github.com/glittercowboy/get-shit-done The way "Phases" are handled is incredible with research then planning, then execution and no context rot because behind the scenes everything is being saved in a State.md file... I'm on Phase 41 of my own project and the reliability and almost absence of any error is amazing. Investigate and see if its a fit for you. The PAL MCP you can setup to have Gemini with its large context review what Claude codes.

I've been playing around with the "Superpowers" [0] plugin in Claude Code on a new small project and really like it. Simple enough to understand quickly by reading the GitHub repo and seems to improve the output quality of my projects. There's basically a "brainstorm" /slash command that you go back and forth with, and it places what you came up with in docs/plans/YYYY-MM-DD-<topic>-design.md. Then you can run a "write-plan" /slash command on the docs/plans/YYYY-MM-DD-<topic>-design.md file, and it'll give you a docs/plans/YYYY-MM-DD-<topic>-implementation.md file that you can then feed to the "execute-plan" /slash command, where it breaks everything down into batches, tasks, etc, and actually implements everything (so three /slash commands total.) There's also "GET SHIT DONE" (GSD) [1] that I want to look at, but at first glance it seems