The DeepSeek Harness ecosystem is built around the core idea that “everything is a plugin.” In spec-driven development, GSD Core provides a complete closed loop: Discuss → Plan → Execute → Verify → Ship. The dsh-gsd-bridge plugin uses in-memory adaptation to map GSD Core commands to DSH-native /gsd-* slash commands, enabling the model to directly invoke GSD workflows without maintaining a separate GSD codebase.

This plugin is maintained by cainiao1992 and is open source under the MIT license.

Core Features

  1. 71 Workflow Commands: GSD Core’s full command surface is mapped to the /gsd-* command family, including /gsd-new-project, /gsd-onboard, /gsd-plan-phase, and more.
  2. Session Orientation: When a session starts in a directory containing a GSD project (.planning/ directory), the model automatically reads the current state header from STATE.md to establish contextual awareness.
  3. Upstream Faithfulness, Zero Forking: Command bodies are adapted in memory (for example, removing frontmatter, inlining references, and rewriting tool vocabulary) without modifying files on disk, making it easy to follow upstream updates.
  4. Interchangeable Project State: GSD state is stored in the .planning/ directory within the project, allowing the same state to be shared across different sessions.

Installation and Enablement

The installation command is as follows:

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

dsh plugin directly passes arguments to pnpm in the web configuration directory. Because DeepSeek Harness npm packages are currently in the rc stage, it is necessary to add --config.auto-install-peers=false during installation to avoid peer dependency issues in the @deepseek-ai/dsh-* dependency graph.

Typical Usage

Enter the following commands in the DeepSeek Harness Web UI:

/gsd-help            # 查看工作流目录
/gsd-new-project     # 新项目：提问 → 研究 → 需求 → 路线图
/gsd-onboard         # 现有代码库：映射 → 吞吐 → 初始化规划
/gsd-plan-phase 1    # 制定第一阶段计划
/gsd-execute-phase 1 # 执行第一阶段计划
/gsd-next            # 状态感知路由器

Notes

  • gsd-core is updated daily by an automated workflow, and breaking formatting changes may be published without review.
  • The plugin does not port PreToolUse hooks (which are already covered by the DSH native stack), and GSD named agents (such as gsd-executor) are mapped to subagent delegation rather than native agent types.
  • The dependency @opengsd/gsd-core also follows the MIT license.

With the above configuration, GSD Core’s spec-driven capabilities are seamlessly integrated into DeepSeek Harness workflows.