Agent skill
get-shit-done
Structured spec-driven workflow for planning and executing software projects with GitHub Copilot CLI.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/copilot
SKILL.md
Get Shit Done (GSD) Skill for GitHub Copilot CLI
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
GitHub Copilot CLI does not support custom slash commands. Treat inputs that start with {{COMMAND_PREFIX}} as command invocations.
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 execute tool
- "Read/Write" → use read/edit tools
- "AskUserQuestion" → ask directly in chat and provide explicit numbered options
- "Task/subagent" → prefer a matching custom agent from
{{PLATFORM_ROOT}}/agentswhen 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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?