ECC vs get-shit-done

Structured AI coding workflows compared

ECC and get-shit-done both bring more structure to AI-assisted development with Claude Code. ECC offers a broader toolkit of workflows and agent utilities across multiple harnesses, while get-shit-done focused on meta-prompting, context engineering, and specifications and is now archived.

ECCget-shit-done
LanguageJavaScriptJavaScript
LicenseMITMIT
Stars272k64.4k
Forks40.6k5.4k
Last analyzedOct 3, 2026Oct 3, 2026

Key differences

  • ECC combines reusable skills, specialized agents, optional hooks and memory, selectable rules, and security scanning; get-shit-done centers on meta-prompting, context engineering, and spec-driven development.
  • ECC supports Claude Code most fully and offers adapters for other coding-agent harnesses; get-shit-done was designed for Claude Code.
  • ECC is an active repository; get-shit-done is archived, with current development moved to GSD Core.
  • ECC describes installation options and requirements, including Node.js 18 or newer for its universal package; get-shit-done's supplied README redirects to GSD Core rather than providing setup instructions.
  • Both projects use JavaScript and the MIT license.

Choose ECC if you…

  • need reusable workflows for planning, implementation, testing, review, and security checks.
  • want specialized agents, optional session automation, or memory features.
  • use multiple coding-agent harnesses and can account for differing support.
Read the ECC analysis →

Choose get-shit-done if you…

  • want a lightweight, specification-focused approach to structuring Claude Code tasks.
  • are exploring meta-prompting and context engineering, and will use GSD Core for current development and project information.
Read the get-shit-done analysis →

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.