@mstar-harness/opencode 0.7.0 → 0.7.4

package/harness-skills/mstar-iteration/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mstar-iteration
-description: Morning Star 迭代管理 —— iteration-start（锁定迭代范围与 roadmap）、Autonomous Execute（per-plan 派发循环：分支→实现→QC→QA→Done→合并，含跨 plan 进度追踪与 push 纪律）、iteration-close（收口知识结晶 `mstar-compound`、更新 roadmap、标记迭代完成）。触发：PM 启动新迭代、跨 plan 编排时、或迭代内所有 plan Done 后。迭代 compass 落盘 `{ITERATION_DIR}/<iteration-id>-delivery-compass.md`；per-plan 状态 SSOT 仍为 `{HARNESS_DIR}/status.json`。适用于一次迭代锁定几个 spec 点（specify+clarify）、多个 plan、每个 plan 多个 tasks 的实践模式。
+description: Morning Star 迭代管理 —— iteration-start（锁定范围、Review & Edit chain 硬门禁）、Autonomous Execute（per-plan 派发循环）、iteration-close（独立 Phase：close gate、compound、roadmap、compass completed）。触发：PM 启动新迭代、跨 plan 编排、或全部 plan Done 后收口。compass：`{ITERATION_DIR}/<iteration-id>-delivery-compass.md`；per-plan SSOT：`{HARNESS_DIR}/status.json`。
 ---
 
 # mstar-iteration（迭代管理）
@@ -19,7 +19,7 @@ mstar 实践模式通常是：一次迭代锁定几个 spec 点（`specify + cla
 iteration-start → [per-plan lifecycle × N] → iteration-close → PR → merge
      │                                               │
      │ 锁定范围、创建 compass                        │ compound、更新 roadmap
-     │ 登记 plans 到 compass                         │ 标记迭代完成
+     │ Review & Edit chain → PM lock                 │ 标记迭代完成
      │ 创建 integration 分支                          │ commit 到 integration 分支
      │                                               │
      └──────── iteration-drive（跨 plan 追踪）────────┘
@@ -58,11 +58,11 @@ PM 在新迭代启动时执行。
 | **里程碑** | 关键节点与日期 |
 | **验收标准** | 迭代级别的 Done 定义 |
 | **非目标** | 明确排除在本次迭代外的事项 |
-| **Roadmap 上下文** | 本迭代在整体 roadmap 中的位置（本批做什么 / 下批做什么） |
+| **Roadmap 上下文** | 本迭代在整体 roadmap 中的位置（current iteration / next iteration） |
 
 ### 1.3 创建迭代 compass
 
-写入 `{ITERATION_DIR}/<iteration-id>-delivery-compass.md`：
+写入 `{ITERATION_DIR}/<iteration-id>-delivery-compass.md`。**必须**使用 `references/iteration-compass-template.md` 完整结构（YAML frontmatter + `## Roadmap Position` + close 占位节）。`end_date` 仅在 iteration-close 填入；禁止用正文 completion prose 替代 frontmatter `status`。
 
 ```markdown
 ---
@@ -95,8 +95,8 @@ plans: []
 - <明确排除的事项>
 
 ## Roadmap Position
-- 本批：<what this iteration delivers>
-- 下批：<what comes next, owner, trigger>
+- Current iteration: <what this iteration delivers>
+- Next iteration: <what comes next, owner, trigger>
 ```
 
 ### 1.4 更新索引
@@ -111,6 +111,21 @@ plans: []
 
 若使用 `status.json`，在 `plans[].metadata` 中为受影响的 plan 设置 `iteration_refs`。
 
+### 1.6 Review & Edit chain（integration 分支前强制）
+
+**iteration-start 在 PM lock 前不算完成**——compass/plans 初稿落盘 ≠ Done。
+
+与 host 命令 `iteration-start` §5 对齐：产物 SSOT 在本节；派发机制 SSOT 在命令 + **`mstar-dispatch-gates`**。
+
+PM **不得**将迭代 harness 文档 commit 到 `spec_integration_branch`，直到：
+
+1. **@product-manager**、**@architect**、**@writing-specialist** 已通过宿主 Task（或等价角色 invoke）**直接编辑**（非仅评论）compass、plans 及受影响 specs
+2. PM 将 compass `status` 设为 `locked`，并确认各 plan 的 Prepare gate（specify / clarify / plan）
+
+**完成证据** = 磁盘上的 compass / plans / specs 修订 + compass `status: locked`。**不**要求 `reports/<iteration-id>/` 审查报告——迭代审查的 SSOT 是被编辑的文档本身，无 per-plan QC 式审计链。
+
+**反模式**：PM 线程代替三角色完成全部编辑而不派发 Task —— 见 **`mstar-harness-core`** 反模式索引。
+
 ---
 
 ## Phase 2: Autonomous Execute（per-plan 派发驱动）
@@ -164,7 +179,7 @@ SSOT = `{HARNESS_DIR}/status.json` + `{PLAN_DIR}/`。todos 只追踪本轮下一
 5. **Cross-plan 进度同步**：更新 `{ITERATION_DIR}/<iteration-id>-delivery-compass.md` 的 `## Plans` 表状态列
 6. **Next plan** 从步骤 1 继续
 
-全部 plan `Done` → 停止循环，进入 **Phase 3: iteration-close**。
+全部 plan `Done` → **STOP** per-plan loop（§2.4 结束），打印 **`## Phase 3: iteration-close`**，按 §3.0 起独立执行。final plan 的 Assignment / closure 可以提供素材，但不能替代 Phase 3 gate。
 
 ### 2.5 Dispatch-first（implement 派发约束）
 
@@ -188,16 +203,40 @@ SSOT = `{HARNESS_DIR}/status.json` + `{PLAN_DIR}/`。todos 只追踪本轮下一
 
 ## Phase 3: iteration-close（收口迭代）
 
-PM 在迭代内全部 plan Done 后执行。**本 Phase 在 integration 分支上运行**，产出物 commit 到 integration 分支，随迭代 PR 合入 main。触发方：`commands/iteration-drive.md`（在 Autonomous Execute loop 全部 Done 后自动进入）。
+PM 在迭代内全部 plan Done 后执行。**本 Phase 在 integration 分支上运行**，产出物 commit 到 integration 分支，随迭代 PR 合入 main。触发方：`commands/iteration-drive.md`（Autonomous Execute 全部 Done 后进入）。
+
+**Close Done 定义**：§3.1→§3.5 全部完成；compass frontmatter 写入 `status: completed` + `end_date`；每篇新增 knowledge doc 已登记 `{KNOWLEDGE_DIR}/README.md`。只在 final plan 中写了 compound / roadmap / PR 说明，不算 iteration-close 完成。
+
+### 3.0 Phase boundary（HARD）
+
+- Phase 3 是 iteration 级收口，不是任一 plan 的子任务。
+- final plan closure、plan notes、plan compaction 可作为输入，但不能替代 §3.1→§3.5。
+- 读过 `mstar-iteration` / `mstar-compound` 不等于执行 gate；必须打印 checklist 并写入产物。
+
+### 3.0.5 Compass shape normalization（legacy 漂移修复）
 
-### 3.1 前置检查
+进入 §3.1 前，先确认 compass 具有 close 可写入的结构。若缺失，PM 在本 thread 做最小规范化，不委派、不重写无关内容。
 
-确认以下条件全部满足后，方可进入 iteration-close：
+| 检查 | 缺则补齐 |
+|------|----------|
+| YAML frontmatter：`iteration_id`, `start_date`, `status` | 从文件名 / 正文提取；收口前 `status` 保持 `active` 或 `locked` |
+| `## Roadmap Position` | 从 general context / roadmap prose 迁移为本节 |
+| `## Compound Round Summary` | 按模板补占位，§3.4 填写 |
+| `## Iteration Retrospective (minimal)` | 按模板补占位，§3.4 填写 |
 
-- [ ] 所有 compass 中登记的 plan 状态均为 `Done`
-- [ ] 所有 plan 的 residual findings 已收口（closed 或 accepted）
-- [ ] `{ITERATION_DIR}/<iteration-id>-delivery-compass.md` 各 plan 状态已同步到最新
-- [ ] 迭代验收标准已达成或显式豁免
+正文 completion status 只能作为历史注释；最终状态必须写入 frontmatter `status: completed` + `end_date`。
+
+### 3.1 Close entry checklist（HARD GATE）
+
+**STOP**: 打印下方 checklist，且全部为 `[x]` 后，才可进入 §3.2 Compound。
+
+- [ ] 所有 compass 中登记的 plan 在 `{HARNESS_DIR}/status.json` 均为 `Done`
+- [ ] 所有 plan 的 residual findings 已收口（closed 或 accepted；见 `mstar-plan-artifacts`）
+- [ ] compass `## Plans` 表状态列已与 `status.json` 同步
+- [ ] 迭代 `## Acceptance Criteria` 已达成或显式豁免（compass 或对话记录原因）
+- [ ] compass shape 已满足（frontmatter + `## Roadmap Position` + close 占位节）
+
+PM **必须**在对话中打印本 checklist；不得默认同过。
 
 ### 3.2 知识结晶（Compound）—— 迭代级核心收口
 
@@ -212,27 +251,44 @@ PM 触发 `mstar-compound`（可批量）：
    - 跨 plan 重复出现的模式
    - 有价值的排错经验
 
-2. **逐条结晶**：对每条识别出的知识，调用 `mstar-compound` 写入 `{KNOWLEDGE_DIR}/<category>/<slug>.md`
+2. **逐条判定**：对每条候选知识，回答 `mstar-compound` 的 Q1-Q8 自检；跳过项要在 compass `## Compound Round Summary` 记录原因。
+
+3. **写入或更新**：值得结晶的条目按 `mstar-compound` Phase 1-7 写入 `{KNOWLEDGE_DIR}/<category>/<slug>.md`，或在高重叠时更新已有文档。
 
-3. **是否值得结晶**：PM 使用 `mstar-compound` 中的「是否值得结晶」自检清单逐条评估（见 `mstar-compound` § 是否值得结晶）。
+4. **CONCEPTS.md 协同**：若迭代中引入了新的领域词汇，更新 `<repo-root>/CONCEPTS.md`（`mstar-compound` Phase 5）
 
-4. **CONCEPTS.md 协同**：若迭代中引入了新的领域词汇，更新 `<repo-root>/CONCEPTS.md`
+5. **索引登记（强制）**：每新增一篇 knowledge doc，必须完成 `mstar-compound` Phase 6，在 `{KNOWLEDGE_DIR}/README.md` 登记一行。Lightweight compound 不豁免 Phase 6。
+
+若本轮没有值得结晶的知识，仍须在 `## Compound Round Summary` 写明 `无可结晶知识` 及原因。
 
 ### 3.3 更新 roadmap
 
-1. 更新 compass 中的 `## Roadmap Position`：
-   - 本批状态标记为 `delivered`
-   - 下批更新为即将开始的内容
+1. 更新 compass **`## Roadmap Position`**（§3.0.5 已确保本节存在）：
+   - current iteration 行标记为 **`delivered`**（或等价明确措辞）
+   - next iteration 更新为即将开始的内容、触发条件、owner
 2. 若 `status.json` 中有 `plans[].metadata.roadmap` 字段，同步更新
-3. 若 `STRATEGY.md` 存在，可建议更新 `## Decision Log`（若有重大架构决策）
+3. 若存在 deferred-features / roadmap tracker 类文档，按项目惯例刷新
+4. 若 `STRATEGY.md` 存在，可更新 `## Decision Log`（重大架构决策时）
+
+### 3.4 标记迭代完成
+
+1. compass **YAML frontmatter**：`status: completed`，`end_date: YYYY-MM-DD`（必须；见 §3.0.5）
+2. 更新 `{ITERATION_DIR}/README.md` 索引中该迭代行 Status 为 `completed`
+3. 填充 compass `## Compound Round Summary` 与 `## Iteration Retrospective (minimal)`（见模板）
+
+### 3.5 Close exit checklist + commit
+
+**Precondition**: §3.1 checklist `[x]`；§3.4 frontmatter `completed` + `end_date` 已写。
 
-### 3.4 标记迭代完成 + Commit
+PM 打印 **iteration-close exit checklist**；全部为 `[x]` 后方可 `git commit` / 开 PR：
 
-1. 将 compass frontmatter `status` 更新为 `completed`，添加 `end_date`
-2. 更新 `{ITERATION_DIR}/README.md` 索引中该迭代行的 Status 为 `completed`
-3. compass 正文末尾追加 Compound Round Summary 和 Retrospective（见 compass 模板）
+- [ ] §3.1 前置 gate 已打印并满足
+- [ ] §3.2 compound 完成；新增 knowledge doc 均已登记 `{KNOWLEDGE_DIR}/README.md`（或已记录无可结晶原因）
+- [ ] §3.3 `## Roadmap Position` current iteration 已标 `delivered`；tracker / STRATEGY 已按需更新
+- [ ] §3.4 frontmatter `status: completed` + `end_date`；Compound Summary + Retrospective 已填
+- [ ] 当前分支是 `spec_integration_branch`
 
-**Commit 到 integration 分支**：iteration-close 产出的所有 harness 制品必须 commit 到当前 integration 分支，随迭代 PR 合入 main：
+**Commit 到 integration 分支**：
 
 ```bash
 git add {ITERATION_DIR}/<id>-delivery-compass.md {ITERATION_DIR}/README.md {KNOWLEDGE_DIR}/ CONCEPTS.md
@@ -240,7 +296,7 @@ git commit -m "chore(iteration): close <iteration-id> — compound round, roadma
 git push origin <spec_integration_branch>
 ```
 
-### 3.5 可选：触发 compound-refresh
+### 3.6 可选：触发 compound-refresh
 
 若本轮 compound 新增了较多知识文档，或 compass 标记了可能过时的旧知识，触发 `mstar-compound-refresh` 对有重叠的知识文档做维护。
 
@@ -270,4 +326,7 @@ git push origin <spec_integration_branch>
 - 不要在 iteration-drive 中修改 per-plan gate 判定
 - 不要用 compass 替代 `status.json` 作为 plan 状态 SSOT
 - 不要在没有完成 per-plan 前置检查的情况下进入 iteration-close
-- 不要跳过 compound——如果本迭代确实没有可结晶的知识，在 compass 中写 `Compound Round Summary: 无可结晶知识（原因：<简述>）`
+- 不要将 Phase 3 折叠进 final plan closure——须显式 §3.0→§3.5
+- 不要用 prose completion status 替代 compass frontmatter `status: completed` + `end_date`
+- 不要跳过 compound Phase 6（`{KNOWLEDGE_DIR}/README.md` 索引）——即使只结晶一篇文档
+- 不要跳过 compound——如果本迭代确实没有可结晶的知识，在 compass `## Compound Round Summary` 写 `无可结晶知识（原因：<简述>）`

package/harness-skills/mstar-iteration/references/iteration-compass-template.md

@@ -6,7 +6,6 @@ Copy this template when creating a new iteration compass in `{ITERATION_DIR}/`.
 ---
 iteration_id: <id>
 start_date: YYYY-MM-DD
-end_date: <filled at close>
 status: active
 plans: []
 ---
@@ -50,8 +49,8 @@ Status values: `Todo` | `InProgress` | `InReview` | `Done` | `Blocked`
 
 ## Roadmap Position
 
-- **本批（<iteration-id>）**：<what this iteration delivers>
-- **下批**：<what comes next>，触发条件：<condition>，owner：<who>
+- **Current iteration（<iteration-id>）**：<what this iteration delivers>
+- **Next iteration**：<what comes next>，触发条件：<condition>，owner：<who>
 - **最终目标**：<the long-term Done definition this iteration contributes to>
 
 ## Risk Register
@@ -83,14 +82,21 @@ Status values: `Todo` | `InProgress` | `InReview` | `Done` | `Blocked`
 |-------|----------|-------------|
 | `iteration_id` | Yes | iteration-start |
 | `start_date` | Yes | iteration-start |
-| `end_date` | No (fill at close) | iteration-close |
-| `status` | Yes | iteration-start → `active`; iteration-close → `completed` |
+| `end_date` | No | Add at iteration-close §3.4 only |
+| `status` | Yes | iteration-start → `active` / `locked`（§1.6 PM lock）；iteration-close §3.4 → **`completed`**（YAML frontmatter，非 prose completion status） |
 | `plans` (frontmatter) | Recommended | iteration-start (initial), iteration-drive (add new) |
 | `## Plans` table | Yes | iteration-drive (sync status), iteration-close (final) |
 | `## Milestones` | Recommended | iteration-start, iteration-drive (update) |
 | `## Acceptance Criteria` | Yes | iteration-start |
 | `## Non-Goals` | Yes | iteration-start |
-| `## Roadmap Position` | Yes | iteration-start, iteration-close (update) |
+| `## Roadmap Position` | **Yes** | iteration-start（必填节，非散落于 general context prose）；iteration-close §3.3（current iteration → `delivered`） |
 | `## Risk Register` | Optional | iteration-start, iteration-drive (update) |
-| `## Compound Round Summary` | Yes | iteration-close |
-| `## Iteration Retrospective` | Recommended | iteration-close |
+| `## Compound Round Summary` | Yes | iteration-close §3.4 |
+| `## Iteration Retrospective` | Recommended | iteration-close §3.4 |
+
+## Legacy compass drift
+
+若仓库中已有 compass **无** YAML frontmatter、**无** `## Roadmap Position`，或只有 prose completion status：
+
+- **新迭代**：iteration-start 必须按本模板重写，不延续 prose-only 惯例。
+- **收口时**：`mstar-iteration` §3.0.5 在 iteration-close 入口规范化，再执行 §3.3–§3.4。

package/harness-skills/mstar-phase-gates/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mstar-phase-gates
-description: Morning Star (启明星) Spec-Driven 双阶段门禁 —— Prepare（`specify → clarify → plan`）、Execute（`plan(locked) → tasks → implement`）、意图门禁、长期目标优先、分批 roadmap 强制落盘、clarify 核心纪律（共享理解 / 先探索 / 每问推荐答案）、hotfix 压缩路径、可验证编辑、Phase Gate 最小证据。**必须**在 PM 判定 gate、首次 implement 派单前、产品/架构参与 Prepare、或解释为何不能跳过 plan/clarify 时 Read；`@project-manager` 每轮编排非 hotfix 任务必读；`@product-manager` / `@architect` 写规格与锁 plan 时必读 Prepare 节；实现角色 Read Execute 与 hotfix 例外即可。Task category 与 `quick` 禁豁免规则仍在 `mstar-harness-core`。并行 Superpowers 短语见 `mstar-superpowers-align`。迭代级活动（iteration-start / iteration-close / compound）见 `mstar-iteration`。
+description: Morning Star (启明星) Spec-Driven 双阶段门禁 —— Prepare（`specify → clarify → plan`）、Execute（`plan(locked) → tasks → implement`）、意图门禁、长期目标优先、分批 roadmap 强制落盘、clarify 核心纪律（共享理解 / 先探索 / 每问推荐答案）、hotfix 压缩路径、可验证编辑、Phase Gate 最小证据。**必须**在 PM 判定 gate、首次 implement 派单前、产品/架构参与 Prepare、或解释为何不能跳过 plan/clarify 时 Read；`@project-manager` 每轮编排非 hotfix 任务必读；`@product-manager` / `@architect` 写规格与锁 plan 时必读 Prepare 节；实现角色 Read Execute 与 hotfix 例外即可。Task category 与 `quick` 禁豁免规则仍在 `mstar-harness-core`。实现行为见 `mstar-coding-behavior`。迭代级活动（iteration-start / iteration-close / compound）见 `mstar-iteration`。
 ---
 
 ## Load order（必读顺序）
@@ -28,7 +28,7 @@ description: Morning Star (启明星) Spec-Driven 双阶段门禁 —— Prepare
 
 - **`plan(locked)`** — 冻结基线；实现中出现新约束时**先回写 plan 再继续**。
 - **`tasks`** — 含依赖顺序、并行标记、完成判据；每任务可追踪到 plan、roadmap 批次与验收标准。
-  - **并行标签**：若 PM 将 ≥2 条实现轨 **同时** 分派，须在 `Superpowers` 中写入 `dispatching-parallel-agents`；同仓 ≥2 可写并发时叠 `using-git-worktrees`（见 **`mstar-superpowers-align`** 与 **`mstar-branch-worktree`**）。
+  - **并行标签**：若 PM 将 ≥2 条实现轨 **同时** 分派，须在 Assignment 写明 `Dispatch mode: parallel independent tracks`；同仓 ≥2 可写并发时写明 `Worktree isolation: required`（见 **`mstar-dispatch-gates`** 与 **`mstar-branch-worktree`**）。
 - **`implement`** — 按 tasks 顺序执行并提交自检证据；完成进入 `InReview`；遵循 **`mstar-coding-behavior`**。
 
 ### 可验证编辑与上下文纪律
@@ -81,7 +81,7 @@ description: Morning Star (启明星) Spec-Driven 双阶段门禁 —— Prepare
 - `tasks`
   - 目标：把 plan 拆成可执行任务与依赖顺序。
   - 最小产物：任务列表、并行标记、完成判据、映射到验收标准与 roadmap 批次。
-  - **PM**：若并行标记对应「多轨同时 implement」，在对外 **Status Update** 与实现 Assignment 的 **`Superpowers`** 中写入 **`dispatching-parallel-agents`**（或同义短语）；同仓多可写并发时叠 **`using-git-worktrees`**（见 `mstar-superpowers-align`）。
+  - **PM**：若并行标记对应「多轨同时 implement」，在对外 **Status Update** 与实现 Assignment 写入 **`Dispatch mode: parallel independent tracks`**；同仓多可写并发时叠 **`Worktree isolation: required`**（见 `mstar-dispatch-gates` 与 `mstar-branch-worktree`）。
 - `implement`
   - 目标：按任务执行并提交证据，进入审查。
   - 最小产物：实现 diff、自检证据、回报与 handoff。

package/harness-skills/mstar-plan-artifacts/references/plan-files-and-reports.md

@@ -35,7 +35,7 @@
 ## QC 三审触发时机（单 plan · 多 batch）
 
 - **默认（推荐）**：同一 **`plan_id`** 下，**完整 QC 三审**（`qc1` + `qc2` + `qc3` 并行）**仅在 dev team 按该 plan 约定范围全部交付之后**执行**一次**，再进入 `@project-manager` 汇总与 `@qa-engineer` 验证。**不要**在每个中间 **batch** / 子里程碑都跑全套三审：否则 `reports/<plan-id>/` 会堆积多套并列报告，**`Review range` / `Diff basis` 与结论**易混淆，handoff 成本高。
-- **batch 之间**：依赖实现方 **`verification-before-completion`**、主 plan 任务勾选与 PM 协调；需要书面中间意见时，用对话、主 plan 批注或**非三审**的定向检查（如单审、架构 review），**不**默认等同「又一轮完整三审」。
+- **batch 之间**：依赖实现方按 **`mstar-coding-behavior`** 提供完成证据、主 plan 任务勾选与 PM 协调；需要书面中间意见时，用对话、主 plan 批注或**非三审**的定向检查（如单审、架构 review），**不**默认等同「又一轮完整三审」。
 - **After `Request Changes` (default — targeted re-review)**：PM maps each **blocking** finding to the QC seat that raised it (`source` on R#, consolidated table, or the originating `qcN.md` / `F-###`). Dispatch **only** those reviewers (`QC re-review: targeted — reviewers: qc-specialist, qc-specialist-2, …`). Each re-reviewing QC **updates the same** `qc1.md` / `qc2.md` / `qc3.md` in place (add `## Revalidation`, refresh verdict / `generated_at`); **do not** add `qc1-rev2.md` siblings on this path. PM **updates the same** `qc-consolidated.md` in place. Git history is the audit trail.
 - **Full tri re-review (exception)**：Only when Assignment states **`QC re-review: full tri-review`**. Run **three** parallel reviews again; use **new basenames** (`qc1-rev2.md` … `qc3-rev2.md`, `qc-consolidated-rev2.md`) so wave-1 files stay immutable; PM states **active wave** in consolidated decision. See `mstar-review-qc` · `mstar-dispatch-gates`.
 - **显式例外**：仅当用户与 PM 书面同意**中间门禁**时，在 Assignment 写清 **`QC gate: incremental — <scope>`**（或等价），并仍须保证该次三审的 **`plan_id` + `Review range` / `Diff basis`** 三份一致；**优先**用子范围子目录，避免与终局 `qc1..3.md` 混名。

package/harness-skills/mstar-plan-conventions/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mstar-plan-conventions
-description: Morning Star (启明星) harness 计划目录约定 —— `{HARNESS_DIR}` / `{PLAN_DIR}` / `{ITERATION_DIR}` / `{KNOWLEDGE_DIR}` / `{SPECS_DIR}` 发现与初始化（默认 `.mstar/`，兼容 `.agents/`）、`docs/` 与 harness 子树边界、未启用 plan 时的工作方式、Spec 集成分支与多 Plan 实现分支（merge 靶与 PR 合 main）、Superpowers `writing-plans` 落盘门限、工期预估（agent-oriented）。**必须**在读写 `.mstar/` / `.agents/`、初始化 harness、编排含 plan 的任务、或对齐 `metadata.primary_spec` 时 Read；`@project-manager` 开 plan 任务前必读。plan 文件 / status / residual / reports / knowledge → **`mstar-plan-artifacts`**；分支与 QC 检出 → **`mstar-branch-worktree`**。
+description: Morning Star (启明星) harness 计划目录约定 —— `{HARNESS_DIR}` / `{PLAN_DIR}` / `{ITERATION_DIR}` / `{KNOWLEDGE_DIR}` / `{SPECS_DIR}` 发现与初始化（默认 `.mstar/`，兼容 `.agents/`）、`docs/` 与 harness 子树边界、未启用 plan 时的工作方式、Spec 集成分支与多 Plan 实现分支（merge 靶与 PR 合 main）、Morning Star plan-writing path gate、工期预估（agent-oriented）。**必须**在读写 `.mstar/` / `.agents/`、初始化 harness、编排含 plan 的任务、或对齐 `metadata.primary_spec` 时 Read；`@project-manager` 开 plan 任务前必读。plan 文件 / status / residual / reports / knowledge → **`mstar-plan-artifacts`**；分支与 QC 检出 → **`mstar-branch-worktree`**。
 ---
 
 ## Load order（必读顺序）
@@ -64,9 +64,9 @@ PM 在需要持久化追踪时：
 - Git 操作与 QC 单一 `HEAD` → **`mstar-branch-worktree`**。
 - `status.json` 登记 `spec_integration_branch` / `merge_target` → **`mstar-plan-artifacts`**。
 
-## Superpowers `writing-plans` 门限
+## Plan-Writing Path Gate
 
-计划写入 **`{PLAN_DIR}`**，**禁止**默认 `docs/superpowers/plans/`。见 **`mstar-superpowers-align`**。
+Plans are written to **`{PLAN_DIR}`** when persistent plan tracking is enabled. Do not introduce external default plan directories.
 
 ## 状态与权限（摘要）
 

package/harness-skills/mstar-roles/SKILL.md

@@ -43,12 +43,12 @@ Treat these as baseline dependencies **where the role touches implementation, re
 | `mstar-phase-gates` | Prepare/Execute gates, clarify, hotfix path, intention gate |
 | `mstar-dispatch-gates` | PM dispatch; **all leaf executors** before any Task/subagent call |
 | `mstar-branch-worktree` | Git write, parallel worktrees, QC/QA checkout fields |
-| `mstar-plan-conventions` | `{HARNESS_DIR}` discovery, init, Spec branch naming, `writing-plans` path |
+| `mstar-plan-conventions` | `{HARNESS_DIR}` discovery, init, Spec branch naming, plan-writing path gate |
 | `mstar-plan-artifacts` | Main plan, `reports/`, `status.json`, residual, knowledge/iteration, Done compaction |
 | `mstar-design-md` | DESIGN.md design system spec — create/audit/maintain tokens, completeness checklist, light/dark dual-theme |
 | `mstar-review-qc` | QC workflow, template, verdict, high-risk checks |
-| `mstar-coding-behavior` | Implementation/debug/refactor (**not** PM orchestration-only) |
-| `mstar-superpowers-align` | Superpowers plugin on; Assignment `Superpowers` lines |
+| `mstar-coding-behavior` | Implementation/debug/refactor/review-feedback handling (**not** PM orchestration-only) |
+| `mstar-skill-authoring` | New skills, major skill rewrites, trigger descriptions, behavior-shaping skill validation |
 | `mstar-compound` | Capturing solved problems as structured knowledge in `{KNOWLEDGE_DIR}`; Discoverability check; CONCEPTS.md synergy |
 | `mstar-compound-refresh` | Auditing/updating/consolidating knowledge docs; maintaining `{KNOWLEDGE_DIR}` accuracy |
 | `mstar-iteration` | Iteration lifecycle: iteration-start (scope/roadmap lock), Autonomous Execute (per-plan dispatch loop), iteration-close (compound + roadmap update) |
@@ -59,7 +59,7 @@ Treat these as baseline dependencies **where the role touches implementation, re
 
 | Role | Typical adds |
 | --- | --- |
-| `project-manager` | `mstar-dispatch-gates`, `mstar-phase-gates`, `mstar-plan-conventions`, `mstar-superpowers-align`, `mstar-roles` ref; + `mstar-review-qc` before QC; + `mstar-branch-worktree` / `mstar-plan-artifacts` as the round requires; + `mstar-iteration` for iteration lifecycle (start/drive/close); + `mstar-strategy` for strategic alignment; + `mstar-compound` / `mstar-compound-refresh` pre-loaded by `mstar-iteration` § iteration-close |
+| `project-manager` | `mstar-dispatch-gates`, `mstar-phase-gates`, `mstar-plan-conventions`, `mstar-roles` ref; + `mstar-review-qc` before QC; + `mstar-branch-worktree` / `mstar-plan-artifacts` as the round requires; + `mstar-skill-authoring` for skill work; + `mstar-iteration` for iteration lifecycle (start/drive/close); + `mstar-strategy` for strategic alignment; + `mstar-compound` / `mstar-compound-refresh` pre-loaded by `mstar-iteration` § iteration-close |
 | `fullstack-dev*`, `frontend-dev` | `mstar-coding-behavior`, `mstar-dispatch-gates`, `mstar-branch-worktree` (if repo writes); plan path symbols from `mstar-plan-conventions` (minimal); `mstar-design-md` when implementing styled UI |
 | `qc-specialist*` | `mstar-review-qc`, `mstar-branch-worktree`, `mstar-plan-artifacts` (report paths); `mstar-design-md` when reviewing UI |
 | `qa-engineer` | `mstar-review-qc`, `mstar-branch-worktree`, `mstar-plan-artifacts` (closing R#); `mstar-design-md` when verifying visual output |

package/harness-skills/mstar-roles/references/architect.md

@@ -2,9 +2,9 @@
 
 **Hub matrix:** `mstar-roles` SKILL.md.
 
-**Always:** `mstar-harness-core`, `mstar-dispatch-gates`, `mstar-phase-gates` (Prepare: specify/clarify/plan), `mstar-plan-conventions` (`{PLAN_DIR}`, `writing-plans` path).
+**Always:** `mstar-harness-core`, `mstar-dispatch-gates`, `mstar-phase-gates` (Prepare: specify/clarify/plan), `mstar-plan-conventions` (`{PLAN_DIR}`, plan-writing path).
 
-**Typically:** `mstar-plan-artifacts` (knowledge/specs/ADR placement); `mstar-design-md` (DESIGN.md design system spec — architect is primary creator); `mstar-coding-behavior` (surgical doc edits); `mstar-superpowers-align` (when plugin on).
+**Typically:** `mstar-plan-artifacts` (knowledge/specs/ADR placement); `mstar-design-md` (DESIGN.md design system spec — architect is primary creator); `mstar-coding-behavior` (surgical doc edits).
 
 **On demand:** `mstar-branch-worktree` (when committing architecture docs to the business repo).
 
@@ -28,23 +28,19 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 - **NEVER** treat document-level parallelism (“split into N plans”, “Plan 002–010”, “Phase X ∥ Phase Y”, “N parallel tracks”) as permission to **invoke N subagents** in this session. The **plan/spec/ADR artifacts** are your deliverable; **scheduling** parallel execution is **PM’s next round**, not part of this assignment unless `Delegation: allowed (...)` explicitly lists callees.
 - **NEVER** treat `Handoff: @project-manager / @fullstack-dev / @qa-engineer …`, role names inside Completion Report templates, routing tables, or “suggested owner” groupings as **host invoke commands**; they are **narrative**, not authorization.
 - **NEVER** infer you may call `Task` / subagents because the host **lists** `subagent_type` names (`architect`, `fullstack-dev`, …). **Tool availability ≠ delegation authorization**; only **`Delegation: allowed (...)`** grants callees.
-- **NEVER** load and execute Superpowers `dispatching-parallel-agents` yourself to fan out child agents; that skill is **PM-orchestration-only** (see `mstar-superpowers-align`). If parallel runners are needed, report to PM for re-dispatch.
+- **NEVER** execute parallel-agent dispatch yourself to fan out child agents; dispatch is **PM-orchestration-only** (see `mstar-dispatch-gates`). If parallel runners are needed, report to PM for re-dispatch.
 - **NEVER** treat `Gate Decision: blocked` (material, high-impact ambiguities still open) as permission to hand off “ready for implement” architecture—finish clarify, update the package, or return `Blocked` to PM.
 - **NEVER** use a temporary, mixed, or partial design as the selected approach unless the target architecture and staged roadmap are written in the assigned plan/spec. “Later” without a tracking location is `Blocked`, not a handoff.
 - **NEVER** edit application implementation source, automated tests, CI workflows, Dockerfiles, or secrets-bearing runtime configuration unless the assignment explicitly limits you to doc-only placeholders **and** PM recorded the risk acceptance.
-- **NEVER** persist planning artifacts from `writing-plans` (or equivalent) under upstream `docs/superpowers/plans/`; only `{PLAN_DIR}` per `mstar-plan-conventions`.
+- **NEVER** persist planning artifacts under external default plan directories; only `{PLAN_DIR}` per `mstar-plan-conventions`.
 
 These rules align with `mstar-harness-core` executor anti-recursion invariants.
 
-## Superpowers (When Enabled)
+## Execution Discipline
 
-Use as applicable:
+Use `mstar-phase-gates` for trade-off exploration and technical plan checkpoints. Use `mstar-coding-behavior` only when editing tracked files or responding to review feedback. Same-repo multi-writer parallelism is governed by `mstar-branch-worktree`.
 
-- `brainstorming` for major trade-off exploration
-- `writing-plans` for technical planning documentation
-- `using-git-worktrees` for same-repo multi-writer parallelism
-
-`writing-plans` outputs must follow `{PLAN_DIR}` from `mstar-plan-conventions`, not external default paths.
+Plan artifacts must follow `{PLAN_DIR}` from `mstar-plan-conventions`, not external default paths.
 
 ## Responsibilities
 

package/harness-skills/mstar-roles/references/frontend-dev.md

@@ -4,7 +4,7 @@
 
 **Always:** `mstar-harness-core`, `mstar-coding-behavior`, `mstar-dispatch-gates`.
 
-**Typically:** `mstar-plan-conventions` (paths + spec metadata); `mstar-superpowers-align` (when plugin on).
+**Typically:** `mstar-plan-conventions` (paths + spec metadata).
 
 **On demand:** `mstar-branch-worktree` (repo writes); `mstar-phase-gates` (Execute / hotfix when referenced in assignment); `mstar-design-md` (when implementing styled UI — read DESIGN.md for tokens before writing components).
 
@@ -28,7 +28,7 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 - **NEVER** invoke `frontend-dev`, `fullstack-dev`, `fullstack-dev-2`, or other roles to perform **this** assignment unless `Delegation: allowed (...)` explicitly lists them.
 - **NEVER** offload UI implementation, tests, or evidence to `@explore`; use glob/grep/read first—short read-only `@explore` only per `mstar-harness-core` explore boundaries.
 - **NEVER** treat `Handoff` lines, route arrows, Completion Report role lists, or routing prose as **invoke instructions**; they are narrative unless `Delegation: allowed` says otherwise.
-- **NEVER** run Superpowers `dispatching-parallel-agents` as an implementer; that skill is **PM-only** (`mstar-superpowers-align`).
+- **NEVER** run parallel-agent dispatch as an implementer; this is **PM-only** (`mstar-dispatch-gates`).
 - **NEVER** self-decide branch pivots (including switching to `main`/`master`) beyond PM’s `Working branch` / `Branch policy`; conflicting or missing branch facts => `Blocked` to PM.
 - **NEVER** start UI implementation while the assignment’s Prepare / execute prerequisites (`plan locked`, `tasks`, branch contract) are unmet—return `Blocked` to PM instead of silent partial delivery.
 

package/harness-skills/mstar-roles/references/fullstack-dev-shared.md

@@ -14,7 +14,7 @@ Behavior is shared; track identity is parameterized.
 
 **Always:** `mstar-harness-core`, `mstar-coding-behavior`, `mstar-dispatch-gates` (leaf anti-recursion before any Task/subagent).
 
-**Typically:** `mstar-plan-conventions` (path symbols + `metadata.primary_spec` / `spec_refs`); `mstar-superpowers-align` (when plugin on).
+**Typically:** `mstar-plan-conventions` (path symbols + `metadata.primary_spec` / `spec_refs`).
 
 **On demand:** `mstar-branch-worktree` (repo writes, `Working branch`); `mstar-phase-gates` (Execute / hotfix sections when gate fields are in the assignment); `mstar-design-md` (when task includes UI implementation — read DESIGN.md for design tokens).
 
@@ -40,7 +40,7 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 - **NEVER** invoke `fullstack-dev`, `fullstack-dev-2`, `frontend-dev`, or other roles to perform **this** assignment body unless `Delegation: allowed (...)` explicitly lists them.
 - **NEVER** offload implementation, tests, or evidence to `@explore`; use glob/grep/read first—short read-only `@explore` only per `mstar-harness-core` explore boundaries.
 - **NEVER** treat `Handoff` lines, route arrows, Completion Report role lists, or routing prose as **invoke instructions**; they are narrative unless `Delegation: allowed` says otherwise.
-- **NEVER** run Superpowers `dispatching-parallel-agents` as an implementer; that skill is **PM-only** (`mstar-superpowers-align`).
+- **NEVER** run parallel-agent dispatch as an implementer; this is **PM-only** (`mstar-dispatch-gates`).
 - **NEVER** self-decide branch pivots beyond PM’s `Working branch` / `Branch policy`; if `<base>` is missing or the working tree disagrees with the assignment, **Blocked** to PM.
 - **NEVER** start implementation while Prepare / execute prerequisites in the assignment are unmet—return `Blocked` to PM.
 

package/harness-skills/mstar-roles/references/ops-engineer.md

@@ -4,7 +4,7 @@
 
 **Always:** `mstar-harness-core`, `mstar-coding-behavior`, `mstar-dispatch-gates`, `mstar-review-qc` (high-risk ops checklist), `mstar-branch-worktree` (repo writes, production-touching branches).
 
-**Typically:** `mstar-plan-conventions` (paths); `mstar-superpowers-align` (when plugin on).
+**Typically:** `mstar-plan-conventions` (paths).
 
 **On demand:** `mstar-phase-gates` (hotfix compressed path when assignment says hotfix).
 
@@ -29,7 +29,7 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 - **NEVER** read multi-phase / “N rollout tracks” **plan narrative** as “I must invoke N subagents now”; scheduling parallel work is **PM-owned** after your plan exists.
 - **NEVER** treat `Handoff` lines, template role names, or routing tables as **invoke commands**; only `Delegation: allowed` authorizes callees.
 - **NEVER** infer tool exposure (`Task`, subagent menus) implies authorization; **tool availability ≠ delegation**.
-- **NEVER** run Superpowers `dispatching-parallel-agents` yourself; **PM-only** (`mstar-superpowers-align`).
+- **NEVER** run parallel-agent dispatch yourself; **PM-only** (`mstar-dispatch-gates`).
 - **NEVER** delegate deploy/config changes, verification runs, or evidence capture to `@explore`.
 
 ## Responsibilities

package/harness-skills/mstar-roles/references/product-manager.md

@@ -2,9 +2,9 @@
 
 **Hub matrix:** `mstar-roles` SKILL.md.
 
-**Always:** `mstar-harness-core`, `mstar-dispatch-gates`, `mstar-phase-gates` (Prepare / clarify), `mstar-plan-conventions` (`{PLAN_DIR}`, `writing-plans` path).
+**Always:** `mstar-harness-core`, `mstar-dispatch-gates`, `mstar-phase-gates` (Prepare / clarify), `mstar-plan-conventions` (`{PLAN_DIR}`, plan-writing path).
 
-**Typically:** `mstar-plan-artifacts` (specs, knowledge index); `mstar-design-md` (DESIGN.md design intent and requirements for UI planning); `mstar-coding-behavior` (surgical doc edits); `mstar-superpowers-align` (when plugin on).
+**Typically:** `mstar-plan-artifacts` (specs, knowledge index); `mstar-design-md` (DESIGN.md design intent and requirements for UI planning); `mstar-coding-behavior` (surgical doc edits).
 
 **On demand:** `mstar-branch-worktree` (when committing product docs to the business repo).
 
@@ -29,19 +29,17 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 - **NEVER** invoke `architect`, dev, QA, or other roles to author **your** PRD/spec/clarify body unless `Delegation: allowed (...)` explicitly lists them—their names in templates are **not** automatic callees.
 - **NEVER** treat `Handoff` lines, route arrows, Completion Report role lists, or routing prose as **invoke instructions**; only `Delegation: allowed` authorizes callees.
 - **NEVER** infer you may call subagents because the host lists `subagent_type` names; **tool availability ≠ authorization**.
-- **NEVER** run Superpowers `dispatching-parallel-agents` yourself; **PM-only** (`mstar-superpowers-align`).
-- **NEVER** point `writing-plans` output to upstream `docs/superpowers/plans/`; use `{PLAN_DIR}` per `mstar-plan-conventions`.
+- **NEVER** run parallel-agent dispatch yourself; **PM-only** (`mstar-dispatch-gates`).
+- **NEVER** point planning output to external default plan directories; use `{PLAN_DIR}` per `mstar-plan-conventions`.
 - **NEVER** offload PRD/product-doc drafting to `@explore`; short read-only orientation only per `mstar-harness-core`.
 - **NEVER** label a Prepare package as “ready for implement” while `Gate Decision: blocked` for material ambiguities—resolve, document waivers with PM, or return `Blocked`.
 - **NEVER** split delivery by saying “later / follow-up / next phase” without writing the product roadmap, deferred scope, and final completion definition in the assigned plan/spec.
 
-## Superpowers (When Enabled)
+## Execution Discipline
 
-- `brainstorming` for ambiguity-heavy discovery
-- `writing-plans` for executable product planning
-- `using-git-worktrees` for same-repo concurrent writers
+Use `mstar-phase-gates` for ambiguity-heavy discovery and executable plan checkpoints. Use `mstar-coding-behavior` only when editing tracked files or responding to review feedback. Same-repo concurrent writers are governed by `mstar-branch-worktree`.
 
-`writing-plans` outputs must follow `{PLAN_DIR}` from `mstar-plan-conventions`.
+Plan artifacts must follow `{PLAN_DIR}` from `mstar-plan-conventions`.
 
 ## Responsibilities
 

package/harness-skills/mstar-roles/references/project-manager/dispatch-and-assignment.md

@@ -24,7 +24,7 @@ For assignees (non-PM):
 
 - **NEVER** treat `Handoff: …`, Completion Report template role names, routing tables, or “suggested owners” as **host invoke commands**; they are narrative unless `Delegation: allowed` authorizes callees.
 - **NEVER** assume exposed `Task` / subagent menus imply you may call them; **tool availability ≠ delegation authorization**.
-- **NEVER** execute Superpowers `dispatching-parallel-agents` as a leaf assignee; that skill is **PM-orchestration-only** (`mstar-superpowers-align`).
+- **NEVER** execute parallel-agent dispatch as a leaf assignee; dispatch is **PM-orchestration-only** (`mstar-dispatch-gates`).
 - **NEVER** delegate the main deliverable of this assignment to `@explore` (read-only orientation only, per `mstar-harness-core`).
 - **NEVER** claim `Done` / pass in **Completion Report v2** without the commands, logs, or artifacts explicitly required by the assignment’s **Evidence Required** section (see `mstar-harness-core` evidence gates).
 
@@ -43,7 +43,7 @@ The **`**You are a leaf executor. You MUST NOT:**`** section (previously just pr
   - **`@fullstack-dev-2`**: "treat `@fullstack-dev` in routing narrative as a handoff or invoke target"
   - **`@qa-engineer`**: "start validation before QC reports are consolidated"; "modify application code"
   - **`@explore`-assigned**: "implement or modify code"
-  - **All non-PM**: "use `dispatching-parallel-agents`"; "spawn a subagent whose `subagent_type` matches your own `Execute as` role id"
+  - **All non-PM**: "dispatch parallel agents"; "spawn a subagent whose `subagent_type` matches your own `Execute as` role id"
 - Anti-patterns must be action-oriented ("auto-dispatch to …", "treat … as invoke", "start … before …") — not abstract descriptions.
 - If the assignment involves multiple QCs or parallel tracks, add a specific bullet about NOT serializing or pre-empting the parallel dispatch.
 - 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.
@@ -114,7 +114,7 @@ The **`**You are a leaf executor. You MUST NOT:**`** section (previously just pr
 - Tool availability ≠ delegation authorization
 **Plan Path**: <{PLAN_DIR}/... or N/A>
 **Report Format**: Completion Report v2
-**Superpowers**: <if plugin enabled and applicable>
+**Execution evidence**: <RCA/test-first/review feedback/evidence expectations for the assignee, if applicable>
 ```
 
 ## Completion Report v2 Template

package/harness-skills/mstar-roles/references/project-manager.md

@@ -6,9 +6,8 @@ Before any non-trivial PM action, read in order:
 2. `mstar-dispatch-gates` + `mstar-phase-gates` (dispatch + Prepare/Execute gates)
 3. Host adapter: `mstar-host` (detect host; Read `references/opencode.md`, `cursor.md`, or `codex.md`)
 4. `mstar-plan-conventions` (path discovery, init, Spec branch summary)
-5. `mstar-superpowers-align` (when Superpowers plugin is enabled)
-6. `mstar-review-qc` (same coordination round, **before** any QC dispatch)
-7. **On demand:** `mstar-branch-worktree` (parallel implement, QC/QA checkout); `mstar-plan-artifacts` (`status.json`, R#); `mstar-plan-artifacts` (InReview waves, reports naming)
+5. `mstar-review-qc` (same coordination round, **before** any QC dispatch)
+6. **On demand:** `mstar-branch-worktree` (parallel implement, QC/QA checkout); `mstar-plan-artifacts` (`status.json`, R#); `mstar-plan-artifacts` (InReview waves, reports naming)
 
 **Not required:** `mstar-coding-behavior` (orchestration-only PM work).
 
@@ -112,7 +111,7 @@ If any item below matches, fix the dispatch/plan state or mark `Blocked`—do **
 - **NEVER** register residuals only inside the plan narrative while skipping root `{HARNESS_DIR}/status.json` `residual_findings[<plan_id>]` when plan conventions require the SSOT field.
 - **NEVER** write non-canonical residual `severity` strings—use only the machine enum from `mstar-plan-artifacts`.
 - **NEVER** use `Task category: quick` to skip mandatory Prepare (`specify → clarify → plan`) for substantive work (`mstar-harness-core` hard rule).
-- **NEVER** omit `Superpowers` hooks when the plugin is enabled and the batch truly requires parallel dev (`dispatching-parallel-agents`) or same-repo multi-writer concurrency (`using-git-worktrees`) per `mstar-superpowers-align`.
+- **NEVER** omit native dispatch/worktree fields when the batch truly requires parallel dev (`Dispatch mode: parallel independent tracks`) or same-repo multi-writer concurrency (`Worktree isolation: required`) per `mstar-dispatch-gates` and `mstar-branch-worktree`.
 - **NEVER** point QC at a single dev worktree/`Review cwd` that cannot contain **all** claimed changes from parallel tracks until Git integration lands on one `Working branch` `HEAD` (`mstar-branch-worktree` QC/QA alignment).
 - **NEVER** label `QA: skipped` for report-only QA—still dispatch `@qa-engineer` with report-only mode; QC skip rules are separate and explicit.
 - **NEVER** let non-PM/non-QA roles mark plan `Done`.
@@ -175,7 +174,7 @@ Anti-patterns:
 - Q7: Is `quick` being misused to bypass prepare?
 - Q8: Is intention gate explicit before implement?
 - Q9: If QC tri-review, are alignment fields text-identical across three reviewers?
-- Q10: Is Delegation consistent with Superpowers usage?
+- Q10: Is `Delegation` consistent with dispatch and worktree usage?
 - Q11: For non-trivial plan, is PM Task Board published with coverage?
 - Q12: In invoke-based hosts, were matching invokes actually issued?
 - Q13: With **>=2 independent** backend/fullstack units, are owners spread across `fullstack-dev` and `fullstack-dev-2` (parallel or rotated), or is `single_stream_justified: yes` recorded with a real reason?

package/harness-skills/mstar-roles/references/prompt-engineer.md

@@ -4,7 +4,9 @@
 
 **Always:** `mstar-harness-core`, `mstar-dispatch-gates`.
 
-**When editing harness text:** read **all** topic skills you touch — at minimum `mstar-phase-gates`, `mstar-plan-conventions`, `mstar-plan-artifacts`, `mstar-plan-artifacts`, `mstar-branch-worktree`, `mstar-review-qc`, `mstar-coding-behavior`, `mstar-superpowers-align`, plus host adapters — so prompts stay aligned with SSOT and do not re-duplicate rules.
+**When editing harness text:** read **all** topic skills you touch — at minimum `mstar-phase-gates`, `mstar-plan-conventions`, `mstar-plan-artifacts`, `mstar-branch-worktree`, `mstar-review-qc`, `mstar-coding-behavior`, plus host adapters — so prompts stay aligned with SSOT and do not re-duplicate rules.
+
+**When creating a new skill, making a major skill rewrite, or changing trigger descriptions:** MUST read `mstar-skill-authoring` before editing.
 
 **Typically:** `mstar-plan-conventions` (path symbols in examples).
 
@@ -28,9 +30,9 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 - **NEVER** invoke `prompt-engineer` or other roles to perform **this** prompt/skill/rule assignment—even when editing files “owned by” another role’s prompt pack, **you** perform the edit; those role names are **targets**, not callees.
 - **NEVER** treat `Handoff` lines, template role lists, or routing prose as **invoke instructions**; only `Delegation: allowed` authorizes callees.
 - **NEVER** infer tool exposure implies authorization; **tool availability ≠ delegation**.
-- **NEVER** run Superpowers `dispatching-parallel-agents` yourself; **PM-only** (`mstar-superpowers-align`).
+- **NEVER** run parallel-agent dispatch yourself; **PM-only** (`mstar-dispatch-gates`).
 - **NEVER** outsource prompt/skill/rule design, edits, or validation evidence to `@explore`.
-- **NEVER** merge prompt/skill/rule text that contradicts `mstar-harness-core`, `mstar-review-qc`, or `mstar-superpowers-align` without an explicit documented exception approved by PM (harness SSOT wins by default).
+- **NEVER** merge prompt/skill/rule text that contradicts `mstar-harness-core`, `mstar-review-qc`, or `mstar-coding-behavior` without an explicit documented exception approved by PM (harness SSOT wins by default).
 
 ## Responsibilities
 
@@ -46,13 +48,17 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 
 ## Skill Authoring Requirement
 
-When creating/updating skills, use the `skill-creator` workflow as required by repository practice.
+When creating a new skill, making a major skill rewrite, changing frontmatter `description`, or changing behavior-shaping skill text:
+
+1. MUST read `mstar-skill-authoring` before editing.
+2. MUST follow the repository `skill-creator` requirement when the change is a new skill or major rewrite.
+3. MUST include validation evidence for behavior-shaping changes, or explicitly state why only manual/search validation is practical.
 
 ## Prompt Change Minimal Checklist
 
 - Trigger conditions and non-goals are explicit
 - Output/evidence expectations are testable
-- No conflict with `mstar-harness-core`, `mstar-review-qc`, `mstar-superpowers-align`
+- No conflict with `mstar-harness-core`, `mstar-review-qc`, or `mstar-skill-authoring`
 - Redundancy removed before adding new constraints
 - At least one replayable scenario exists for regression check
 

package/harness-skills/mstar-roles/references/qa-engineer.md

@@ -4,7 +4,7 @@
 
 **Always:** `mstar-harness-core`, `mstar-review-qc`, `mstar-coding-behavior`, `mstar-dispatch-gates`, `mstar-branch-worktree` (same checkout fields as QC for the feature).
 
-**Typically:** `mstar-plan-conventions` (paths); `mstar-superpowers-align` (when plugin on).
+**Typically:** `mstar-plan-conventions` (paths).
 
 **On demand:** `mstar-plan-artifacts` (closing R# after verified fix); `mstar-phase-gates` (gate checklist when assignment references verification phase); `mstar-design-md` (when verifying UI — check visual output against DESIGN.md).
 
@@ -30,7 +30,7 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 - **NEVER** switch to an unprescribed worktree/branch to “pick up the other half” of parallel development; if the current `HEAD` cannot contain the claimed diff scope, **Blocked** and ask PM for Git integration or a corrected assignment (`mstar-branch-worktree`).
 - **NEVER** treat `Handoff` / template role lists / route arrows as invoke instructions; only `Delegation: allowed` authorizes callees.
 - **NEVER** infer tool exposure implies authorization; **tool availability ≠ delegation**.
-- **NEVER** run Superpowers `dispatching-parallel-agents` yourself; **PM-only** (`mstar-superpowers-align`).
+- **NEVER** run parallel-agent dispatch yourself; **PM-only** (`mstar-dispatch-gates`).
 - **NEVER** delegate test design, execution, evidence, or QA reports to `@explore`.
 - **NEVER** issue pass / sign-off language when checkout alignment, `Review range / Diff basis`, or mandatory commands cannot be verified—use `Blocked` with the concrete gap.