Get Shit Done

Why it's ranked here

The workflow is unusually explicit about traceability and verification. Requirements map to roadmap phases, plans receive pre-execution checks, and completed work is tested against phase goals rather than task completion alone. However, this repository is archived and redirects current development elsewhere, so it is useful for understanding the system but is the wrong source for current releases, issues, or contributions.

What's good

Its quality gates address concrete failure modes. The planner breaks work into context-sized tasks, checks dependencies and reachable references, and can require human approval before suspicious package installs. Executors report deviations and commit tasks separately. Verification audits requirement coverage, cross-phase integration, and whether tests genuinely prove their claims, including skipped tests, weak assertions, and circular expected values.

Tradeoffs

The full workflow carries substantial ceremony: research artifacts, requirements, roadmaps, phase discussions, plans, summaries, verification reports, and state tracking. That structure suits consequential projects better than tiny edits, for which separate fast and quick modes exist. Some capabilities depend on specific runtimes, while beta cloud planning is Claude Code only and may change or disappear. Preview packages may regress and are explicitly discouraged for production delivery.

How to use it well

Use it for multi-step engineering work where requirements, decisions, implementation, and proof must remain connected across long sessions. Start with project discovery, discuss each phase, then plan, execute, verify, and ship. Choose fast or quick modes for narrow tasks that do not justify the full artifact chain. Treat it as an orchestration and quality framework, not a replacement for your coding runtime, package registry checks, or human acceptance testing.

Observed

License

MIT

Package surface

Node.js npm package with three command-line binaries

Runtime requirement

Node.js 22 or newer

Languages

JavaScript and TypeScript surfaces

Interfaces

Runtime commands, command-line tools, and a typed SDK

Runtime support

Documentation covers Claude Code, Gemini CLI, Codex, Copilot, OpenCode, Kilo, and additional coding runtimes

Repository status

Archived redirect; active development continues in the Open GSD repository

Testing structure

Package scripts define unit, integration, install, security, slow, and coverage suites