Menu
Structured spec-driven workflow for planning and executing software projects with Claude Code.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Reapply local modifications after a GSD update
Generate tests for a completed phase based on UAT criteria and implementation
Archive completed milestone and prepare for next version
Create detailed phase plan (PLAN.md) with verification loop
Add phase to end of current milestone in roadmap
Capture idea or task as todo from current conversation context
| name | get-shit-done |
| description | Structured spec-driven workflow for planning and executing software projects with Claude Code. |
{{COMMAND_PREFIX}}* command.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.mdCommand files and workflows include @path references. These are mandatory context. Use the Read tool to load each referenced file before proceeding.
{{PLATFORM_ROOT}}/agents when available; otherwise adopt that role in-placeFollow the XML or markdown formats defined in the command and template files exactly. These files are operational prompts, not documentation.
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.