For me it was awesome. I needed a custom Pipeline for Preprocessing some Lab Data, including Visualization and Manipulation and it got me exactly what I wanted, as opposed to Codex Plan Mode, which just burned my weekly quota and produced Garbage
Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
91–100 of 278 posts
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#92Did anyone compare it with everything-claude-code (ECC)?
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#93I’ve tried GSD several times. I actually like the verbosity and it’s a simple chore for Claude to refresh project docs from GSD planning docs.
Like most spec driven development tools, GSD works well for greenfield or first few rounds of “compound engineering.” However, like all others, the project gets too big and GSD can’t manage to deliver working code reliably.
Agents working GSD plans will start leaving orphans all over, it won’t wire them up properly because verification stages use simple lexical tools to search code for implementation facts. I tried giving GSD some ast aware tools but good luck getting Claude to reliably use them.
Ultimately I put GSD back on the shelf and developed my own “property graph” based planner that is closer to Claude “plan mode” but the design SOT is structured properties and not markdown. My system will generate docs from the graph as user docs. Agents only get tasked as my “graph” closes nodes and re-sorts around invariants, then agents are tasked directly.
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#94"I am a super productive person that just wants to get shit done" Looked at profile, hasn't done or published anything interesting other than promoting products to "get stuff done" This is like the TODO list book gurus writing about productivity
Looking for 5 seconds at the github profile I see a bunch of music-related stuff, and also a bunch of contributions to private repos that we have no idea what they are. I get the productivity guru anti-pattern, but I honestly don't know what you're looking at that merits this kind of reflexive personal attack.
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#95I’ve tried GSD several times. I actually like the verbosity and it’s a simple chore for Claude to refresh project docs from GSD planning docs. Like most spec driven development tools, GSD works well for greenfield or first few rounds of “compound engineering.” However, like all others, the project gets too big and GSD can’t manage to deliver working code reliably. Agents working GSD plans will start leaving orphans a…
Can you expand on that at all (or point to some reading on how Claude plan mode works etc?)
I think I have to get my head around a lot more than I think
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#96Earlier quoted context omitted.
It's a cli wrapper. Don't know how you could say it wasn't. edit: GSD is a cli wrapper, Superpowers not so much. Both are over-engineered for an easy problem IMHO.
Both are dramatically over-engineered. & That's okay. I find them to be products of an industry reconciling how to really work with AI as well as optimize workflows around it. Similar to Gastown et al. Otherwise, if you can own your own thinking, orchestrating, and steering of agents, you're in a more mature place.
I also see it as fleeting as right when you have it figured out, a new model will work differently and may/may not need all their engineering layers.
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#97I use openspec and love it. I’m doing 5-7x with close to 100% of code AI generated, and shipping to production multiple times a day. I work on a large sass app with hundreds of customers. Wrote something here: https://zarar.dev/spec-driven-development-from-vibe-coding-t...
> large sass app > hundreds of customers
Large codebase. Yeah man, I have a small business, trying to grow but not easy going up against Ticketmaster.
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#98I 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 how to use my system as someone who just uses it alone.
it feels like I don't want anyone to run my system, I just want people to point their ai system to mine and ask it what there is valuable to potentially add to their own system.
I don't want to maintain one for people. I don't want to market it as some magic cure. Just show patterns that others can use.
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#99250K lines in a month — okay, but what does review actually look like at that volume? I've been poking at security issues in AI-generated repos and it's the same thing: more generation means less review. Not just logic — checking what's in your .env, whether API routes have auth middleware, whether debug endpoints made it to prod. You can move that fast. But "review" means something different now. Humans make human m…
I've been trying to beat this drum for a minute now. Your code quality is a function of validation time, and you have a finite amount of that which isn't increased by better orchestration.
My rant about this: https://sibylline.dev/articles/2026-01-27-stop-orchestrating...
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#100I'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 tried both. Each has pros and cons. Two things I don't like about superpowers is it writes all the codes into the implementation plan, at the plan step, then the subagents basically just rewrite these codes back to the files. And I have to ask Claude to create a progress.md file to track the progress if I want to work in multiple sessions. GSD pretty much solved these problems for me, but the down side of GSD is…
There is a fork that uses Claude Code-native features and tracks progress and task dependencies natively: https://github.com/pcvelz/superpowers