dsh-gsd-bridge

GSD Core wraps a spec-driven development workflow—Discuss, Plan, Execute, Verify, Ship—into 71 structured slash commands, but its native home is Claude Code. If your primary coding environment is DeepSeek Harness, those commands are simply out of reach. dsh-gsd-bridge closes that gap in one move: it pulls @opengsd/gsd-core in as a plain npm dependency and adapts every command in memory at dispatch time, so you can type /gsd-new-project, /gsd-ship, and friends right inside the Harness Web UI with an experience nearly identical to Claude Code.

All adaptation is runtime-only; nothing on disk is ever rewritten. Under the hood the bridge strips Claude-specific frontmatter, recursively inlines @~/.claude/gsd-core/... references with a character budget and cycle guard, maps the tool vocabulary onto dsh's native registry, and re-points the gsd_run shim to the installed package root. At session start it also injects the project's .planning/STATE.md head as a non-waking orientation notice, mirroring GSD Core's SessionStart hook. Because the upstream package is never forked or patched, an upgrade is just a version bump—no vendoring, no maintenance burden.

It is built for engineers who already run GSD workflows in Claude Code and want DeepSeek Harness in the same pipeline. Project state lives in the shared .planning/ directory, so a Claude Code session and a Harness session can drive the same project interchangeably without conflicts. If you prefer thinking through a plan before touching code, or you need state consistency across multiple AI assistants, this bridge is plug-and-play.