Introduction

The core idea of DeepSeek Harness (DSH) is “Everything is a plugin.” When building complex task workflows, manually managing each stage from requirement understanding, plan writing, code review to test acceptance can easily miss details or get trapped in repeated revisions. The dsh-dev-mode plugin automates this entire pipeline through a preconfigured Agent workflow.

What Is It?

dsh-dev-mode is a “Developer Mode” preset added for DSH. It is designed for users who are not familiar with programming details: users only need to describe requirements in plain language, and the agent automatically completes the workflow of “write plan -> subagent reviews plan -> minimal-mode background session writes code and compiles -> subagent QA -> fix bugs -> retest -> delivery”.

Core Features

1. Step 0 Pre-Flight Check
Before starting, the agent validates local channel, model availability, permission level, and whether workflow clauses are active. If validation fails, it automatically degrades gracefully and does not block the user.

2. Workflow Tiering
Choose “Fast Lane” or “Full Lane” based on the scale of changes and the number of acceptance criteria. Both lanes retain a complete test report, reproduction steps, and delivery acceptance table.

3. Independent Review and Independent Testing
The plan is exclusively reviewed by a review subagent; after implementation, a testing subagent actually runs the program to verify it, instead of inferring from code only.

4. Delivery Acceptance Table
Each acceptance criterion must include its verification method, result, and evidence file path; uncovered items must state reasons.

5. Failure Exit Paths
Every failure type has a clear next step (e.g., degraded mode when a channel is unavailable, continue waiting when timeout occurs, request re-approval when blocked by permissions), so it does not get stuck in a dead-end wait.

6. Self-Verification of Effectiveness
selfcheck verifies each actually effective workflow clause (13 clause titles + 12 body anchors), avoiding the issue of “the file was changed but not effective”.

7. Beginner-Friendly Expression Conventions
It includes a built-in terminology replacement table, examples before questions, reporting only three items per step, the delivery trio, a self-check list, and three sentences for errors.

Installation

dsh plugin --profile <your profile name> add github:lingyingaojue/dsh-dev-mode

Note: A profile exclusively managed by the desktop application (named desktop) cannot be installed or uninstalled from the command line and will be rejected directly. In this case, please use the UI installation.

After installation, you need to create a new session to see “Developer Mode”.

Usage

In a Developer Mode session, just describe the requirement directly. For example:

Help me create a small bookkeeping tool and place it in this directory. Requirements: record an entry, view details, view balance, data must persist after closing and reopening, and double-clicking should start bookkeeping. I know nothing about programming at all; you decide how to implement it.

If the description is unclear, the mode will first provide three concrete examples to choose from and ask at most one round of questions throughout.

The agent generates a .dsh-dev/ folder in the project directory, including plan.md, review-*.md, qa/qa-*.md, logs/, backup-*, and status.json.

The background session runs independently in the sidebar (minimal mode, persistent shell only), and can be checked at any time.

Delivery includes a double-clickable runnable file, Chinese documentation, launch script, desktop shortcut, and self-check list.

Notes and Limitations

Permissions and Sandbox
Permissions are determined by the deployer; the default may be “approval required” or may already be fully open. Under restricted permissions, a background session may be unable to start commands, and the script will automatically reopen with fully open permissions. Packing into an executable, launching a real browser, or writing outside the working directory may be blocked by the sandbox.

Scripts and Cost
The self-check script is not guaranteed to exist: during the testing stage, the locally available skills are listed first; if no ready-made script exists, the testing subagent writes the check itself and explains the coverage. A complete workflow includes multiple subagents and background sessions; the larger the program, the longer it takes; the mode asks the user when stuck, instead of continuing to consume resources idle.

Mode Configuration
The mode id is dev. If a preset with the same name already exists in your profile, it will report Duplicate agent preset.
UI copy and questions are primarily in Chinese; if asked in English, it answers in English.

Summary

dsh-dev-mode lowers the barrier from requirements to delivery through automated subagent collaboration. It is suitable for users who need rapid iteration or want to reduce manual testing stages.

  • GitHub: https://github.com/lingyingaojue/dsh-dev-mode
  • Catalog: https://www.skillhub.cn/plugins/lingyingaojue/dsh-dev-mode