cainiao1992/dsh-gsd-bridge

dsh-gsd-bridge mounts the spec-driven development system GSD Core onto DeepSeek Harness as native /gsd-* slash commands: 71 workflow commands (new-project, onboard, plan-phase, execute-phase, verify-work, ship and more) are adapted in memory at dispatch time with frontmatter stripped, includes inlined and the gsd_run shim re-pointed, so the upstream npm package is never modified; a session started in a directory with a .planning/ project is oriented with the current STATE.md head, and GSD state stays in the project so a Claude Code session and a DSH session can drive the same project interchangeably.

dsh-gsd-bridge mounts GSD Core - the spec-driven development system whose loop is Discuss, Plan, Execute, Verify, Ship - onto DeepSeek Harness as native /gsd-* slash commands. The full GSD Core command surface becomes 71 workflow commands including /gsd-new-project, /gsd-onboard, /gsd-plan-phase, /gsd-execute-phase, /gsd-verify-work, /gsd-ship, /gsd-next and /gsd-help. When a session starts in a directory that contains a GSD project, the model is oriented with the current STATE.md head, mirroring GSD Core's SessionStart hook. Because command bodies are adapted in memory at dispatch time and project state lives in .planning/, the upstream package is never forked and both Claude Code and DeepSeek Harness can drive the same project.

Workflow & Automation ★ 0 updated 2026-10-15
View on GitHub ↗

Install

dsh plugin --profile web add github:cainiao1992/dsh-gsd-bridge --config.auto-install-peers=false

Copied verbatim from the README's Install block; the README explains that --config.auto-install-peers=false avoids the incomplete rc-era peer graph of the @deepseek-ai/dsh-* packages (peers are already provided by the host bundles in a profile) and documents an equivalent manual corepack pnpm add form.

Compatibility

Mounting requires editing the profile's cordis.patch.yml to insert the row - id: gsd-bridge with name: dsh-gsd-bridge, after which the loader resolves the bare name against the profile's node_modules; the local absolute path is replaced by the bare package name. Nothing is rewritten on disk - upstream-faithful command bodies are adapted in memory (frontmatter stripped, ~/.claude/gsd-core includes inlined, tool vocabulary renamed, the gsd_run shim re-pointed) - so the gsd-core package is never modified and an upstream upgrade is just a version bump. GSD state lives in the project under .planning/, letting a Claude Code session and a DeepSeek Harness session drive the same project interchangeably.

Details

Alternatives

940842546/dsh-permissions · adithya-hmt/fullstack-expert · alib8b8/dsh-plugin-aflare

More plugins in Workflow & Automation

Browse more in Workflow & Automation

Guides for Workflow & Automation plugins