dsh-expert-team: A 12-Role Expert Team Orchestration Plugin for DeepSeek Harness

What Does It Do?

Expert Team (dsh-expert-team) is a DSH plugin for DeepSeek Harness that turns a one-line request into delivery by a virtual 12-role engineering team. It addresses the three classic failure modes of a single agent on long tasks: context drift, self-approval, and non-converging rework, using role separation, stage gates, quality gates, and artifact trails. Maintained by yangdcm under the MIT license, it has zero runtime dependencies and no build step, with the latest update in September 2026.

Core Features

• 12-role expert team: product, architecture, research, UI, frontend/backend, data, security, review, QA, DevOps, and docs, each with its own persona, tool boundaries, and delegation depth; only implementers touch code.
• 9-stage gated pipeline: clarification, research, design, spec review, plan confirmation, implementation, review, testing, and delivery, with every handoff carried by structured return values plus artifact files.
• Hard gate and confirmation gate: spec review is blocked until the boundaries and prohibitions section of SPEC.md is filled in, while the plan confirmation gate is on by default and can be turned off in settings.
• Dependency-DAG parallel implementation: the implementation stage fans out in parallel, with multiple implementers working at once and each editing only its own files.
• Quality gates enforced by plugin code: unfinished tasks cannot be marked completed, quality issues must be adjudicated by QA or the reviewer, and overwriting another role's artifact is rejected on the spot.
• Full artifact trail: SPEC.md, PLAN.md, TASKS.json, REVIEW.md, TEST.md, SUMMARY.md and more, with local data stored in the expert-team directory under the DSH home folder.

How to Use This Plugin?

After enabling it in DSH, restart dsh web once so the plugin can lay out the Expert Team mode preset automatically. Open a new session, switch to that mode, and enter a one-line request such as /team 做一个带登录的支付模块 to start the team.

While it runs, check the persistent status bar above the input box to see who is working, open the team overlay for stages, members, and artifacts, or use /team canvas for the full-screen canvas; output files land under the /team/ directory. It suits internal tools and product iterations at small and mid-sized companies, freelance and outsourcing delivery, and independent developers building complete projects, while product-level and scope-level decisions stay with you.

How to Troubleshoot This Plugin?

If the spec review stage stalls, the boundaries and prohibitions section of SPEC.md is usually missing; fill it in to let the pipeline continue.

If an overwrite is rejected during implementation, the current role is not the owner of that artifact; route the work to the responsible role according to the role split.

When the overlay or /team status reports state-machine consistency warnings, they usually mean a task was marked completed while unfinished, a quality issue was not adjudicated by QA or the reviewer, or there is a coverage gap or over-limit rework; fix the artifact and state as described in the official documentation, then rerun that stage.