gsd

Get Shit Done for Claude Code

Plugin version: 4.0.1

GSD Plugin for Claude Code ensures your coding work gets done in a systematic, structured way. It prompts you only for the important design and architectural decisions that actually need your judgment, and it splits each step into its own focused subcontext so token use stays optimised across long projects.

Under the hood, a performance-optimized plugin evolution of GSD for Claude Code: reduces per-turn token overhead by ~92%, adds MCP-backed project state, auto-resumes across /compact, and bundles everything into a single-install plugin.

Installation

GSD Plugin installs inside a Claude Code session, not from your host shell. If you have never used Claude Code plugins before, follow these steps in order.

No prerequisites

As of v2.42.0 the plugin bundles its own copy of the GSD SDK at sdk/dist/cli.js and ships a bin/gsd-sdk wrapper that Claude Code automatically puts on PATH for plugin Bash calls. You no longer need to npm install -g get-shit-done-cc (or its successor get-shit-done-redux). Closes #4.

Pre-install: remove any pre-v2.42.0 global SDK install

If you previously installed get-shit-done-cc / get-shit-done-redux or @gsd-build/sdk / @gsd-redux/sdk via npm -g (or npx), the global binary at /opt/homebrew/bin/gsd-sdk (Apple Silicon) or /usr/local/bin/gsd-sdk (Intel macOS / Linux) takes precedence in $PATH over the plugin's bundled wrapper. The global SDK does NOT honor CLAUDE_PLUGIN_ROOT, so every plugin workflow that calls bare gsd-sdk (init queries, agent-skill lookups, config reads) reports agents_installed: false, and skills like /gsd:new-project silently degrade by skipping the parallel research path. The plugin's v2.42.5 wrapper-env-export patch only fires when the wrapper itself is invoked, so a shadowing global bypasses it.

Check whether you have a shadowing install:

which gsd-sdk

If the output is anything OTHER than a path under ~/.claude/plugins/cache/gsd-plugin/ (typical bad outputs are /opt/homebrew/bin/gsd-sdk or /usr/local/bin/gsd-sdk), uninstall it from your host shell before going further:

npm uninstall -g @gsd-build/sdk
npm uninstall -g get-shit-done-cc
npm uninstall -g @gsd-redux/sdk
npm uninstall -g @opengsd/get-shit-done-redux
npm uninstall -g get-shit-done-redux   # if you tried the unscoped name (404s on npm; v2.43.x docs incorrectly referenced this form, fixed in v2.44.6)

Re-run which gsd-sdk. The expected post-uninstall output is either a path under ~/.claude/plugins/cache/gsd-plugin/ (after the plugin is installed in Step 3) or gsd-sdk not found (before installation). Both are correct.

If you skip this step and install the plugin anyway, v2.43.1+ ships a gsd-shadowing-sdk-detector SessionStart hook that will detect the conflict at the start of every Claude Code session and emit a one-time advisory pointing back to this section.

Step 1: Trust GitHub's SSH host key (first time only on a new machine)

/plugin marketplace add clones over SSH. On a fresh machine GitHub's host key is unknown, which makes the non-interactive git clone Claude Code runs fail silently. Prime known_hosts once from your host shell:

ssh -T [email protected]

Type yes at the "Are you sure you want to continue connecting?" prompt. The follow-up "Permission denied (publickey)" message is expected for a public-repo clone via SSH and harmless; you only needed the host key fingerprint to land in ~/.ssh/known_hosts. Skip this step if you have used [email protected] from this machine before.

Step 2: Launch Claude Code

From your host shell (Terminal, iTerm, etc.), in any directory:

claude --dangerously-skip-permissions

The --dangerously-skip-permissions flag is recommended for the install flow: it lets the plugin marketplace add, plugin install, and MCP server bootstrap run without a wall of permission prompts. You can launch with plain claude later if you prefer to approve each tool use.

Step 3: Add the marketplace and install the plugin

You should now be inside a Claude Code session (you'll see the Claude Code prompt, not your shell prompt). Type these three commands at the Claude Code prompt:

/plugin marketplace add jnuyens/gsd-plugin
/plugin install gsd@gsd-plugin
/reload-plugins

That's it. This installs everything: slash commands, agent definitions, hooks, and an MCP server for project state. The /reload-plugins step activates the freshly installed plugin in your current session; without it the slash commands and hooks aren't loaded until you restart Claude Code. Enable auto-update for the marketplace in Claude Code settings to receive updates automatically.

Quick start