The README recommends --dangerously-skip-permissions as the intended workflow. Looking at gsd-executor.md you can see why — subagents run node gsd-tools.cjs, git checkout -b, eslint, test runners, all generated dynamically by the planner. Approving each one kills autonomous mode. There is a gsd-plan-checker that runs before execution, but it only verifies logical completeness — requirement coverage, dependency graphs…
Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
71–80 of 278 posts
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#72[flagged]
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#73Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#74https://zarar.dev/spec-driven-development-from-vibe-coding-t...
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#75I'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 tried Superpowers for my current project - migrating my blog from Hugo to Astro (with AstroPaper theme). I wrote the main spec in two ways - 1) my usual method of starting with a small list of what I want in the new blog and working with the agent to expand on it, ask questions and so on (aka Collaborative Spec) and 2) asked Superpowers to write the spec and plan. I did both from the working directory of my blog's…
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#76[1] https://www.riaanzoetmulder.com/articles/ai-assisted-program...
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#77Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#78Earlier quoted context omitted.
GSD and superpowers aren't CLI wrappers?
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.
Otherwise, if you can own your own thinking, orchestrating, and steering of agents, you're in a more mature place.
Re: Get Shit Done: A meta-prompting, context engineering and spec-driven dev system
#79Earlier quoted context omitted.
I don't know brother, I don't use them, they may be great they may suck. What I've found is that adding peripherals always creates more problems. If you aren't using Claude for professional work then just sticking with the factory plan mode probably works. If not, look into creating your own Claude skills, try to understand how prompt pipelines work and it will unlock a ton of automation for you. Not just for coding.
I do use Claude for professional work, but I suspect I don't know enough to be able to get anything useful out of your advice since I don't know how to add my own Claude skills that form a prompt pipeline without adding peripherals. I'll just have to catch this part of the whole thing as a late adopter, I suppose. Ah well, thanks for the help.