When conducting complex engineering development in DeepSeek Harness (DSH), the biggest challenge is often not the implementation of a single module, but controlling the granularity of requirement decomposition, managing dependencies between modules, and handling the cascading effects of changes. Manually maintaining the module tree and dependency relationships is error-prone and makes it difficult to track the impact scope of changes.

phantomsuying/dsh-module-driven-develop is a plugin that provides Module-Driven Development (MDD) capabilities for DSH. It implements a complete skill-driven software development protocol to address the issues mentioned above.

What Is This

This is a DSH plugin focused on workflows, maintained by phantomSuying. It formalizes the software development process into decomposition, design, implementation, integration, debugging, and change management. The core value of this plugin lies in using automated workflows to decompose any requirement into a module tree and leveraging multi-agent collaboration to complete the entire process from design to delivery.

Core Features

This plugin provides the following key capabilities:

  1. Skill-Driven Development Protocol: It covers the full lifecycle from requirement decomposition and architectural design to code generation, integration testing, and change management.
  2. Recursive Requirement Decomposition: It breaks down large requirements step by step into modules and submodules until each leaf module is small enough to be designed and implemented independently by a single agent.
  3. Independent Agent Code Generation: Leaf modules are fully generated by independent child agents. Parent modules containing submodules act as schedulers for the next level of coordination and integration.
  4. Main Agent Orchestration and Integration: The main agent is responsible for orchestrating the workflow, scheduling child agents, and performing integration, building, and debugging after generation.
  5. Full Code Regeneration: When a design change occurs, the plugin triggers a version number increment, archives the old code, clears the directory, and forces all code to be regenerated from the new design documents. Patching is prohibited.
  6. Recursive Requirement Change Propagation: When requirements are adjusted, the plugin identifies affected modules, including indirect dependencies. Module agents recursively determine whether tasks need to be propagated downward, then redesign and regenerate the code.

Installation and Enablement

Install this plugin through DSH’s plugin manager. After installation, the plugin registers a skill named module-driven-dev to the corresponding profile.

dsh plugin --profile web add git+https://github.com/phantomSuying/dsh-module-driven-develop.git

After installation is complete, restart the DSH process. In a new session, the agent’s skill directory should include the module-driven-dev skill.

Typical Usage

This plugin drives the workflow using natural-language instructions:

  • Implement a Requirement:
    Enter 用模块驱动开发实现 <requirement> in the conversation. The agent will run through the P0–P5 phases: first decompose the module tree, then design each module, dispatch independent child agents to generate code, and finally perform integration, building, and debugging by the main agent.

  • Modify a Design:
    Enter 把 <module> 的设计改成 .... The agent will identify this as a design change, trigger a version number increment, archive the old code, and fully regenerate the code for the module and its related dependencies from the new design documents.

  • Adjust a Requirement:
    Enter 需求调整：<new requirement>. The agent will dispatch a change-analysis child agent to identify affected modules, module agents will recursively determine the scope of task sinking, and then perform redesign, regeneration, and reintegration.

Project Structure and Data

This plugin requires all workflow artifacts to be managed centrally. All files, including the module tree, design documents, and logs, are stored uniformly in the .mdd/ folder under the project root directory.

Design documents are the single source of truth. All code generation is based on the documents under .mdd/designs/, ensuring consistency between implementation and design.

Applicable Scenarios and Notes

This plugin is suitable for complex projects that require a highly structured development process and have demanding requirements for module decoupling.

Notes:
1. The plugin runs with the permissions of the current DSH process. Please ensure awareness of review for the plugin source code and license.
2. The auth-service sample project provided in the plugin repository demonstrates a complete MDD workflow and can be used as a reference.

Summary

phantomsuying/dsh-module-driven-develop introduces a module-driven development protocol and provides DeepSeek Harness with a rigorous set of engineering practices. Through recursive decomposition, independent generation, and full regeneration mechanisms, it reduces the development barrier and integration risk of complex systems.