Plugin

get-shit-done

Name: get-shit-done
Author: glittercowboy

Drive full project lifecycles in Claude Code using phased roadmaps: initialize repos, create/insert milestones and phases, generate executable plans, run tasks with atomic git commits, track progress/issues, pause/resume work, verify via UAT, and archive completions.

Component Overview

/add-phase, /complete-milestone +20

Commands

Agents

Skills

Hooks

MCP Servers

LSP Servers

Output Styles

Install

npx claudepluginhub glittercowboy/get-shit-done --plugin get-shit-done

Component Details

Commands (22)

gsd:add-phase

/add-phase

Add phase to end of current milestone in roadmap

gsd:complete-milestone

/complete-milestone

Archive completed milestone and prepare for next version

gsd:consider-issues

/consider-issues

Review deferred issues with codebase context, close resolved ones, identify urgent ones

gsd:create-roadmap

/create-roadmap

Create roadmap with phases for the project

gsd:discuss-milestone

/discuss-milestone

Gather context for next milestone through adaptive questioning

gsd:discuss-phase

/discuss-phase

Gather phase context through adaptive questioning before planning

gsd:execute-plan

/execute-plan

Execute a PLAN.md file

gsd:help

/help

Show available GSD commands and usage guide

gsd:insert-phase

/insert-phase

Insert urgent work as decimal phase (e.g., 72.1) between existing phases

gsd:list-phase-assumptions

/list-phase-assumptions

Surface Claude's assumptions about a phase approach before planning

gsd:map-codebase

/map-codebase

Analyze codebase with parallel Explore agents to produce .planning/codebase/ documents

gsd:new-milestone

/new-milestone

Create a new milestone with phases for an existing project

gsd:new-project

/new-project

Initialize a new project with deep context gathering and PROJECT.md

gsd:pause-work

/pause-work

Create context handoff when pausing work mid-phase

gsd:plan-fix

/plan-fix

Plan fixes for UAT issues from verify-work

gsd:plan-phase

/plan-phase

Create detailed execution plan for a phase (PLAN.md)

gsd:progress

/progress

Check project progress, show context, and route to next action (execute or plan)

gsd:remove-phase

/remove-phase

Remove a future phase from roadmap and renumber subsequent phases

gsd:research-phase

/research-phase

Research how to implement a phase before planning

gsd:resume-task

/resume-task

Resume an interrupted subagent execution

gsd:resume-work

/resume-work

Resume work from previous session with full context restoration

gsd:verify-work

/verify-work

Guide manual user acceptance testing of recently built features

README

GET SHIT DONE

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

npx get-shit-done-cc

Works on Mac, Windows, and Linux.

GSD Install

"If you know clearly what you want, this WILL build it for you. No bs."

"I've done SpecKit, OpenSpec and Taskmaster — this has produced the best results for me."

"By far the most powerful addition to my Claude Code. Nothing over-engineered. Literally just gets shit done."

Trusted by engineers at Amazon, Google, Shopify, and Webflow.

Why I Built This · How It Works · Commands · Why It Works

Why I Built This

I'm a solo developer. I don't write code — Claude Code does.

Other spec-driven development tools exist; BMAD, Speckit... But they all seem to make things way more complicated than they need to be (sprint ceremonies, story points, stakeholder syncs, retrospectives, Jira workflows) or lack real big picture understanding of what you're building. I'm not a 50-person software company. I don't want to play enterprise theater. I'm just a creative person trying to build great things that work.

So I built GSD. The complexity is in the system, not in your workflow. Behind the scenes: context engineering, XML prompt formatting, subagent orchestration, state management. What you see: a few commands that just work.

The system gives Claude everything it needs to do the work and verify it. I trust the workflow. It just does a good job.

That's what this is. No enterprise roleplay bullshit. Just an incredibly effective system for building cool stuff consistently using Claude Code.

— TÂCHES

Vibecoding has a bad reputation. You describe what you want, AI generates code, and you get inconsistent garbage that falls apart at scale.

GSD fixes that. It's the context engineering layer that makes Claude Code reliable. Describe your idea, let the system extract everything it needs to know, and let Claude Code get to work.

Who This Is For

People who want to describe what they want and have it built correctly — without pretending they're running a 50-person engineering org.

Getting Started

npx get-shit-done-cc

That's it. Verify with /gsd:help.

Non-interactive Install (Docker, CI, Scripts)

npx get-shit-done-cc --global   # Install to ~/.claude/
npx get-shit-done-cc --local    # Install to ./.claude/

Use --global (-g) or --local (-l) to skip the interactive prompt.

Development Installation

Clone the repository and run the installer locally:

git clone https://github.com/glittercowboy/get-shit-done.git
cd get-shit-done
node bin/install.js --local

Installs to ./.claude/ for testing modifications before contributing.

Recommended: Skip Permissions Mode

GSD is designed for frictionless automation. Run Claude Code with:

claude --dangerously-skip-permissions

[!TIP] This is how GSD is intended to be used — stopping to approve date and git commit 50 times defeats the purpose.

Alternative: Granular Permissions

If you prefer not to use that flag, add this to your project's .claude/settings.json:

{
  "permissions": {
    "allow": [
      "Bash(date:*)",
      "Bash(echo:*)",
      "Bash(cat:*)",
      "Bash(ls:*)",
      "Bash(mkdir:*)",
      "Bash(wc:*)",
      "Bash(head:*)",
      "Bash(tail:*)",
      "Bash(sort:*)",
      "Bash(grep:*)",
      "Bash(tr:*)",
      "Bash(git add:*)",
      "Bash(git commit:*)",
      "Bash(git status:*)",
      "Bash(git log:*)",
      "Bash(git diff:*)",
      "Bash(git tag:*)"
    ]
  }
}

How It Works

1. Start with an idea

/gsd:new-project

The system asks questions. Keeps asking until it has everything — your goals, constraints, tech preferences, edge cases. You go back and forth until the idea is fully captured. Creates PROJECT.md.

2. Create roadmap

/gsd:create-roadmap

View full README on GitHub

Similar Plugins

prompts.chat

159.9k

470

Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.

Stats

Version1.3.20

Stars1288

Installs101

MaintenanceExcellent

LicenseMIT

AddedJan 8, 2026

Actions

View on GitHub View README Plugin Marketplace JSON

Available In

get-shit-done1,290

GET SHIT DONE

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

npx get-shit-done-cc

Works on Mac, Windows, and Linux.

GSD Install

"If you know clearly what you want, this WILL build it for you. No bs."

"I've done SpecKit, OpenSpec and Taskmaster — this has produced the best results for me."

"By far the most powerful addition to my Claude Code. Nothing over-engineered. Literally just gets shit done."

Trusted by engineers at Amazon, Google, Shopify, and Webflow.

Why I Built This · How It Works · Commands · Why It Works

Why I Built This

I'm a solo developer. I don't write code — Claude Code does.

The system gives Claude everything it needs to do the work and verify it. I trust the workflow. It just does a good job.

That's what this is. No enterprise roleplay bullshit. Just an incredibly effective system for building cool stuff consistently using Claude Code.

— TÂCHES

Vibecoding has a bad reputation. You describe what you want, AI generates code, and you get inconsistent garbage that falls apart at scale.

GSD fixes that. It's the context engineering layer that makes Claude Code reliable. Describe your idea, let the system extract everything it needs to know, and let Claude Code get to work.

Who This Is For

People who want to describe what they want and have it built correctly — without pretending they're running a 50-person engineering org.

Getting Started

npx get-shit-done-cc

That's it. Verify with /gsd:help.

Non-interactive Install (Docker, CI, Scripts)

npx get-shit-done-cc --global   # Install to ~/.claude/
npx get-shit-done-cc --local    # Install to ./.claude/

Use --global (-g) or --local (-l) to skip the interactive prompt.

Development Installation

Clone the repository and run the installer locally:

git clone https://github.com/glittercowboy/get-shit-done.git
cd get-shit-done
node bin/install.js --local

Installs to ./.claude/ for testing modifications before contributing.

Recommended: Skip Permissions Mode

GSD is designed for frictionless automation. Run Claude Code with:

claude --dangerously-skip-permissions

[!TIP] This is how GSD is intended to be used — stopping to approve date and git commit 50 times defeats the purpose.

Alternative: Granular Permissions

If you prefer not to use that flag, add this to your project's .claude/settings.json:

{
  "permissions": {
    "allow": [
      "Bash(date:*)",
      "Bash(echo:*)",
      "Bash(cat:*)",
      "Bash(ls:*)",
      "Bash(mkdir:*)",
      "Bash(wc:*)",
      "Bash(head:*)",
      "Bash(tail:*)",
      "Bash(sort:*)",
      "Bash(grep:*)",
      "Bash(tr:*)",
      "Bash(git add:*)",
      "Bash(git commit:*)",
      "Bash(git status:*)",
      "Bash(git log:*)",
      "Bash(git diff:*)",
      "Bash(git tag:*)"
    ]
  }
}

How It Works

1. Start with an idea

/gsd:new-project

2. Create roadmap

/gsd:create-roadmap

get-shit-done

Component Overview

Install

Component Details

Commands (22)

README

GET SHIT DONE

Why I Built This

Who This Is For

Getting Started

Recommended: Skip Permissions Mode

How It Works

1. Start with an idea

2. Create roadmap

Similar Plugins

prompts.chat

get-shit-done

Component Overview

Install

Component Details

Commands (22)

README

GET SHIT DONE

Why I Built This

Who This Is For

Getting Started

Recommended: Skip Permissions Mode

How It Works

1. Start with an idea

2. Create roadmap

Similar Plugins

prompts.chat

fullstack-dev-skills

agent-teams

ralph-loop

plugin-dev

planning-with-files