get-shit-done vs gsd-pi
Spec-driven coding workflows compared
get-shit-done is an archived JavaScript system for meta-prompting, context engineering, and spec-driven development with Claude Code. gsd-pi is an active TypeScript coding agent that manages planning, implementation, verification, and tracking through a local command-line workflow, with an optional web interface.
get-shit-done: Spec-Driven Development for Claude Code
get-shit-done is TÂCHES’s meta-prompting and context-engineering system for spec-driven development with Claude Code. This repository is archived; development has moved to GSD Core in the Open GSD repository.
gsd-pi: Plan and Build Software with a Coding Agent
GSD Pi is a local-first, TypeScript coding agent for planning, implementing, verifying, and tracking project work from the command line. It adds milestone-based workflows, Git worktree automation, and project memory to autonomous coding sessions.
| get-shit-done | gsd-pi | |
|---|---|---|
| Language | JavaScript | TypeScript |
| License | MIT | MIT |
| Stars | 64.2k | 1.3k |
| Forks | 5.4k | 113 |
| Last analyzed | Oct 29, 2026 | Oct 28, 2026 |
Key differences
- get-shit-done focuses on structuring work for Claude Code, while gsd-pi provides an agent workflow for carrying work from planning through verification.
- get-shit-done is archived and points users to GSD Core as its successor; gsd-pi is not archived and has active repository activity.
- get-shit-done is written in JavaScript; gsd-pi is written in TypeScript and requires Node.js 22.18.0 or later and Docker.
- gsd-pi organizes work into milestones, slices, and tasks, and records project context and validation evidence locally; get-shit-done is described as a meta-prompting and context-engineering system.
- gsd-pi supports Git worktrees, multiple model providers, and terminal or web interfaces; get-shit-done is presented as a Claude Code-focused workflow.
- Both projects use the MIT license, while get-shit-done has substantially more stars and forks than gsd-pi.
Choose get-shit-done if you…
- want to examine a spec-driven, context-engineering approach designed for Claude Code.
- are evaluating the archived project before moving to its named successor, GSD Core.
Choose gsd-pi if you…
- need a command-line agent workflow for planning, implementation, verification, and progress tracking.
- want milestone-based work, Git worktrees, and local records of project context.
- need terminal or web access, or options for running quick tasks with JSON output.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.