gsd▌
ctsstc/get-shit-done-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Structured project management system for solo developers using Claude agents to plan, execute, and ship software.
- ›Provides 19+ commands covering project initialization, phase planning/execution, codebase mapping, debugging, and verification workflows
- ›Organizes work into goal-backward phases with atomic commits, parallel execution waves, and context budgeting to maintain quality
- ›Generates .planning/ directory structure with project context, requirements, roadmaps, phase artifacts, and
Get Shit Done (GSD) - Project Management System
A comprehensive project management system designed for solo developers working with Claude AI agents. GSD provides structured workflows for project initialization, planning, execution, verification, and debugging.
Overview
GSD is a modular agent-based system that transforms project ideas into shipped software through:
- Deep questioning - Extract user vision and requirements
- Domain research - Discover standard stacks and patterns
- Roadmap creation - Break requirements into phases
- Phase planning - Create executable plans with verification
- Execution - Implement plans with atomic commits
- Verification - Ensure goals are achieved, not just tasks done
- Debugging - Systematic investigation of issues
Core Philosophy
- Solo Developer + Claude Workflow - No teams, no stakeholders, no ceremonies
- Plans are Prompts - PLAN.md files ARE the execution prompts, not documents
- Goal-Backward Planning - Start from what must be TRUE, derive what to build
- Atomic Commits - Each task commits independently for clean history
- Quality Over Speed - Stop before context degrades (~50% usage)
- Ship Fast - Plan → Execute → Ship → Learn → Repeat
When to Use GSD
Use GSD when you need to:
- Initialize a new software project
- Plan and execute development phases
- Map an existing codebase
- Debug issues systematically
- Verify phase completion
- Track project progress and state
Quick Start Commands
New Project
/gsd:new-project
Initializes a new project with questioning → research → requirements → roadmap flow.
Plan a Phase
/gsd:plan-phase [phase-number]
Creates detailed execution plans with research and verification.
Execute a Phase
/gsd:execute-phase [phase-number]
Executes all plans in a phase with parallel execution support.
Map Codebase
/gsd:map-codebase [optional-focus-area]
Analyzes existing codebase with parallel mapper agents.
Debug Issues
/gsd:debug [issue-description]
Systematic debugging using scientific method and hypothesis testing.
Verify Phase
/gsd:verify-work [phase-number]
Goal-backward verification of phase completion.
Check Progress
/gsd:progress
Shows current project position, completed phases, and next steps.
Agent Skills
GSD includes specialized agents for different tasks:
- gsd-codebase-mapper - Explores and documents codebase structure
- gsd-planner - Creates executable phase plans
- gsd-executor - Executes plans with atomic commits
- gsd-debugger - Investigates bugs systematically
- gsd-verifier - Verifies goal achievement
- gsd-research-synthesizer - Synthesizes research outputs
- gsd-roadmapper - Creates project roadmaps
- gsd-phase-researcher - Researches phase implementation
- gsd-project-researcher - Researches domain ecosystem
- gsd-integration-checker - Verifies integrations work
- gsd-plan-checker - Validates plan quality
Command Skills
GSD provides commands for orchestrating the entire project lifecycle:
- gsd:new-project - Initialize new project
- gsd:map-codebase - Map existing codebase
- gsd:plan-phase - Plan a phase
- gsd:execute-phase - Execute a phase
- gsd:verify-work - Verify phase completion
- gsd:debug - Debug issues
- gsd:discuss-phase - Gather phase context
- gsd:research-phase - Research phase implementation
- gsd:complete-milestone - Complete milestone
- gsd:audit-milestone - Audit milestone
- gsd:add-phase - Add new phase
- gsd:insert-phase - Insert phase
- gsd:remove-phase - Remove phase
- gsd:add-todo - Add todo item
- gsd:check-todos - Check todos
- gsd:plan-milestone-gaps - Plan milestone gaps
- gsd:pause-work - Pause work
- gsd:resume-work - Resume work
- gsd:update - Update project state
- gsd:whats-new - Show what's new
Workflow Skills
Detailed workflow definitions for complex operations:
- discovery-phase - Phase discovery workflow
- execute-phase - Phase execution workflow
- diagnose-issues - Parallel UAT diagnosis
- map-codebase - Codebase mapping workflow
- discuss-phase - Phase discussion workflow
- verify-phase - Phase verification workflow
- verify-work - Work verification workflow
- transition - Phase transition workflow
- resume-project - Project resumption workflow
Reference Skills
Reference documents for best practices and guidelines:
- questioning - Deep questioning techniques
- tdd - Test-driven development patterns
- ui-brand - UI/UX guidelines
- verification-patterns - Verification methodologies
- git-integration - Git workflow patterns
- checkpoints - Checkpoint handling
- continuation-format - Continuation format specification
Project Structure
GSD creates a .planning/ directory with:
.planning/
├── PROJECT.md # Project context and vision
├── config.json # Workflow preferences
├── REQUIREMENTS.md # Scoped requirements
├── ROADMAP.md # Phase structure
├── STATE.md # Project memory and state
├── research/ # Domain research outputs
├── phases/ # Phase-specific artifacts
│ ├── XX-name/
│ │ ├── XX-PLAN.md
│ │ ├── XX-SUMMARY.md
│ │ ├── XX-CONTEXT.md
│ │ ├── XX-RESEARCH.md
│ │ ├── XX-VERIFICATION.md
│ │ └── XX-UAT.md
└── codebase/ # Codebase analysis
├── STACK.md
├── ARCHITECTURE.md
├── STRUCTURE.md
├── CONVENTIONS.md
├── TESTING.md
├── INTEGRATIONS.md
└── CONCERNS.md
Key Concepts
Goal-Backward Planning
Instead of asking "what should we build?", ask "what must be TRUE for the goal to be achieved?"
Forward: "Build authentication system" → task list Goal-Backward: "Users can securely access accounts" → derive what must exist
Atomic Commits
Each task commits independently with descriptive messages:
feat(01-01): implement user login
fix(01-02): fix password validation
test(01-03): add login tests
Context Budgeting
Plans complete within ~50% context usage to maintain quality:
- 0-30%: PEAK quality
- 30-50%: GOOD quality
- 50-70%: DEGRADING quality
- 70%+: POOR quality (avoid)
Wave-Based Execution
Plans are grouped into waves for parallel execution:
- Wave 1: Independent plans (no dependencies)
- Wave 2: Plans depending only on Wave 1
- Wave 3: Plans depending on Wave 2, etc.
Anti-Patterns to Avoid
- Enterprise PM Theater - No RACI matrices, sprint ceremonies, stakeholder management
- Horizontal Layers - Don't group by "all models, then all APIs" - group by features
- Vague Success Criteria - "Authentication works" → "User can log in with email/password"
- Time Estimates - Never estimate in hours/days/weeks
- Task Completion ≠ Goal Achievement - Verify outcomes, not just task completion
Getting Help
Each agent, command, and workflow has its own SKILL.md with detailed instructions. Use:
@skills/gsd/agents/for agent-specific help@skills/gsd/commands/for command-specific help@skills/gsd/workflows/for workflow-specific help@skills/gsd/references/for reference documentation
Version
GSD Version: 1.0.0 Last Updated: 2026-01-19
How to use gsd on Cursor
AI-first code editor with Composer
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 gsd
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches gsd from GitHub repository ctsstc/get-shit-done-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate gsd. Access the skill through slash commands (e.g., /gsd) 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
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.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 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▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★48 reviews- ★★★★★Evelyn Haddad· Dec 28, 2024
gsd has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Sakura Sanchez· Dec 28, 2024
gsd reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Olivia Yang· Dec 20, 2024
I recommend gsd for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Yusuf Li· Dec 20, 2024
Solid pick for teams standardizing on skills: gsd is focused, and the summary matches what you get after install.
- ★★★★★Evelyn Ndlovu· Dec 4, 2024
Registry listing for gsd matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Noah Martinez· Nov 23, 2024
gsd fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Advait Flores· Nov 19, 2024
We added gsd from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Michael Martin· Nov 11, 2024
Keeps context tight: gsd is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Lucas Dixit· Oct 18, 2024
gsd reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Kabir Sanchez· Oct 14, 2024
We added gsd from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 48