Get Shit Done (GSD) Skill for Codex CLI

When to use

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

How to run commands

Codex CLI supports custom commands with $ prefix. Commands starting with $gsd- are custom skills.

Commands are installed as individual skills in .codex/skills/. Load the corresponding skill:

.codex/skills/gsd-<command>/SKILL.md

Example:

• $gsd-new-project -> .codex/skills/gsd-new-project/SKILL.md
• $gsd-help -> .codex/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 .codex/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 .codex/get-shit-done. Individual skills are under .codex/skills/gsd-*/. Use those paths when command content references platform paths.