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:

• Your first project
• Onboarding an existing codebase

How-to guides — task-focused recipes:

• Install on your runtime
• Plan a phase
• Verify and ship
• … see all how-to guides

Reference — authoritative facts:

• Commands
• Configuration
• CLI tools

Explanation — concepts and design decisions:

• Context engineering
• The phase loop
• Architecture

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

Star History

License

MIT License. See LICENSE for details.

Claude Code is powerful. GSD Core makes it reliable.