FIND-20260323-020

adhoc HIGH 2026-03-23 — via @James #Innovation

get-shit-done (GSD) — Spec-Driven Meta-Prompting System for Claude Code

GSD is a lightweight meta-prompting and context engineering system installable via npx get-shit-done-cc@latest. It structures AI-assisted development into 6 repeatable phases using slash commands (/gsd:new-project, /gsd:plan-phase, /gsd:execute-phase, /gsd:verify-work, /gsd:ship). Key innovation: each execution task runs in a fresh 200k-token context, preventing context degradation that degrades output quality in long sessions. Supports parallel wave execution with dependency tracking. Currently 39,571 stars on GitHub, 3,213 forks, last commit today (2026-03-23). Active community with only 9 open issues. The system is runtime-agnostic: works with Claude Code, Gemini CLI, OpenCode, Codex, Copilot, and Cursor.

39,571 stars
3,213 forks
9 open issues
Language: JavaScript
Last commit: 2026-03-23
claude-code meta-prompting context-engineering spec-driven-development multi-agent devtools ai-workflow

Security Review

MIT
2026-03-23 (today)
0
ACTIVE
LOW
SAFE_TO_USE

ODS Impact

Directly applicable to the ODS ADLC/PDLC pipeline. GSD provides a structured multi-agent orchestration layer (discuss → plan → execute → verify → ship) that mirrors the ODS pipeline's BA/dev/review/PR flow. The XML-structured task plans, wave-based parallel execution, and context state files (PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md) could formalize the ODS agent workflow, reduce context degradation in long sessions, and provide a repeatable spec-driven development methodology for all 10 shared services.

The /gsd:new-project and /gsd:plan-phase commands are especially relevant for onboarding new ODS services with consistent spec artifacts. The "yolo" auto-approve mode aligns with the ODS ADLC autonomous operation philosophy. Evaluation recommended for P1 service development (DocStore, PDF Engine, Notification Hub).

How It Works

GSD installs a set of slash-command skills into the AI coding tool. The workflow is:

  1. Initialize — Guided questions, domain research, requirements extraction, roadmap creation
  2. Discuss — Capture implementation preferences before planning
  3. Plan — Research, task decomposition, atomic plans with XML structure
  4. Execute — Parallel waves with fresh 200k-token context per task
  5. Verify — User acceptance testing with structured checklist
  6. Ship — PR creation and phase iteration

Configuration via .planning/config.json: mode (interactive/yolo), model profile (quality/balanced/budget), git strategy (none/phase/milestone).

View source →