Skip to content

amanpal3/Dr-SKILLs / .agent/plugins/gsd/skills/gsd

Master Get Shit Done (GSD) methodology and workflow system. Enforces spec-driven development, planning locks, state persistence, context hygiene, and empirical verification. Use when the user mentions GSD, Get Shit Done, or slash commands like /new-project, /map, /plan, /execute, /verify, /sprint, /debug, /progress, /pause, /resume.

Get Shit Done (GSD) — Master Workflow System


Core Principles

  1. Plan Before You Build — No code is written until SPEC.md and PLAN.md are finalized.
  2. State Is Sacred — Every significant milestone and task updates .gsd/STATE.md.
  3. Context Is Limited — Stop before quality degrades (>50-70% context). Dump state and refresh.
  4. Verify Empirically — Every task requires verifiable proof (commands, test output, browser checks).

Lifecycle Commands

WorkflowCommandPurposeOutput Artifact
Initialize/new-projectInteractive questioning & spec discovery.gsd/SPEC.md, .gsd/ROADMAP.md, .gsd/STATE.md
Map/mapAnalyzes codebase and architectures.gsd/ARCHITECTURE.md, .gsd/STACK.md
Plan/plan [N]Generates atomic wave-based execution plans for Phase N.gsd/phases/N/XX-PLAN.md
Execute/execute [N]Executes Phase N plans with atomic commitsImplemented code + XX-SUMMARY.md
Verify/verify [N]Validates phase must-haves against reality.gsd/phases/N/VERIFICATION.md
Debug/debug [issue]Systematic 3-strike root cause debugging.gsd/DEBUG.md
Sprint/sprintAutonomous multi-phase planning & executionCompleted milestone
Pause/Resume/pause, /resumeContext checkpointing & session state restoration.gsd/STATE.md
Progress/progressReal-time roadmap tracking and state auditStatus summary

Sub-Skills Directory

The GSD methodology utilizes specialized modular sub-skills:

  • gsd-planner — Phase decomposition, task sizing, and wave dependency mapping.
  • gsd-executor — Autonomous task implementation with atomic commits.
  • gsd-verifier — Goal-backward empirical validation.
  • gsd-debugger — 3-strike debugging protocol.
  • gsd-codebase-mapper — Codebase inspection and architecture generation.
  • gsd-context-compressor — Memory pruning and state preservation.
  • gsd-context-health-monitor — Context pressure tracking.
  • gsd-plan-checker — Plan quality and atomicity auditing.
  • gsd-subagent-delegation — Multi-agent parallel execution.
  • gsd-token-budget — Context window allocation and token budgeting.

Quality Degradation & Context Rules

Context Usage | Quality | Action
0% - 30%      | PEAK    | Comprehensive planning & heavy analysis
30% - 50%     | GOOD    | Focused execution
50% - 70%     | DEGRADE | Wrap up active task, run /pause
70%+          | POOR    | Mandatory state dump & start fresh session
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall