btspoony/mstar-harness
morning-star
An omni-plugin for harness engineering workflows with multi-agents, programmatic gates and skills.
Install
npx @deepseek-ai/dsh plugin --profile web add @mstar-harness/dsh`Restart `dsh web` after install. Bundle APIs can change during the developer preview.
README badge
[](https://dshhub.dev/plugins/mstar-harness)Paste this into your README. The star count updates with every catalog sync.
From the README
Excerpt from btspoony/mstar-harness, cleaned of badges and images.
Morning Star
Harness Workflow Engine · Agent Plugin
English / 中文
<a href="https://github.com/btspoony/mstar-harness">GitHub</a> · <a href="https://github.com/btspoony/mstar-harness/issues">Issues</a>
Morning Star brings a delivery process to the AI coding tools you already use — dsh, omp, OpenCode, Cursor, Kimi Code, ZCode, and Codex. You describe what you want; a project-manager agent clarifies the request, keeps a plan, and carries the work from requirements through implementation, review, and acceptance to a pull request. Requirements, architecture, implementation, review, acceptance, and audits each go to a role that owns that part.
Why use it
- From request to pull request — describe the work once; the PM keeps the plan, brings in the right specialists, and drives everything to a pull request. If work stops partway, the plan records where it left off so the work can resume later.
- Specialists instead of one long prompt — a PM orchestrates; separate roles own requirements, architecture, implementation, QC, acceptance, audits, and ops, each with a narrow brief.
- A trail you can audit — plans, findings, review reports, and decisions are recorded under the harness directory in your repo, not just in the chat.
- Boundaries are explicit — the workflow opens pull requests and records a merge policy when an iteration starts. Under
reviewed-autoonly a settled, postedship itreview report at the current PR head authorizes the merge; underowner-gatedit stops at merge-ready and waits for your written approval. A policy that was never recorded returns the run to Phase 1 rather than defaulting to either. Audits read and report, and anything that touches a real environment needs your explicit authorization.
Install
Every host installs two ways: this CLI's init flow, or the host's own plugin manager — the native command installs the plugin only. Options, path layout, and host notes: INSTALL.md.
- dsh (DeepSeek Harness) — needs the
dshCLI onPATH- CLI:
npx @mstar-harness/cli init --target dsh - Native:
dsh plugin --profile web add @mstar-harness/dsh
- CLI:
- omp — needs the
ompCLI installed- CLI:
npx @mstar-harness/cli init --target omp - Native:
omp plugin install @mstar-harness/omp
- CLI:
- OpenCode
- CLI:
npx @mstar-harness/cli init --target opencode - Native:
@mstar-harness/opencodefor OpenCode 1.x,@mstar-harness/opencode-v2for OpenCode 2.x — add it to the plugin list inopencode.json, then restart OpenCode
- CLI:
- Cursor — needs
git- CLI:
npx @mstar-harness/cli init --target cursor - Native:
git clone https://github.com/btspoony/mstar-harness.git ~/.cursor/plugins/local/morning-star-harness, then Developer: Reload Window
- CLI:
- Kimi Code — no CLI target
- Native:
/plugins install https://github.com/btspoony/mstar-harness, then/plugins reload
- Native:
- ZCode
- CLI:
npx @mstar-harness/cli init --target zcode - Native: add
https://github.com/btspoony/mstar-harnessas a ZCode plugin marketplace, then install morning-star-harness
- CLI:
- Codex — needs the
codexCLI- CLI:
npx @mstar-harness/cli init --target codex - Native:
codex plugin marketplace add btspoony/mstar-harness --ref main, thencodex plugin add morning-star-harness@mstar-repo
- CLI:
Use
…
