GSD Core workflow
A spec-driven development framework for coding agents: a discuss, plan, execute, verify and ship loop run in fresh contexts
- 10,976 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Installs hooks that run on agent session events
- Subagents write code, commit and open PRs
Install
- Works in
Manual install
npx @opengsd/gsd-core@latestThe installer asks for the runtime and install scope.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Installs hooks that run on agent session events
- Subagents write code, commit and open PRs
This is third-party code. Review the repository files before installing.
What it does
GSD Core installs a set of /gsd-* commands, skills, subagents and hooks that drive a project phase by phase. Each phase has five steps: decisions are captured, a plan is drafted and checked, tasks run in parallel waves in fresh-context subagents, the result is verified with fix plans, then a PR is created. Heavy work goes to subagents so the main session stays lean, and state between sessions lives in files like STATE.md and CONTEXT.md. There are flows for greenfield projects and for onboarding an existing codebase.
Who it is for. For developers running large tasks with an agent who want a disciplined process instead of long chats.
Good fit when
- A multi-phase project where the agent degrades by the end of a session
- You need to onboard an agent to an existing repo with a code map
- You want verification before a PR is created
- Work spans many sessions and state must persist
Not a fit when
- A small fix of a few lines
- You do not want an installer adding hooks and files to your agent config
Example request
/gsd-onboard, then plan the first phase: OAuth sign-inLimitations
Requires Node.js 18+ and npm; the authors advise against copying files by hand because the installer converts them per runtime. Parallel subagents use noticeably more tokens than a single session. The installer registers Claude Code hooks, including an update check at session start.
How to disable. Remove the gsd commands, skills, agents and hooks from ~/.claude or the project's .claude folder, then remove the hook entries from settings.json.
FAQ
Which agents are supported?
Per the README: Claude Code, OpenCode, Antigravity CLI, Kimi CLI, Kilo, Codex, Copilot, Cursor, Windsurf and more. The installer asks which one to target.
Can I install both globally and per project?
Yes, but on name clashes the global skill wins the command. The installer and /gsd-health warn about it.
Discussion
No questions or reviews yet.
Related
WorkflowsA team of AI agents from one request: it plans the task, writes code in parallel branches, tests, reviews and opens a pull request
A memory and coordination layer for coding agents: specs and issues live in git while agents work in parallel
A LangWatch command-line tool that creates the scaffold of a new AI agent project and hands it to a coding assistant
Skills for cross-provider work between Claude Code and Codex: one agent drafts the plan, the other reviews it, then a build and an independent code inspection f
A plugin marketplace for agents: reflexion, code and PR review, git, TDD, DDD, specs and subagent-driven development
A desktop app where Claude Code, Codex, Gemini and other agents work as a team of specialists in a shared project
Comparison with similar tools
Entries that share the main search query, and how they differ.
README in short
The README explains that GSD Core fights quality loss as the context fills up by moving research, planning and execution into subagents. It describes the five-step phase loop and a single npx install with runtime and scope selection. Docs are split into tutorials, how-to recipes, command and config reference, and architecture explanations. MIT licensed.