get-shit-done

shoootyou/get-shit-done-multi · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

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

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

skill.md

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.

how to use get-shit-done

How to use get-shit-done on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add get-shit-done
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

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

The skills CLI fetches get-shit-done from GitHub repository shoootyou/get-shit-done-multi and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/get-shit-done

Reload or restart Cursor to activate get-shit-done. Access the skill through slash commands (e.g., /get-shit-done) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.774 reviews
  • Ishan Johnson· Dec 28, 2024

    Useful defaults in get-shit-done — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Maya Nasser· Dec 24, 2024

    get-shit-done has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Soo Haddad· Dec 20, 2024

    Registry listing for get-shit-done matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Nia Li· Dec 16, 2024

    Solid pick for teams standardizing on skills: get-shit-done is focused, and the summary matches what you get after install.

  • Pratham Ware· Dec 12, 2024

    get-shit-done reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ira Thomas· Dec 8, 2024

    We added get-shit-done from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ira Choi· Nov 27, 2024

    Keeps context tight: get-shit-done is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Kiara Torres· Nov 19, 2024

    get-shit-done has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Ishan Taylor· Nov 15, 2024

    Useful defaults in get-shit-done — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Nia Thomas· Nov 7, 2024

    I recommend get-shit-done for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 74

1 / 8