Gsd Build Get Shit Done
- 64.8k repo stars
- Updated May 31, 2026
- gsd-build/get-shit-done
Get Shit Done is a Claude Code plugin that delivers a lightweight meta-prompting, context engineering, and spec-driven development system for solo builders using Claude Code.
About
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. Developers 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.
- 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
Gsd Build Get Shit Done by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
/plugin install gsd-build-get-shit-done@gsd-build/get-shit-doneAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 64.8k |
|---|---|
| Last updated | May 31, 2026 |
| Repository | gsd-build/get-shit-done ↗ |
What it does
Install this Claude Code plugin when you want a repeatable spec-driven and context-engineering workflow so builds stay focused instead of sprawling across random prompts.
Who is it for?
Best when you live in Claude Code and want a disciplined spec-and-context system without adopting a heavy enterprise framework.
Skip if: Skip if you only need one-shot code generation with no spec ritual, or developers and do not use Claude Code as your primary agent.
What you get
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.
- Repeatable spec-driven prompting structure inside Claude Code
- Context engineering patterns for multi-step implementation
- A single-plugin bundle ready to register from the GSD repo
By the numbers
- Repository gsd-build/get-shit-done lists pluginCount: 1
- Catalog source metadata: community category, auto-ingested listing
Recommended Plugins
0oastro Kawai Girl Output StyleTransform Claude's responses into kawaii anime girl style\!3
0xbigboss Claude CodeComprehensive configuration system for Claude Code51
2lab Ai Oh My ClaudeClaude Code plugin for AI-powered iterative development loops.37
45ck Claude Sdlc PluginClaude Code plugin for SDLC workflow automation with Storybook planning hub1
70 10 Claude Code Plugins70-10's Claude Code plugins
Aaronbassett Agent FoundryMy personal plugin marketplace for Claude Code4How it compares
Journey-wide productivity plugin for spec-driven agent workflow, not an MCP server or a single-task integration.
FAQ
Who is Gsd Build Get Shit Done for?
It is for 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.