Foreword

When working on agent workflows within DeepSeek Harness (dsh), a common practice is to delegate tasks to multiple roles: one for architecture, one for implementation, and others for testing, review, and documentation. dsh-crew is a plugin for dsh that transforms a dsh session into a Product Manager (PM). The PM schedules a group of role agents, enabling communication between roles via files on the disk.

The community directory referenced here is an independent site; please do not interpret the directory page as the official app store for DeepSeek or Fantom.

What is this

dsh-crew is a plugin for DeepSeek Harness (dsh), owned by stuarthu, and licensed under MIT.

Its function is to turn a dsh session into a PM that runs a set of role agents. The listed roles include:

  • architect
  • engineer
  • test engineer
  • code engineer
  • QA
  • code reviewer
  • security reviewer
  • doc reviewer
  • researcher

These roles communicate via files on the disk. For the user, the PM is the sole entry point: you ask questions of the PM, or request that the PM execute a change.

Core Features

Ask lane

The Ask lane is used for asking questions. The PM answers questions without making any content changes.

Suitable scenarios include: confirming requirements, checking status, understanding the current task, or asking the PM to explain existing documentation within a repository.

Team lane

The Team lane is used for making changes. The PM runs the crew according to a fixed process:

  • One change corresponds to one task;
  • One round of QA;
  • One round of each type of review;
  • A final commit.

During this process, decisions are written into documentation retained within the repository.

It is important to note that pushing and publishing still require user confirmation, and this must be done for each action.

Optional Configuration

dsh-crew’s configuration is optional. It can be configured in two locations:

  • In the profile’s cordis.patch.yml, configure two lines: dsh-crew-core and dsh-crew-git-guard.
  • In ~/.dsh/.agent-presets/crew/agent.cordis.yml, configure the tools and models for each role via the dsh-crew-roles line.

If not configured specifically, you can install and use it according to default behavior.

Installation and Enablement

dsh-crew requires Node >=18.

The installation command is as follows:

dsh plugin --profile tui add dsh-crew

If using the web profile:

dsh plugin --profile web add dsh-crew

After installation, restart dsh.

Since dsh-crew runs within the current dsh process and inherits the permissions of the current dsh session, it is recommended to review the source code and license before installation. The license is MIT.

Reference:

https://github.com/stuarthu/dsh-crew

Typical Usage

The following is a reproducible usage path.

  1. Install the plugin:
dsh plugin --profile tui add dsh-crew

  1. Restart dsh.

  2. Start a session on the Crew preset. At this point, the session becomes the PM.

  3. Ask the PM questions or request that the PM execute a change.

If you choose to ask questions, the PM will answer them, and the repository content will not change.

If you request a change, the PM will run the crew. One change corresponds to one task, passing through one round of QA and one round of each type of review, followed by a final commit. Subsequent pushes and publishes still require user confirmation each time.

Applicable Scenarios and Notes

dsh-crew is suitable for those who wish to break down work within a dsh session into a role agent workflow, particularly for scenarios where decisions need to be retained in repository documentation.

Please note the following when using it:

  • It is not an automatic push or automatic publishing tool; pushing and publishing require user confirmation every time.
  • It runs within the current dsh process, so it is subject to the permissions of the current dsh session.
  • Configuration items are optional; you can use the default workflow without configuring them.
  • Before installation, it is recommended to review the source code, license, and repository directory structure to ensure you accept its behavior boundaries.

References

  • GitHub: https://github.com/stuarthu/dsh-crew
  • Directory Page: https://www.skillhub.cn/plugins/stuarthu/dsh-crew