Claude Code supports custom slash commands. Commands starting with {{COMMAND_PREFIX}} are custom skills.
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
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
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
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
Submit your Claude Code skill and start earning
epx add shoootyou/get-shit-done-multi --skill get-shit-doneCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionget-shit-doneExecute the skills CLI command in your project's root directory to begin installation:
epx add shoootyou/get-shit-done-multi --skill get-shit-doneFetches get-shit-done from shoootyou/get-shit-done-multi and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/get-shit-done
Restart Cursor to activate get-shit-done. Access via /get-shit-donein your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
premortem
parcadei/continuous-claude-v3 · Productivity · same category
nestjs-best-practices
kadajett/agent-nestjs-skills · Productivity · same category
prd-to-plan
mattpocock/skills · Productivity · same category
pwa-expert
erichowens/some_claude_skills · Productivity · same category
flutter-performance
flutter/skills · Productivity · same category
sports-betting-analyzer
onewave-ai/claude-skills · Productivity · same category
Useful defaults in get-shit-done — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
get-shit-done has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for get-shit-done matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: get-shit-done is focused, and the summary matches what you get after install.
get-shit-done reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added get-shit-done from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: get-shit-done is the kind of skill you can hand to a new teammate without a long onboarding doc.
get-shit-done has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in get-shit-done — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
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