Skip to main content
ClaudeWave
ES, Spanish
open-gsd / Subagents

gsd-core

Git. Ship. Done - Core

  • 10.8k estrellas
  • 765 forks
  • 275 issues abiertos
  • Lenguaje: JavaScript
  • Licencia: MIT
  • actualizado

Instalación

Terminal
git clone https://github.com/open-gsd/gsd-core && cp gsd-core/*.md ~/.claude/agents/
  1. Clone the repository and copy the agent .md definitions into ~/.claude/agents (or .claude/agents inside a project).
  2. Start a new Claude Code session to load the agents.
  3. Delegate work to them with the Task/Agent tool or by name.

Nota editorial

GSD Core is a meta-prompting and spec-driven development framework installable via `npx @opengsd/gsd-core@latest` that organizes AI coding sessions into a repeating five-step phase loop: Discuss, Plan, Execute, Verify, and Ship. Its primary design goal is combating context rot, the gradual quality degradation that occurs as an AI agent's context window fills up, by offloading research, planning, and code execution to fresh-context subagents that each start with a clean 200k-token window rather than inheriting a cluttered session. Structured artifacts including `STATE.md` and `CONTEXT.md` persist information across session boundaries so work is not lost between phases. The framework integrates directly with Claude Code as its primary target but also supports Gemini CLI, Codex, Cursor, Windsurf, Copilot, and several other runtimes through the same installer. A `/gsd-new-project` slash command bootstraps new projects. Developers working on multi-session, multi-milestone codebases who have experienced AI output degradation over long sessions are the main intended audience.

Items instalables

24 items en este repositorio

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

Instalar

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-phase orchestrator.

Instalar

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

Instalar

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.

Instalar

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

Instalar

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.

Instalar

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

Instalar
gsd-debuggerSubagent

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

Instalar

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.

Instalar

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.

Instalar

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

Instalar

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

Instalar

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 measurable rubrics. Spawned by /gsd:ai-integration-phase orchestrator.

Instalar

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 orchestrator.

Instalar

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-integration-phase orchestrator.

Instalar
gsd-executorSubagent

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

Instalar

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.

Instalar

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

Instalar

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

Instalar

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

Instalar

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.

Instalar

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

Instalar

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

Instalar
gsd-plannerSubagent

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

Instalar
README

Resumen de Subagents

README completo en GitHub

GSD Core

Git. Ship. Done.

English · Português · 简体中文 · 日本語 · 한국어

A light-weight meta-prompting, context engineering, and spec-driven development system for Claude Code, OpenCode, Antigravity CLI, Kimi CLI, Kilo, Codex, Copilot, Cursor, Windsurf, and more.

npm version npm downloads Tests Discord GitHub stars License


What is GSD Core

GSD Core is a context-engineering and spec-driven development framework that drives AI coding agents (Claude Code, Codex, Antigravity CLI, Kimi CLI, Copilot, Cursor, and more) through a disciplined phase loop. It solves context rot — the quality degradation that accumulates as an AI fills its context window — by running all heavy research, planning, and execution work in fresh-context subagents while keeping your main session lean.


How it works

Each milestone repeats the same five-step loop, one phase at a time:

  1. Discuss — capture implementation decisions before anything is planned

  2. Plan — research, decompose, and verify the plan fits a fresh context window

  3. Execute — run plans in parallel waves; each executor starts with a clean 200k-token context

  4. Verify — walk through what was built; diagnose and fix before declaring done

  5. Ship — create the PR, archive the phase, repeat for the next one


Quickstart

npx @opengsd/gsd-core@latest

The installer prompts for your runtime (Claude Code, OpenCode, Antigravity CLI, Kimi CLI, Kilo, Codex, Copilot, Cursor, Windsurf, and more) and whether to install globally or locally. The installer is required for cross-runtime compatibility — do not copy files from agents/ or commands/ directly.

On another runtime or without Node.js? See Install on your runtime.

Once installed, start a new project or onboard an existing repo:

/gsd-new-project   # greenfield project
/gsd-onboard       # existing codebase

New here? Follow Your first project for a guided walkthrough from install to first shipped phase, or Onboarding an existing codebase for brownfield setup.


Documentation

What's new in 1.7.0 → docs/whats-new-1.7.0.md

Tutorials — learning by doing:

How-to guides — task-focused recipes:

Reference — authoritative facts:

Explanation — concepts and design decisions:

Full index: docs/README.md. Other languages: 日本語 · 한국어 · Português · 简体中文.


Why it works

Most AI-coding setups fail at scale because context bloat silently degrades output quality, there is no shared memory between sessions, and nothing verifies that code actually works. GSD Core solves all three: heavy work runs in fresh subagents, structured artifacts like STATE.md and CONTEXT.md survive session boundaries, and the verify step walks through what was built and generates fix plans before a phase is declared done. See docs/explanation/context-engineering.md for the full reasoning.

Troubleshooting? See docs/how-to/recover-and-troubleshoot.md.


Community

ProjectPlatform
gsd-opencodeOriginal OpenCode port
DiscordCommunity support

Star History


License

MIT License. See LICENSE for details.


Claude Code is powerful. GSD Core makes it reliable.

Topics
claude-codecontext-engineeringmeta-promptingspec-driven-development
Preguntas frecuentes

Lo que la gente pregunta sobre gsd-core

¿Qué es open-gsd/gsd-core?

open-gsd/gsd-core es subagents para el ecosistema de Claude AI. Git. Ship. Done - Core Tiene 10.8k estrellas en GitHub y su última actualización registrada es del 2026-10-23.

¿Cómo se instala gsd-core?

Puedes instalar gsd-core clonando el repositorio (https://github.com/open-gsd/gsd-core) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar open-gsd/gsd-core?

Nuestro agente de seguridad ha analizado open-gsd/gsd-core y le ha asignado un Trust Score de 100/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene open-gsd/gsd-core?

open-gsd/gsd-core es mantenido por open-gsd. La última actividad registrada en GitHub es del 2026-10-23, con 275 issues abiertos.

¿Hay alternativas a gsd-core?

Sí. En ClaudeWave puedes explorar subagents similares en /categories/agents, ordenados por popularidad o actividad reciente.

¿Mantienes este repo? Muestra su Trust Score en tu README

La insignia muestra el Trust Score y el veredicto actuales de este repositorio y enlaza a esta página. Sigue los datos del catálogo: nadie puede comprar ni editar la puntuación que enseña.

ClaudeWave Trust Score for open-gsd/gsd-core
Markdown (README)
[![ClaudeWave Trust Score for open-gsd/gsd-core](https://claudewave.com/api/badge/open-gsd-gsd-core)](https://claudewave.com/en/repo/open-gsd-gsd-core)
HTML
<a href="https://claudewave.com/en/repo/open-gsd-gsd-core"><img src="https://claudewave.com/api/badge/open-gsd-gsd-core" alt="ClaudeWave Trust Score for open-gsd/gsd-core" width="320" height="64"></a>

Qué significa la insignia y cómo se calcula la puntuación

Web del proyecto
https://opengsd.net