Skip to content

gsd-* — Get Shit Done framework family

← Skills From the community

Slash command /gsd-*

Get Shit Done framework family

A light-weight meta-, context-engineering and spec-driven development system for . A family of commands (`:new-project`, `gsd:plan-phase`, `gsd:execute-phase`, `gsd:progress`, etc.) for managing multi-week projects with persistent `.planning/` state and per-phase artefacts.

advanced ⏱ ~half a day per phase on multi-week projects View source ↗

The gsd-* family is the heaviest workflow option in the team’s toolbox — for projects that genuinely span weeks or months, not one sitting.

What you get: a persistent .planning/ folder with roadmap, milestones, per-phase artefacts (discuss / spec / plan / execute / verify / secure), and an audit trail. Pick it up next week and Claude remembers exactly where you left off.

When it’s right:

  • Long horizon (weeks/months)
  • Multiple collaborators
  • Traceability matters
  • You’ll pause and resume

When it’s overkill: one-off scripts, single-sitting prototypes — use plain or /team instead.

Common entry points: /gsd:new-project, /gsd:plan-phase, /gsd:execute-phase, /gsd:progress, /gsd:help. See /hub-glossary gsd for the broader framework explanation.

Access

Public — no access request needed. The canonical upstream is gsd-build/get-shit-done by TÂCHES.

Next skill →

/team — multi-agent build orchestrator

Orchestrates a multi- team — refiner, scanner, investigator, planner, designer, parallel coders, reviewer, dependency validator, test builder, integration verifier — to take a request from idea to merged code in one sitting.