@xirang-ai/dsh-teamflow

Q: Does it collide with @nanmicoder/dsh-agent-teams?

@xirang-ai/dsh-teamflow is the one to keep here: If the pipeline is the product (issues, defects, handoffs), take the one that models it; otherwise stay with the generic teams.

Q: Which dsh versions load it, and what happens outside that window?

On >=0.2.2-rc.1 <0.3.0 the CLI loads @xirang-ai/dsh-teamflow; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version @xirang-ai/dsh-teamflow is the per-package override if you accept the risk.

A workbench for the requirement → development → defect pipeline across a team.

Version 0.1.3 of @xirang-ai/dsh-teamflow, last published 2026-11-13; the install command and the range come from its own manifest.

Install

dsh plugin add @xirang-ai/dsh-teamflow writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.

dsh plugin --profile web add @xirang-ai/dsh-teamflow

Compatibility

engines.dsh in @xirang-ai/dsh-teamflow declares >=0.2.2-rc.1 <0.3.0; run dsh --version and compare it, because outside that range the CLI skips the plugin at boot and prints the requirement instead of booting.

If two plugins fight

Seven peers and its own requirement-to-defect pipeline with roles. @nanmicoder/dsh-agent-teams and dsh-agent-compare orchestrate agents from the same chat surface, and the second orchestrator to patch that row replaces the first one's controls.

Who made it

Author: xirang-ai. Repository: https://github.com/xirang-ai/dsh-teamflow. Package page: https://www.npmjs.com/package/@xirang-ai/dsh-teamflow.

After install

It declares @deepseek-ai/cordis as a peer and renders agent controls in the composer toolbar; after dsh plugin add @xirang-ai/dsh-teamflow, dsh --profile web --dump-config lists the row that mounts it.

Files it touches

@xirang-ai/dsh-teamflow routes whatever it persists through @deepseek-ai/dsh-home-paths under $DSH_HOME, and its own dependency line sits in $DSH_HOME/profiles/<name>/package.json.

Removing it

Removing @xirang-ai/dsh-teamflow is the mirror command, dsh plugin --profile web remove @xirang-ai/dsh-teamflow; the surface goes with it, and whatever it stored under $DSH_HOME stays until you delete it.

Common questions

Does it collide with @nanmicoder/dsh-agent-teams?

@xirang-ai/dsh-teamflow is the one to keep here: If the pipeline is the product (issues, defects, handoffs), take the one that models it; otherwise stay with the generic teams.

Which dsh versions load it, and what happens outside that window?

On >=0.2.2-rc.1 <0.3.0 the CLI loads @xirang-ai/dsh-teamflow; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version @xirang-ai/dsh-teamflow is the per-package override if you accept the risk.