claude

gsd

Get Shit Done — a structured planning/execution/verification workflow for Claude Code (/gsd:*), MCP-backed project state. Re-published here as a dependency of cairn so it installs automatically; upstream is jnuyens/gsd-plugin (tracking open-gsd/get-shit-done-redux). Installable on its own too.

1 on GitHubby Jasper Nuyensv5.1.0MITupdated 4 days agoworkflow
/

Plugin gsd from marketplace eventually-consistent-code in eventually-consistent-code-org/claude-plugins. Commands read from the repo's manifest — 3 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use and it starts local MCP servers. The exact commands are listed below; read them before installing.

What it installs

Skills (87)

  • add-backlog

    Add an idea to the backlog parking lot (999.x numbering)

  • add-phase

    Add phase to end of current milestone in roadmap

  • add-tests

    Generate tests for a completed phase based on UAT criteria and implementation

  • add-todo

    Capture idea or task as todo from current conversation context

  • ai-integration-phase

    Generate AI design contract (AI-SPEC.md) for phases that involve building AI systems — framework selection, implementation guidance from official docs, and evaluation strategy

  • analyze-dependencies

    Analyze phase dependencies and suggest Depends on entries for ROADMAP.md

  • audit-fix

    Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit

  • audit-milestone

    Audit milestone completion against original intent before archiving

  • audit-uat

    Cross-phase audit of all outstanding UAT and verification items

  • autonomous

    Run all remaining phases autonomously — discuss→plan→execute per phase

  • check-todos

    List pending todos and select one to work on

  • cleanup

    Archive accumulated phase directories from completed milestones

  • code-review-fix

    Auto-fix issues found by code review in REVIEW.md. Spawns fixer agent, commits each fix atomically, produces REVIEW-FIX.md summary.

  • code-review

    Review source files changed during a phase for bugs, security issues, and code quality problems

  • complete-milestone

    Archive completed milestone and prepare for next version

  • debug

    Systematic debugging with persistent state across context resets

  • discuss-phase

    Gather phase context through adaptive questioning before planning. Use --all to skip area selection and discuss all gray areas interactively. Use --auto to skip interactive questions (Claude picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --po

  • do

    Route freeform text to the right GSD command automatically

  • docs-update

    Generate or update project documentation verified against the codebase

  • eval-review

    Retroactively audit an executed AI phase's evaluation coverage — scores each eval dimension as COVERED/PARTIAL/MISSING and produces an actionable EVAL-REVIEW.md with remediation plan

  • execute-phase

    Execute all plans in a phase with wave-based parallelization

  • explore

    Socratic ideation and idea routing — think through ideas before committing to plans

  • extract-learnings

    Extract decisions, lessons, patterns, and surprises from completed phase artifacts

  • fast

    Execute a trivial task inline — no subagents, no planning overhead

  • forensics

    Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong

  • from-gsd2

    Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format

  • graphify

    Build, query, and inspect the project knowledge graph in .planning/graphs/

  • health

    Diagnose planning directory health and optionally repair issues

  • help

    Show available GSD commands and usage guide

  • import

    Ingest external plans with conflict detection against project decisions before writing anything.

  • inbox

    Triage and review all open GitHub issues and PRs against project templates and contribution guidelines

  • ingest-docs

    Scan a repo for mixed ADRs, PRDs, SPECs, and DOCs and bootstrap or merge the full .planning/ setup from them. Classifies each doc in parallel, synthesizes a consolidated context with a conflicts report, and routes to new-project or merge-milestone depending on whether .planning/ already exists.

  • insert-phase

    Insert urgent work as decimal phase (e.g., 72.1) between existing phases

  • intel

    Query, inspect, or refresh codebase intelligence files in .planning/intel/

  • join-discord

    Join the GSD Discord community

  • list-phase-assumptions

    Surface Claude's assumptions about a phase approach before planning

  • list-workspaces

    List active GSD workspaces and their status

  • manager

    Interactive command center for managing multiple phases from one terminal

  • map-codebase

    Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents

  • milestone-summary

    Generate a comprehensive project summary from milestone artifacts for team onboarding and review

  • mvp-phase

    Plan an MVP-mode phase — captures an "As a / I want to / So that" user story, runs SPIDR splitting, then delegates to plan-phase

  • new-ddd

    Initialize a new project using Documentation-Driven Development. Research, then write user-facing docs (SPEC.md) as the spec, then user validates docs, then phases derive from doc sections. Best for CLIs, libraries, SDKs, APIs, plugin systems, anything with a well-defined user-facing surface.

  • new-milestone

    Start a new milestone cycle — update PROJECT.md and route to requirements

  • new-project

    Initialize a new project with deep context gathering and PROJECT.md

  • new-workspace

    Create an isolated workspace with repo copies and independent .planning/

  • next

    Automatically advance to the next logical step in the GSD workflow

  • note

    Zero-friction idea capture. Append, list, or promote notes to todos.

  • pause-work
  • plan-milestone-gaps
  • plan-phase
  • plant-seed
  • pr-branch
  • profile-user
  • progress
  • quick
  • reapply-patches
  • reconcile
  • remember-access
  • remove-phase
  • remove-workspace
  • research-phase
  • resume-at
  • resume-work
  • review-backlog
  • review
  • scan
  • secure-phase
  • session-report
  • set-profile
  • settings
  • ship
  • sketch-wrap-up
  • sketch
  • spec-phase
  • spike-wrap-up
  • spike
  • stats
  • thread
  • ui-phase
  • ui-review
  • ultraplan-phase
  • undo
  • update
  • validate-phase
  • verify-work
  • version
  • workstreams

Subagents (33)

  • bm-advisor-researcher

    Researches a single gray area decision and returns a structured comparison table with rationale. Spawned by discuss-phase advisor mode.

  • bm-ai-researcher

    Researches a chosen AI framework's official docs to produce implementation-ready guidance — best practices, syntax, core patterns, and pitfalls distilled for the specific use case. Writes the Framework Quick Reference and Implementation Guidance sections of AI-SPEC.md. Spawned by /gsd:ai-integration

  • bm-assumptions-analyzer

    Deeply analyzes codebase for a phase and returns structured assumptions with evidence. Spawned by discuss-phase assumptions mode.

  • bm-code-fixer

    Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.

  • bm-code-reviewer

    Reviews source files for bugs, security issues, and code quality problems. Produces structured REVIEW.md with severity-classified findings. Spawned by /gsd:code-review.

  • bm-codebase-mapper

    Explores codebase and writes structured analysis documents. Spawned by map-codebase with a focus area (tech, arch, quality, concerns). Writes documents directly to reduce orchestrator context load.

  • bm-debug-session-manager

    Manages multi-cycle /gsd:debug checkpoint and continuation loop in isolated context. Spawns bm-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd:debug command.

  • bm-debugger

    Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /gsd:debug orchestrator.

  • bm-doc-classifier

    Classifies a single planning document as ADR, PRD, SPEC, DOC, or UNKNOWN. Extracts title, scope summary, and cross-references. Spawned in parallel by /gsd:ingest-docs. Writes a JSON classification file and returns a one-line confirmation.

  • bm-doc-synthesizer

    Synthesizes classified planning docs into a single consolidated context. Applies precedence rules, detects cross-ref cycles, enforces LOCKED-vs-LOCKED hard-blocks, and writes INGEST-CONFLICTS.md with three buckets (auto-resolved, competing-variants, unresolved-blockers). Spawned by /gsd:ingest-docs.

  • bm-doc-verifier

    Verifies factual claims in generated docs against the live codebase. Returns structured JSON per doc.

  • bm-doc-writer

    Writes and updates project documentation. Spawned with a doc_assignment block specifying doc type, mode (create/update/supplement), and project context.

  • bm-domain-researcher

    Researches the business domain and real-world application context of the AI system being built. Surfaces domain expert evaluation criteria, industry-specific failure modes, regulatory context, and what "good" looks like for practitioners in this field — before the eval-planner turns it into measurab

  • bm-eval-auditor

    Retroactive audit of an implemented AI phase's evaluation coverage. Checks implementation against the AI-SPEC.md evaluation plan. Scores each eval dimension as COVERED/PARTIAL/MISSING. Produces a scored EVAL-REVIEW.md with findings, gaps, and remediation guidance. Spawned by /gsd:eval-review orchest

  • bm-eval-planner

    Designs a structured evaluation strategy for an AI phase. Identifies critical failure modes, selects eval dimensions with rubrics, recommends tooling, and specifies the reference dataset. Writes the Evaluation Strategy, Guardrails, and Production Monitoring sections of AI-SPEC.md. Spawned by /gsd:ai

  • bm-executor

    Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.

  • bm-framework-selector

    Presents an interactive decision matrix to surface the right AI/LLM framework for the user's specific use case. Produces a scored recommendation with rationale. Spawned by /gsd:ai-integration-phase and /gsd-select-framework orchestrators.

  • bm-integration-checker

    Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.

  • bm-intel-updater

    Analyzes codebase and writes structured intel files to .planning/intel/.

  • bm-nyquist-auditor

    Fills Nyquist validation gaps by generating tests and verifying coverage for phase requirements

  • bm-pattern-mapper

    Analyzes codebase for existing patterns and produces PATTERNS.md mapping new files to closest analogs. Read-only codebase analysis spawned by /gsd:plan-phase orchestrator before planning.

  • bm-phase-researcher

    Researches how to implement a phase before planning. Produces RESEARCH.md consumed by bm-planner. Spawned by /gsd:plan-phase orchestrator.

  • bm-plan-checker

    Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.

  • bm-planner

    Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.

  • bm-project-researcher

    Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd:new-project or /gsd:new-milestone orchestrators.

  • bm-research-synthesizer

    Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by /gsd:new-project after 4 researcher agents complete.

  • bm-roadmapper

    Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd:new-project orchestrator.

  • bm-security-auditor

    Verifies threat mitigations from PLAN.md threat model exist in implemented code. Produces SECURITY.md. Spawned by /gsd:secure-phase.

  • bm-ui-auditor

    Retroactive 6-pillar visual audit of implemented frontend code. Produces scored UI-REVIEW.md. Spawned by /gsd:ui-review orchestrator.

  • bm-ui-checker

    Validates UI-SPEC.md design contracts against 6 quality dimensions. Produces BLOCK/FLAG/PASS verdicts. Spawned by /gsd:ui-phase orchestrator.

  • bm-ui-researcher

    Produces UI-SPEC.md design contract for frontend phases. Reads upstream artifacts, detects design system state, asks only unanswered questions. Spawned by /gsd:ui-phase orchestrator.

  • bm-user-profiler

    Analyzes extracted session messages across 8 behavioral dimensions to produce a scored developer profile with confidence levels and evidence. Spawned by profile orchestration workflows.

  • bm-verifier

    Verifies phase goal achievement through goal-backward analysis. Checks codebase delivers what phase promised, not just that tasks completed. Creates VERIFICATION.md report.

MCP servers (1)

  • gsd

    runs: ${CLAUDE_PLUGIN_ROOT}/bin/gsd-node ${CLAUDE_PLUGIN_ROOT}/mcp/server.cjs

Hooks (19)

  • SessionStart

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • SessionStart

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • SessionStart

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • SessionStart

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • SessionStart

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • PreToolUse

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • PreToolUse

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • PreToolUse

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • PreToolUse

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • PreToolUse

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • PostToolUse

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • PostToolUse

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • PostToolUse

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • PostToolUse

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • PostToolUse

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • PostToolUse

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • PreCompact

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • Stop

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

  • SubagentStop

    command -v node >/dev/null 2>&1 || { for d in "$HOME/.pixi/bin" /opt/homebrew/bin /usr/local/bin "$HOME/.volta/bin" "$HOME/.local/share/mise/shims" "$HOME/.asdf/shims" "$HOME/.nodenv/shims" "$HOME/.ni

View source on GitHub buildomator.com

More from eventually-consistent-code-org/claude-plugins

All 2 plugins →

cairn

claude

Cairn — marks the trail and remembers the path. Batteries-included: installing it pulls in GSD (a plugin dependency) and bootstraps the beads issue tracker (bd), then a single /cairn:init wires a project end to end. Wires the GSD planning workflow (/gsd:*) to beads (bd) so phases create/claim/close tracked work, optionally mirrors bd issues two-way (hub-and-spoke) to GitHub Issues, GitLab, Jira, Asana, and Azure Boards, and optionally makes the context-mode knowledge base intent-aware (scopes compressed memory to the active issue + phase). The integration conventions activate only in repos that use both GSD and beads.

3 skills · 18 commands · hooks

1

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development

9 skills · 1 command · 8 agents

wshobson/agents 42,461

beads

claudecodex

AI-supervised issue tracker for coding workflows

1 skill · 1 agent · hooks

gastownhall/beads 28,698

PRD generation and conversion skills for the Ralph autonomous agent loop

2 skills

snarktank/ralph 22,224

MiniMax AI skills library for frontend, fullstack, Android, iOS, shader, GIF sticker, document, presentation, spreadsheet, and multimodal media workflows

18 skills

MiniMax-AI/skills 13,828

worktrunk

claudecodex

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows. This plugin provides configuration guidance (LLM commit messages, project hooks, worktree paths), automatic activity tracking (🤖/💬 indicators in `wt list` showing active Claude sessions), and a `/wt-diff` pane showing each worktree's changes.

2 skills · hooks

max-sixty/worktrunk 12,481

Maintain gsd?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins2 plugins