Gsd Build Get Shit Done
Get Shit Done is a Claude Code plugin for the Build phase that delivers a lightweight meta-prompting, context engineering, and spec-driven development system for solo builders using Claude Code.
by gsd-build · github.com/gsd-build/get-shit-done
Install this Claude Code plugin when you want a repeatable spec-driven and context-engineering workflow so solo builds stay focused instead of sprawling across random prompts.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install gsd-build-get-shit-done@gsd-build/get-shit-doneBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:gsd-build/get-shit-done") and the paste-ready config with skillselion.get_install_config("plugin:gsd-build/get-shit-done").
What it does
Get Shit Done (gsd-build/get-shit-done) is a Claude Code plugin from the gsd-build ecosystem that packages a lightweight meta-prompting, context engineering, and spec-driven development system attributed to TÂCHES. Solo and indie builders use it when they already ship with Claude Code but lose thread across sessions, vague prompts, or scope creep. The plugin sits in the catalog as agent tooling with a PM-oriented workflow: you define what you are building, engineer the context the agent needs, and drive execution in a spec-first way rather than improvising every turn. It is methodology-heavy, not a database connector or deploy script, so it pairs well with ordinary coding skills and review habits. Because it shapes how you work across ideation, scoping, implementation, and iteration, Skillselion tags it journey-wide with a canonical Build → PM shelf for browse and SEO.
Highlights
- Meta-prompting layer that structures how Claude Code approaches tasks instead of one-off chat
- Context engineering patterns to keep long builds coherent without manually re-pasting state
- Spec-driven development flow aligned with TÂCHES-style lightweight execution
- Designed as a system for Claude Code rather than a single-purpose integration
- Community plugin bundle with 1 packaged plugin in the gsd-build/get-shit-done repo
Why builders use it
Claude Code sessions often dissolve into unstructured prompts, lost context, and shipped code that never matched what you actually intended to build.
After you register the plugin, you can run a consistent spec-driven and context-engineered workflow so each session picks up clear intent and execution steps instead of starting from zero.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 48.3k stars, 0 votes.
FAQ
Who is gsd-build-get-shit-done for?
It is for indie and solo developers who use Claude Code and want meta-prompting, context engineering, and spec-driven habits packaged as an installable plugin.
When should I use gsd-build-get-shit-done?
Use it when you are starting or continuing a feature and need structured specs and context before and during implementation, especially on multi-session builds.
How do I add gsd-build-get-shit-done to my agent?
Install or register the plugin from the gsd-build/get-shit-done repository in your Claude Code plugins setup, then invoke it according to the repo’s GSD workflow documentation.
Comments
Share how you use gsd-build-get-shit-done, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.