Get Shit Done (GSD)

English · Português · 简体中文 · 日本語 · 한국어 A light-weight and powerful meta-prompting, context engineering and spec-driven development system for Claude Code, OpenCode, Gemini CLI, Kilo, Codex, Copilot, Cursor, Windsurf, Antigravity, Augment, Trae, Qwen Code, Cline, and CodeBuddy. Solves context rot — the quality degradation that happens as Claude fills its context window.         <br> `bash npx get-shit-done-cc@latest ` Works on Mac, Windows, and Linux. <br> !GSD Install <br> "If you know clearly what you want, this WILL build it for you. No bs." "I've done SpecKit, OpenSpec and Taskmaster — this has produced the best results for me." "By far the most powerful addition to my Claude Code. Nothing over-engineered. Literally just gets shit done." <br> Trusted by engineers at Amazon, Google, Shopify, and Webflow. Why I Built This · How It Works · Commands · Why It Works · User Guide </div> --- > [!IMPORTANT] > ### Welcome Back to GSD > > If you're returning to GSD after the recent Anthropic Terms of Service changes — welcome back. We kept building while you were gone. > > To re-import an existing project into GSD: > 1. Run /gsd-map-codebase to scan and index your current codebase state > 2. Run /gsd-new-project to initialize a fresh GSD planning structure using the codebase map as context > 3. Review docs/USER-GUIDE.md and the CHANGELOG for updates — a lot has changed since you were last here > > Your code is fine. GSD just needs its planning context rebuilt. The two commands above handle that. ---

I'm a solo developer. I don't write code — Claude Code does. Other spec-driven development tools exist; BMAD, Speckit... But they all seem to make things way more complicated than they need to be (sprint ceremonies, story points, stakeholder syncs, retrospectives, Jira workflows) or lack real big picture understanding of what you're building. I'm not a 50-person software company. I don't want to play enterprise theater. I'm just a creative person trying to build great things that work. So I built GSD. The complexity is in the system, not in your workflow. Behind the scenes: context engineering, XML prompt formatting, subagent orchestration, state management. What you see: a few commands that just work. The system gives Claude everything it needs to do the work and verify it. I trust the workflow. It just does a good job. That's what this is. No enterprise roleplay bullshit. Just an incredibly effective system for building cool stuff consistently using Claude Code. — TÂCHES --- Vibecoding has a bad reputation. You describe what you want, AI generates code, and you get inconsistent garbage that falls apart at scale. GSD fixes that. It's the context engineering layer that makes Claude Code reliable. Describe your idea, let the system extract everything it needs to know, and let Claude Code get to work. ---

People who want to describe what they want and have it built correctly — without pretending they're running a 50-person engineering org. Built-in quality gates catch real problems: schema drift detection flags ORM changes missing migrations, security enforcement anchors verification to threat models, and scope reduction detection prevents the planner from silently dropping your requirements.

• Gates taxonomy — 4 canonical gate types (pre-flight, revision, escalation, abort) wired into plan-checker and verifier agents • Shell hooks fix — hooks/*.sh files are now correctly included in the npm package, eliminating startup hook errors on fresh installs • Post-merge hunk verification — reapply-patches detects silently dropped hunks after three-way merge • detectConfigDir fix — Claude Code users no longer see false "update available" warnings when multiple runtimes are installed • 3 bug fixes — Milestone backlog preservation, detectConfigDir priority, and npm package manifest ---