mcpField
G
get-shit-done

get-shit-done

github.com/shoootyouAgent workflows22628 installsUpdated 32w ago
Repository

About get-shit-done

A Claude Code skill for running Get Shit Done (GSD) commands. It directs the agent to load the corresponding skill files, follow referenced workflows, and use the required output formats for planning and execution.

Key features

  1. 01Route GSD commands to skill files
  2. 02Load referenced files as context
  3. 03Map tasks to available tools
  4. 04Follow defined output formats

Use cases

  1. 01Run a GSD planning command
  2. 02Execute a phase workflow
  3. 03Use GSD roadmap or verification tasks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/shoootyou/get-shit-done-multi --skill get-shit-done

After installing, type/get-shit-donein Claude Code to confirm it loaded.

Details

From the project README

Get Shit Done (GSD) Skill for Claude Code

When to use

  • Use this skill when the user asks for GSD or uses a {{COMMAND_PREFIX}}* command.
  • Use it for structured planning, phase execution, verification, or roadmap work.

How to run commands

Claude Code supports custom slash commands. Commands starting with {{COMMAND_PREFIX}} are custom skills.

Commands are installed as individual skills in {{PLATFORM_ROOT}}/skills/. Load the corresponding skill:

{{PLATFORM_ROOT}}/skills/gsd-<command>/SKILL.md

Example:

  • {{COMMAND_PREFIX}}new-project -> {{PLATFORM_ROOT}}/skills/gsd-new-project/SKILL.md
  • {{COMMAND_PREFIX}}help -> {{PLATFORM_ROOT}}/skills/gsd-help/SKILL.md

File references

Command files and workflows include @path references. These are mandatory context. Use the Read tool to load each referenced file before proceeding.

Tool mapping

  • "Bash tool" → use the Bash tool
  • "Read/Write" → use Read/Write tools
  • "AskUserQuestion" → ask directly in chat and provide explicit numbered options
  • "Task/subagent" → prefer a matching custom agent from {{PLATFORM_ROOT}}/agents when available; otherwise adopt that role in-place

Output expectations

Follow the XML or markdown formats defined in the command and template files exactly. These files are operational prompts, not documentation.

Paths

Resources are installed under {{PLATFORM_ROOT}}/get-shit-done. Individual skills are under {{PLATFORM_ROOT}}/skills/gsd-*/. Use those paths when command content references platform paths.

Comments

Markdown supported