I was using this and superpowers but eventually, Plan mode became enough and I prefer to steer Claude Code myself. These frameworks are great for fire-and-forget tasks, especially when there is some research involved but they burn 10x more tokens, in my experience. I was always hitting the Max plan limits for no discernable benefit in the outcomes I was getting. But this will vary a lot depending on how people prefer…
Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
111–120 of 278 posts
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#112Earlier quoted context omitted.
Wrappers are useful for some tasks. I use ralph loops for things that are extremely complicated and take days of work. Like reverse engineering projects or large scale migration efforts.
Even with the 1 mil context windows? Can't you just keep the orchestrator going and run sub agents? Maybe the added space is too new? I also haven't tested out the context rot from 300K and up. Would love some color on it from first hand exp.
Most projects I do take 20 minutes or less for an agent to complete and those don't need a wrapper. But for longer tasks, like hours or days, it gets distracted.
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#113I'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?
I've used both From my experience, gsd is a highly overengineered piece of software that unfortunately does not get shit done, burns limits and takes ages while doing so. Quick mode does not really help because it kills the point of gsd, you can't build full software on ad-hocs. I've used plain markdown planning before, but it was limiting and not very stable, superpowers looks like a good middleground
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#114I was using this and superpowers but eventually, Plan mode became enough and I prefer to steer Claude Code myself. These frameworks are great for fire-and-forget tasks, especially when there is some research involved but they burn 10x more tokens, in my experience. I was always hitting the Max plan limits for no discernable benefit in the outcomes I was getting. But this will vary a lot depending on how people prefer…
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#115Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#116Apart from GSD and superpowers, there's another system, called PAUL [1]. It apparently requires fewer tokens compared to GSD, as it does not use subagents, but keeps all in one session. A detailed comparison with GSD is part of the repo [2]. [1] https://github.com/ChristopherKahler/paul [2] https://github.com/ChristopherKahler/paul/blob/main/PAUL-VS-...
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#117I have a ai system i use. I'd like to release it so others can benefit, but at the same time it's all custom to myself and what i do, and work on. If I fork out a version for others that is public, then I have to maintain that variation as well. Is anyone in a similar situation? I think most of the ones I see released are not particularly complex compraed to my system, but at the same time I don't know how to convey…
you don't have to maintain it. Especially in the age of ai, just giving people inspiration and something to vibe from is more than sufficient and appreciated
there's a lot of patterns i think are helpful for me.
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#118I have a ai system i use. I'd like to release it so others can benefit, but at the same time it's all custom to myself and what i do, and work on. If I fork out a version for others that is public, then I have to maintain that variation as well. Is anyone in a similar situation? I think most of the ones I see released are not particularly complex compraed to my system, but at the same time I don't know how to convey…
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#119Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#120For this reason I don’t think it’s actually a good name. It should be called planning-shit instead. Since that’s seemingly 80%+ of what I did while interacting with this tool. And when it came to getting things done, I didn’t need this at all, and the plans were just alright.