Introduction¶

DeepSeek Harness (DSH) extends its capabilities through a plugin mechanism. Core execution usually relies on Harness’s existing tooling, approval, and logging systems. When teams define their development, testing, release, and operations processes, these definitions often exist only as documents or scripts, making them difficult to validate, reuse, and audit.

The dsh-runbook-ops plugin addresses the “process definition” problem. It encodes team SOPs (Standard Operating Procedures) as structured YAML and exposes them to the model as Harness tools. It does not replace Harness’s execution system; instead, it provides validation-capable, reusable, and auditable execution guidance.

Features¶

This plugin provides the following capabilities:

1. List runbooks: Lists the runbooks in the current project.
2. Read and validate: Reads and validates a specified runbook.
3. Generate guidance text: Generates model guidance text for step-by-step execution.
4. Default directory: By default, it only reads .dsh/runbooks inside the current session workspace.
5. Execution control: It does not directly execute shell commands; command execution remains handled by Harness’s existing tooling, approval, and logging systems.

Installation and Enablement¶

After release, it can be installed via DeepSeek Harness’s plugin mechanism:

dsh plugin --profile web add dsh-runbook-ops

Local Development¶

For local development, build the plugin first, then load the patch in the DeepSeek Harness repository:

cd C:/Users/admin/Desktop/code/dsh-runbook-ops
npm run build
cd C:/Users/admin/Desktop/code/deepseek-harness
pnpm dsh web --patch C:/Users/admin/Desktop/code/dsh-runbook-ops/cordis.dev.yml

Headless verification:

pnpm dsh --profile headless --patch C:/Users/admin/Desktop/code/dsh-runbook-ops/cordis.dev.yml "按 release-preflight runbook 检查当前项目"

Note: In the --patch parameter, the plugin entry point must be written as file:///C:/.../lib/index.js to prevent the Node ESM loader from treating C: as an unsupported protocol. Loading the built JS artifacts during local development avoids inconsistent support for the .ts loader across different DSH startup modes.

Configuration¶

The plugin supports configuration via a config file to adjust behavior. The default configuration is:

- insert:
    - id: runbook-ops
      name: dsh-runbook-ops
      config:
        root: .dsh/runbooks
        maxBytes: 65536
        allowAbsoluteRoot: false

Dependencies¶

The plugin depends on the following libraries:

• @deepseek-ai/schemastery
• js-yaml
• @deepseek-ai/cordis (peer dependency)
• @deepseek-ai/dsh-tools (peer dependency)

Summary¶

dsh-runbook-ops converts structured YAML runbooks into tools recognizable by DSH, making it suitable for teams that want to standardize their development and operations processes. It executes through Harness’s existing systems, ensuring security and auditability.