get-shit-done
GSD (Get Shit Done) is a spec-driven development framework for AI coding agents that combines meta-prompting and context engineering with a set of slash commands, configurable workflows, and role-based agents to take a project from idea through implementation to a shipped PR.
MITPermissive — free to use in commercial and proprietary software, with attribution.View license →
Production readiness
5/5- Actively maintainedCommits in the last 6 months
- No known vulnerabilitiesNo OSV advisories
- Clear, usable licenseMIT (permissive)
- Proven adoptionWidely used
- Has documentationDocumentation indexed
npm install get-shit-done-ccOur analysis
An installable framework that layers structured, spec-driven workflows on top of AI coding agents (Claude Code, Codex CLI, etc.). It provides slash commands like /gsd-new-project and /gsd-ship, configurable model profiles, git branching policy, and role-based agent definitions to drive features from discussion through PR.
When to use get-shit-done
Useful when you want repeatable, disciplined AI-assisted development — turning a tracker issue or idea into a spec, then into code and a reviewable pull request — rather than ad-hoc chat prompting. Good for teams standardizing how they use coding agents across projects.
When not to
Overkill for quick one-off edits or small scripts where direct agent chat suffices. If you are not already working inside a supported agent CLI, or you want a full IDE-integrated assistant, an editor-native tool like Cursor or Continue is a better fit. It is also opinionated, so teams wanting a lightweight, unstructured workflow may find it heavy.
Strengths
- Imposes structure (spec → implement → ship) on otherwise freeform agent work
- Rich CLI tooling with JSON error modes and programmatic API for extensibility
- Supports multiple agents/CLIs and offers safe install-time migrations with dry-run and rollback
- Active release cadence with canary stream and multilingual docs
Trade-offs
- Highly opinionated workflow with a learning curve and its own command vocabulary
- Tied to specific agent CLIs and their versions (e.g., Codex CLI routability hotfixes)
- Conceptual overhead — meta-prompting and context engineering require buy-in
- Value depends heavily on the underlying agent's quality, which GSD does not control
Maturity
Mature and very actively maintained — past v1.42 with frequent hotfix releases, a documented canary channel, comprehensive contributor docs, and ~64k GitHub stars indicating strong community interest.
GSD Documentation
Comprehensive documentation for the Get Shit Done (GSD) framework — a meta-prompting, context engineering, and spec-driven development system for AI coding agents.
Language versions: English · Português (pt-BR) · 日本語 · 简体中文
Documentation Index
DocumentAudienceDescriptionArchitectureContributors, advanced usersSystem architecture, agent model, data flow, and internal designInstaller MigrationsContributorsArchitecture for safe install-time migrations, cleanup, preservation, dry-run planning, and rollbackFeature ReferenceAll usersFeature narratives and requirements for released features (see CHANGELOG for latest additions)v1.42.3 Release NotesAll usersHotfix release notes for 1.42.3 — Codex CLI 0.130.0 install routability and 11 other fixesv1.42.1 Release NotesAll usersStable release notes for the 1.42.1 releaseCommand ReferenceAll usersStable commands with syntax, flags, options, and examplesConfiguration ReferenceAll usersFull config schema, workflow toggles, model profiles, git branchingCustom PR Body SectionsAll usersHow to append project-specific PRD sections to /gsd-ship PR bodiesCLI Tools ReferenceContributors, agent authorsgsd-tools.cjs programmatic API for workflows and agentsJSON Error ModeContributors, agent authorsMachine-readable gsd-tools --json-errors failure envelopesAgent ReferenceContributors, advanced usersRole cards for primary agents — roles, tools, spawn patterns (the agents/ filesystem is authoritative)User GuideAll usersWorkflow walkthroughs, troubleshooting, and recoveryIssue-Driven OrchestrationAll usersRecipe for driving GSD from a tracker issue (GitHub / Linear / Jira) using existing primitives — no new commands or daemonContext MonitorAll usersContext window monitoring hook architectureDiscuss ModeAll usersAssumptions vs interview mode for discuss-phaseCanary StreamContributors, early adoptersdev → @canary dist-tag policy, when to install, rollback path
Quick Links
What's new: see v1.42.3 Release Notes (latest hotfix), v1.42.1 Release Notes, CHANGELOG, and upstream README for release highlights
Canary preview:
docs/CANARY.md— opt into the early-preview stream fromdev. Active cut:v1.50.0-canary.1Getting started: README → install →
/gsd-new-projectFull workflow walkthrough: User Guide
All commands at a glance: Command Reference
Configuring GSD: Configuration Reference
Customizing ship PR bodies: Custom PR Body Sections
How the system works internally: Architecture
Contributing or extending: CLI Tools Reference + Agent Reference