@mstar-harness/opencode 0.6.11 → 0.6.13
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/harness-agents/architect.md +0 -1
- package/harness-agents/frontend-dev.md +0 -1
- package/harness-agents/fullstack-dev-2.md +0 -1
- package/harness-agents/fullstack-dev.md +0 -1
- package/harness-agents/ops-engineer.md +0 -1
- package/harness-agents/product-manager.md +0 -1
- package/harness-agents/project-manager.md +0 -1
- package/harness-agents/prompt-engineer.md +0 -1
- package/harness-agents/qa-engineer.md +0 -1
- package/harness-agents/qc-specialist-2.md +0 -1
- package/harness-agents/qc-specialist-3.md +0 -1
- package/harness-agents/qc-specialist.md +0 -1
- package/harness-agents/writing-specialist.md +0 -1
- package/harness-skills/mstar-dispatch-gates/SKILL.md +2 -0
- package/harness-skills/mstar-dispatch-gates/references/leaf-executor-checklist.md +2 -0
- package/harness-skills/mstar-roles/references/project-manager/dispatch-and-assignment.md +26 -1
- package/package.json +1 -1
|
@@ -3,7 +3,6 @@ name: frontend-dev
|
|
|
3
3
|
description: |-
|
|
4
4
|
前端开发工程师 - 页面/组件/交互/a11y/前端性能。全栈功能里默认前端主责（与 `@fullstack-dev` 分轨）；纯 UI 任务首选本角色。
|
|
5
5
|
Frontend Developer - pages/components/interactions/accessibility/frontend performance. This is the default frontend owner in fullstack work (split with `@fullstack-dev`) and the preferred role for pure UI tasks.
|
|
6
|
-
model: inherit
|
|
7
6
|
mode: subagent
|
|
8
7
|
tools:
|
|
9
8
|
write: true
|
|
@@ -3,7 +3,6 @@ name: fullstack-dev-2
|
|
|
3
3
|
description: |-
|
|
4
4
|
全栈开发工程师 - 与 `@fullstack-dev` 并行的第二实现轨（独立模块/API/页面岛）。PM 在 tasks 可并行或加速时指派；须写明模块边界与分支，勿当作闲置备用。
|
|
5
5
|
Fullstack Developer (Track 2) - the second implementation track parallel to `@fullstack-dev` (independent modules/APIs/page islands). PM should assign this role when tasks can run in parallel or when acceleration is needed, with explicit module boundaries and branch ownership.
|
|
6
|
-
model: inherit
|
|
7
6
|
mode: subagent
|
|
8
7
|
tools:
|
|
9
8
|
write: true
|
|
@@ -3,7 +3,6 @@ name: fullstack-dev
|
|
|
3
3
|
description: |-
|
|
4
4
|
全栈开发工程师 - 后端主导的全栈实现（API/业务/数据层）。UI 重或新页面多时由 PM 拆给 `@frontend-dev`；第二并行实现轨用 `@fullstack-dev-2`。Hotfix/单流小改可一人完成。
|
|
5
5
|
Fullstack Developer - backend-led fullstack implementation (API/business/data). PM should split UI-heavy or new-page work to `@frontend-dev`, and use `@fullstack-dev-2` for the second parallel track. One developer can handle hotfixes or small single-stream updates.
|
|
6
|
-
model: inherit
|
|
7
6
|
mode: subagent
|
|
8
7
|
tools:
|
|
9
8
|
write: true
|
|
@@ -35,6 +35,8 @@ description: Morning Star 派发与委派门禁 —— 仅 PM 可增派 subagent
|
|
|
35
35
|
3. 下一动作是不是「Task / subagent_type=…」？是 → 停手，改为 Read / Write / Shell / Edit，或 **`Blocked`**。
|
|
36
36
|
4. 命中任一 NEVER → 写 `## Blocked — recursive dispatch refused (<which NEVER>)` 回报 PM，**不**继续 invoke。
|
|
37
37
|
|
|
38
|
+
**Assignment 顶部反模式块**：每个 PM Assignment 开头均有 **`**You are a leaf executor. You MUST NOT:**`** 块，PM 按此 Assignment 的角色+上下文定制反模式清单。leaf executor 收到 Assignment 后须 **首先** 阅读该块；命中任一条 → **停止**（亲自完成或 `Blocked`）。详见 **`mstar-roles/references/project-manager/dispatch-and-assignment.md`**。
|
|
39
|
+
|
|
38
40
|
## 并发分派完整性门禁（PM 强制）
|
|
39
41
|
|
|
40
42
|
当 PM 声明「并发分派」时，须同时满足**文案并发**与**工具并发**：
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
# Leaf executor dispatch checklist
|
|
2
2
|
|
|
3
3
|
> Load **`mstar-harness-core`** first, then **`mstar-dispatch-gates`** SKILL.md.
|
|
4
|
+
>
|
|
5
|
+
> **First**: read the `**You are a leaf executor. You MUST NOT:**` block at the top of your Assignment. Those anti-patterns are customized for your specific role+context and are the authoritative dispatch boundaries for this assignment.
|
|
4
6
|
|
|
5
7
|
Before any Task/subagent call:
|
|
6
8
|
|
|
@@ -30,9 +30,33 @@ For assignees (non-PM):
|
|
|
30
30
|
|
|
31
31
|
## Assignment Template (Canonical)
|
|
32
32
|
|
|
33
|
+
Every Assignment **MUST** start with a **`You are a leaf executor. You MUST NOT:`** block listing the most likely dispatch violations for THIS assignment's situation. PM customizes per assignment; generic rules (no recursive dispatch, no interpreting routing text as invoke, available ≠ authorized) are the minimum floor. Add assignment-specific anti-patterns that the current role+context combination is prone to.
|
|
34
|
+
|
|
35
|
+
**How to fill the block (PM guidance)**:
|
|
36
|
+
|
|
37
|
+
- Always include the universal floor (recursive dispatch, routing-text-as-invoke, tool-availability-misread).
|
|
38
|
+
- Add anti-patterns specific to the assignment context. Examples per role type:
|
|
39
|
+
- **QC reviewers**: "start review before all QC reviewers are dispatched in parallel"; "treat other reviewers' names in routing text as invoke targets"
|
|
40
|
+
- **Multi-track implementers** (`fullstack-dev` + `frontend-dev`): "auto-dispatch to the other track mentioned in Dev routing"
|
|
41
|
+
- **`@fullstack-dev-2`**: "treat `@fullstack-dev` in routing narrative as a handoff or invoke target"
|
|
42
|
+
- **`@qa-engineer`**: "start validation before QC reports are consolidated"; "modify application code"
|
|
43
|
+
- **`@explore`-assigned**: "implement or modify code"
|
|
44
|
+
- **All non-PM**: "use `dispatching-parallel-agents`"; "spawn a subagent whose `subagent_type` matches your own `Execute as` role id"
|
|
45
|
+
- Anti-patterns must be action-oriented ("auto-dispatch to …", "treat … as invoke", "start … before …") — not abstract descriptions.
|
|
46
|
+
- If the assignment involves multiple QCs or parallel tracks, add a specific bullet about NOT serializing or pre-empting the parallel dispatch.
|
|
47
|
+
- If the assignment is part of a broader staged plan with follow-up tasks, add a bullet about NOT auto-extending scope into downstream tasks.
|
|
48
|
+
|
|
33
49
|
```markdown
|
|
34
50
|
## Assignment
|
|
35
51
|
|
|
52
|
+
**You are a leaf executor. You MUST NOT:**
|
|
53
|
+
- dispatch or invoke any subagent unless `Delegation: allowed (...)` appears below
|
|
54
|
+
- treat `@role-id` mentions, `Handoff`, `QA note`, routing tables, or multi-track prose as invoke commands
|
|
55
|
+
- invoke a subagent whose `subagent_type` matches your own `Execute as` role id (recursive dispatch)
|
|
56
|
+
- <situation-specific anti-pattern #1>
|
|
57
|
+
- <situation-specific anti-pattern #2>
|
|
58
|
+
- ...
|
|
59
|
+
|
|
36
60
|
**Execute as**: <role-id>
|
|
37
61
|
**Who runs this turn (executor lock)**: only `Execute as` role for this message
|
|
38
62
|
**Primary**: <route type>
|
|
@@ -70,10 +94,11 @@ For assignees (non-PM):
|
|
|
70
94
|
- [ ] commit proof
|
|
71
95
|
**Constraints**: ...
|
|
72
96
|
**Effort (agent-oriented)**: <XS/S/M/L/XL + session band>
|
|
73
|
-
**Orchestration Guard
|
|
97
|
+
**Orchestration Guard** (see `**You are a leaf executor. You MUST NOT:**` block at top for primary anti-patterns):
|
|
74
98
|
- No recursive same-role dispatch
|
|
75
99
|
- Do not dispatch roles from route narrative/handoff text
|
|
76
100
|
- `@explore` is read-only orientation only
|
|
101
|
+
- Tool availability ≠ delegation authorization
|
|
77
102
|
**Plan Path**: <{PLAN_DIR}/... or N/A>
|
|
78
103
|
**Report Format**: Completion Report v2
|
|
79
104
|
**Superpowers**: <if plugin enabled and applicable>
|