GSD Core

---

Why this fork exists

sh1ny/gsd-omp is a downstream fork of open-gsd/gsd-core. Upstream declined in-repository OMP runtime support in open-gsd/gsd-core#874 and pointed OMP users at open-gsd/gsd-pi. This fork keeps the lighter GSD Core runtime-integration path available for users who want GSD Core artifacts installed directly into OMP.

We maintain this fork to track upstream GSD Core fixes while preserving native OMP install behavior. The maintenance policy is deliberately small: merge upstream next, keep OMP-specific installer/runtime support working, and avoid changing non-OMP behavior unless upstream compatibility requires it.

---

What is GSD Core

GSD Core is a context-engineering and spec-driven development framework that drives AI coding agents (Claude Code, Codex, Gemini 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 this fork differs from upstream

Area	Upstream open-gsd/gsd-core	This fork sh1ny/gsd-omp
OMP runtime	No in-repo native OMP runtime support.	Adds --omp install support.
Install targets	Installs supported upstream runtime artifacts.	Also installs .omp/{commands,skills,agents,rules,extensions}/ locally, or the Oh My Pi agent home ($PI_CODING_AGENT_DIR, profiled $PI_CONFIG_DIR, or ~/.omp/agent) globally.
OMP extension	Not shipped.	Ships .omp/extensions/gsd-core/ for guardrails, update checks, context warnings, and status behavior.
OMP rules	Not shipped.	Installs explicit safe static rules from gsd-core/omp/rules/manifest.json.
Agent model overrides	No OMP agent frontmatter handling.	Embeds resolved OMP model overrides into generated .omp/agents/gsd-*.md frontmatter.
Upstream tracking	Owns the main runtime set and release process.	Tracks upstream while keeping OMP as a fork-local integration.

For operational details, see OMP Support.

---

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

For OMP, install from this fork checkout:

git clone [email protected]:sh1ny/gsd-omp.git
cd gsd-omp
node bin/install.js --local --omp

For a global OMP install, set PI_CODING_AGENT_DIR or let the installer fall back to ~/.omp/agent. Named OMP profiles use OMP_PROFILE or PI_PROFILE under $PI_CONFIG_DIR/profiles/<profile>/agent:

PI_CODING_AGENT_DIR=~/.omp/agent node bin/install.js --global --omp
OMP_PROFILE=work node bin/install.js --global --omp

The upstream npm package remains @opengsd/gsd-core; use it for upstream GSD Core installs, not for this fork's OMP-only additions.