Get Shit Done (GSD), tested — and it has moved

The famous meta-prompting and spec-driven development system for Claude Code. Before anything else, the fact most listings have not caught up with: the 64,696-star repo gsd-build/get-shit-done is archived. Development continues as GSD Core at open-gsd/gsd-core. We installed the live version.

The move, since nobody else seems to have noticed

Open the old repo today and the README is a redirect notice: "This repository is no longer the active home for GSD development." The project continues as GSD Core under an open-governance org, shipped as the npm package @opengsd/gsd-core, with commits landing daily. Meanwhile, as of our test date, the skill directories we checked still link the archived repo and quote its 64.8k stars. If you starred, forked, or installed from gsd-build/get-shit-done, the place to be is the new org — and star counts you see quoted for "GSD" are almost certainly the old repo's.

What it is

GSD Core is a context-engineering framework that drives coding agents through a disciplined five-step loop per milestone — Discuss, Plan, Execute, Verify, Ship. Its target is context rot: quality decay as an agent's context window fills. The mechanism is to run research, planning and execution in fresh-context subagents while the main session stays lean. Unlike everything else in our first batch, this is not a skill you drop into .claude/skills/ — it is an installer that provisions a whole working system.

The install, as it actually happened

npx @opengsd/gsd-core@latest --local --claude

1.8 seconds, no prompts with the right flags (the plain command runs an interactive installer covering seventeen runtimes — Claude Code, Codex, Cursor, OpenCode and more). What it wrote into .claude/ in our project: 71 slash commands (/gsd-new-project, /gsd-onboard, /gsd-plan-phase…), 34 agents, a set of lifecycle hooks (context monitors on Stop/SubagentStop/PreCompact, config reload), plus a file manifest, install-state, and a migration journal with checksums. It correctly skipped status-line configuration for a local install to avoid clobbering profile-level settings — the kind of detail that signals a mature installer. Version tested: v1.8.0.

What broke

Nothing broke. Install and the minimal use case both ran clean on first try — rarer than you would think, and worth saying explicitly.

Who it's for

Developers running multi-hour agent sessions on real codebases — the people who have felt an agent get dumber as a session drags. It is a methodology commitment, not a utility: 71 commands and 34 agents is a lot of surface, and you adopt its phase loop or you fight it. For a quick taste before committing, run the installer in a scratch repo and read what it writes; the uninstall story is simply deleting what the manifest lists.

FAQ

Is the old repo's documentation still valid?

Mostly, but point your bookmarks at the new org — the mintlify docs and the npm package both track GSD Core now, and version numbers restarted under the new package name.

Claude Code only?

No — the installer targets seventeen runtimes via flags (--claude, --codex, --cursor, …). We tested the Claude Code path.