Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
1–10 of 278 posts
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#2With GSD, I was able to write 250K lines of code in less than a month, without prior knowledge of claude.
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#3With GSD, I was able to write 250K lines of code in less than a month, without prior knowledge of claude.
I could copy 250k lines from github.
Faster than using ai. Cheaper. Code is better tested/more secure. I can learn/build with other humans.
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#4With GSD, I was able to write 250K lines of code in less than a month, without prior knowledge of claude.
250K? Could you expand your experience with details about your project and the lessons and issues you found?
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#5I've tried it, and I'm not convinced I got measurably better results than just prompting claude code directly.
It absolutely tore through tokens though. I don't normally hit my session limits, but hit the 5-hour limits in ~30 minutes and my weekly limits by Tuesday with GSD.
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#6[flagged]
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#7> If you know clearly what you want
This is the real challenge. The people I know that jump around to new tools have a tough time explaining what they want, and thus how new tool is better than last tool.
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#8GSD has a reputation for being a token burner compared to something like Superpowers. Has that changed lately? Always open to revisiting things as they improve.
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#9> If you know clearly what you want This is the real challenge. The people I know that jump around to new tools have a tough time explaining what they want, and thus how new tool is better than last tool.
What do you think drives the tooling ecosystem aside from VC dollars?
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#10I've had a good experience with https://github.com/obra/superpowers. At first glance this looks similar. Has anyone tried both who can offer a comparison?