gsd-build/get-shit-done

A light-weight and powerful meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 50 minutes ago
Added to GitGenius on February 16th, 2026
Created on December 14th, 2025
Open Issues & Pull Requests: 0 (+0)
Number of forks: 5,464
Total Stargazers: 64,652 (+0)
Total Subscribers: 269 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.4 hours
Mean response time: 37.7 hours
90th percentile: 2.9 days
Tracked items: 1,859

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 9% of issues opened in the past year have been closed. Three people close 91% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (814)
  • needs-triage (615)
  • enhancement (364)
  • confirmed (251)
  • confirmed-bug (233)
  • area: workflow (206)
  • priority: medium (178)
  • approved-enhancement (175)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Get Shit Done is a meta-prompting and context engineering system designed for Claude Code that enables spec-driven development workflows.

The tool addresses the challenge of maintaining consistent context and specifications across AI-assisted development sessions. It works by providing a lightweight framework for organizing prompts, context, and development specifications in a way that Claude Code can reliably interpret and act upon, reducing the friction between human intent and AI code generation.

The system suits developers who work extensively with Claude Code and want to establish repeatable, specification-driven development patterns. It is particularly valuable for projects where maintaining clear context across multiple development sessions matters, or where teams need consistent approaches to how they communicate requirements to AI assistants. The tool is designed to be lightweight, making it accessible for projects of varying scale without heavy overhead.

Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker is dominated by bug reports, enhancement requests, and confirmed issues, indicating active triage and prioritization of reported problems.