gsd

What This Skill Does

GSD (Get Shit Done) is a comprehensive project orchestration engine for OpenClaw, porting the high-performance logic of the Claude Code workflow into a structured agentic environment. It serves as a full-cycle project manager, developer, and auditor, taking vague ideas and transforming them into production-ready software through a multi-step, systematic approach. The core philosophy of GSD is to eliminate ambiguity; it handles everything from initial deep-context gathering and multi-threaded automated domain research to granular roadmap development and wave-based parallel code execution. By breaking complex builds into discrete, verifiable phases, the GSD skill ensures that progress is incremental, measurable, and highly resilient to project scope creep.

Installation

To integrate this skill into your environment, use the OpenClaw terminal command: clawhub install openclaw/skills/skills/glittercowboy/gsd

Use Cases

• Brownfield Development: Use map-codebase to let the agent ingest legacy code before initiating a refactor or new feature injection.
• Greenfield MVP Building: Use new-project to move from a high-level product concept to a fully scoped architectural roadmap and implemented code structure.
• Complex Bug Resolution: Utilize the debug [issue] command to maintain persistent state and context across multiple troubleshooting sessions.
• Iterative Project Management: Use milestones and phase management tools (add-phase, insert-phase) to maintain a professional, agile workflow for long-term coding projects.

Example Prompts

1. "/gsd new-project: I want to build a real-time collaborative whiteboarding app using React and WebSockets. Please guide me through the setup."
2. "/gsd plan-phase 2 --research: Re-evaluate the technical requirements for the authentication module and create an updated plan for the team."
3. "/gsd debug 'The user settings form fails to persist data when switching between tabs in the profile section.'"

Tips & Limitations

• Leverage Flags: Use --skip-research if you already have a well-defined technical spec, or use --gaps when addressing verification failures to avoid redundant full-phase execution.
• Context is Key: While GSD is powerful, it relies heavily on the quality of the initial new-project context gathering. Take the time to answer the agent's prompts thoroughly at the start of the session.
• Verification: Always utilize the verify-work [N] command. The agent is designed to be self-correcting; letting it perform conversational UAT (User Acceptance Testing) significantly reduces long-term maintenance costs.