@mstar-harness/opencode 0.7.0 → 0.7.4

package/INSTALL.md

@@ -6,14 +6,11 @@
 
 ## Installation
 
-Add Morning Star to the `plugin` array in your `opencode.json` (global or project-level).
-
-If you use Superpowers together, use:
+Add Morning Star to the `plugin` array in your `opencode.json` (global or project-level):
 
 ```json
 {
   "plugin": [
-    "superpowers@git+https://github.com/obra/superpowers.git",
     "@mstar-harness/opencode@latest"
   ]
 }
@@ -64,7 +61,7 @@ The `@mstar-harness/cli` package (`npx @mstar-harness/cli init`) migrates that e
 
 ### Plugin not loading
 
-1. Check logs: `opencode run --print-logs "hello" 2>&1 | grep -i superpowers`
+1. Check logs: `opencode run --print-logs "hello" 2>&1 | grep -i mstar`
 2. Verify the plugin line in your `opencode.json`
 3. Make sure you're running a recent version of OpenCode
 

package/harness-commands/iteration-drive.md

@@ -13,9 +13,10 @@ Drive the active Morning Star iteration forward. The canonical flow is in **`mst
 1. `mstar-harness-core`
 2. `mstar-roles` → `references/project-manager.md`
 3. `skills/pm/SKILL.md` → **§ Host entry** + **§ Boot**（PM role identity + dispatch-first rules）
-4. `mstar-iteration` → **§ Phase 2: Autonomous Execute**（per-plan dispatch loop）+ **§ Phase 3: iteration-close**（compound + compass）
-5. `mstar-dispatch-gates` + host reference
-6. `mstar-plan-artifacts`, `mstar-plan-conventions`, `mstar-branch-worktree`
+4. `mstar-iteration` → **§ Phase 2** + **§ Phase 3**（close 为独立 gate，§3.0–§3.5）
+5. `mstar-compound` — Phase 3 §3.2 前加载（含 Phase 6 索引登记）
+6. `mstar-dispatch-gates` + host reference
+7. `mstar-plan-artifacts`, `mstar-plan-conventions`, `mstar-branch-worktree`
 
 ## Phase 2: Autonomous Execute
 
@@ -39,12 +40,16 @@ Execute **`mstar-iteration` § Phase 2** exactly. Summary:
 
 ## Phase 3: iteration-close
 
-When every plan is `Done`, execute **`mstar-iteration` § Phase 3**:
+当 **every** plan 为 `Done` 时，**STOP** per-plan loop，打印 `## Phase 3: iteration-close`，按 **`mstar-iteration` § Phase 3** 逐步执行。final plan 的 closure 只能提供输入，不能替代 close gate。
 
-1. **前置检查** (§ 3.1) — all plans Done, residuals closed, compass synced
-2. **Compound 轮** (§ 3.2) — 收集素材 → 自检清单（Q1-Q8）→ `mstar-compound` → CONCEPTS.md
-3. **更新 compass** (§ 3.3-3.4) — status → completed, roadmap, compound summary, retrospective, index
-4. **Commit** to integration branch:
+| Step | Section | 要点 |
+|------|---------|------|
+| 1 | §3.0 / §3.0.5 | Phase 边界；legacy compass 规范化（frontmatter + `## Roadmap Position`） |
+| 2 | §3.1 | 打印 close entry checklist，全部 `[x]` |
+| 3 | §3.2 | Compound；新增 doc 完成 `mstar-compound` Phase 6（`{KNOWLEDGE_DIR}/README.md`） |
+| 4 | §3.3 | `## Roadmap Position` current iteration → `delivered`；STRATEGY/tracker 按需更新 |
+| 5 | §3.4 | frontmatter `status: completed` + `end_date`；Compound Summary + Retrospective |
+| 6 | §3.5 | 打印 close exit checklist → commit → push |
 
 ```bash
 git add {ITERATION_DIR}/ {KNOWLEDGE_DIR}/ CONCEPTS.md
@@ -52,6 +57,8 @@ git commit -m "chore(iteration): close <iteration-id> — compound round, roadma
 git push origin <spec_integration_branch>
 ```
 
+**Not Done until**: §3.5 checklist `[x]` + compass frontmatter `completed`.
+
 ## Completion: Create PR
 
 All iteration-close changes committed to integration branch:

package/harness-commands/iteration-start.md

@@ -1,21 +1,24 @@
 ---
 name: iteration-start
-description: Start a new harness iteration — research backlog, lock direction with grill-me, produce compass/plans, run edit chain (product-manager → architect → writing-specialist each review-and-edit, then PM final review and lock), submit to integration branch
+description: Start a new harness iteration — research backlog, lock direction with grill-me, produce compass/plans, run mandatory Review & Edit chain via Task dispatch (product-manager → architect → writing-specialist each review-and-edit, then PM final lock), then integration branch. Not Done until review chain completes and compass is locked.
 agent: project-manager
 ---
 
 # Start Iteration
 
-Start a new Morning Star harness iteration. Detailed workflow → **`mstar-iteration` § Phase 1: iteration-start**；per-plan Prepare gates → **`mstar-phase-gates`**（specify → clarify → plan）。
+Start a new Morning Star harness iteration. **Not Done until the Review & Edit chain runs via dispatched roles and PM lock — not when compass files are first written.**
+
+Detailed workflow → **`mstar-iteration` § Phase 1: iteration-start**（含 §1.6 Review & Edit chain）；per-plan Prepare gates → **`mstar-phase-gates`**（specify → clarify → plan）。
 
 ## 0. Boot
 
 1. `mstar-harness-core`
 2. `mstar-roles` → `references/project-manager.md`
 3. `skills/pm/SKILL.md` → **§ Host entry** + **§ Boot**
-4. `mstar-iteration` → **§ Phase 1: iteration-start**（迭代范围、compass 模板、状态初始化）
-5. `mstar-phase-gates` → Prepare（specify → clarify → plan）
-6. `mstar-plan-conventions`, `mstar-plan-artifacts`
+4. `mstar-iteration` → **§ Phase 1: iteration-start**（迭代范围、compass 模板、§1.6 Review & Edit chain、状态初始化）
+5. `mstar-dispatch-gates` → iteration-start review chain + implement dispatch
+6. `mstar-phase-gates` → Prepare（specify → clarify → plan）
+7. `mstar-plan-conventions`, `mstar-plan-artifacts`
 
 ## 1. Research
 
@@ -63,17 +66,49 @@ Produce harness artifacts per **`mstar-iteration` § 1.3 创建迭代 compass**
 - Register all plans in `{HARNESS_DIR}/status.json`（per `mstar-plan-artifacts`）
 - Update `{ITERATION_DIR}/README.md` index（per `mstar-iteration` § 1.4）
 
-## 5. Review & Edit Chain
+## 5. Review & Edit Chain（HARD GATE — do not commit before this）
+
+**STOP**: Do not run §6 Integration Branch until **all** rows below are true.
 
 Each role below **reviews and directly edits** the documents. Do not just flag issues — apply the fixes yourself. PM only steps in for the final lock.
 
-1. **@product-manager** — review and edit the compass; adjust scope, priorities, and user-facing details; write or update specs in `{SPECS_DIR}/`
-2. **@architect** — review and edit the compass and specs; adjust technical architecture, interface contracts, module boundaries, and trade-off reasoning
-3. **@writing-specialist** — review and edit all documents for clarity, consistency, completeness, and bilingual parity; tighten prose, unify terminology, and remove ambiguity
-4. **PM** — final review; lock all documents; confirm Prepare phase gates pass
+| # | Role | Required action |
+|---|------|-----------------|
+| 5.1 | **@product-manager** | Task subagent: **edit** compass, plans, `{SPECS_DIR}/`; scope, UX, priorities |
+| 5.2 | **@architect** | Task subagent: **edit** compass, plans, specs; contracts, SQL, module boundaries |
+| 5.3 | **@writing-specialist** | Task subagent: **edit** all iteration docs; terminology, structure, clarity |
+| 5.4 | **@project-manager** | Merge subagent edits; resolve conflicts; **lock** compass (`status: locked`); confirm Prepare gates |
+
+**Evidence of done** = edited compass / plans / specs on disk + compass `status: locked`. **No** separate iteration review reports under `reports/` — unlike per-plan QC, there is no downstream audit chain to preserve.
+
+**Tool rule (Cursor / hosts with Task)**:
+- Steps 5.1–5.3: **MUST** use `Task` (parallel when independent). See **`mstar-dispatch-gates`** · iteration-start review chain.
+- PM thread **MUST NOT** substitute by performing all three specialist edits itself.
+- Exception: user explicitly waives subagent dispatch ("PM-only review").
+
+**Prepare gate (per plan in compass)**:
+- [ ] specify / clarify / plan = done on each plan file
+- [ ] `primary_spec` path exists (if declared)
+- [ ] `blocked_by` / sequential deps documented
+
+Only after 5.4 → proceed to §6.
+
+### iteration-start pre-commit checklist
+
+PM must print this block before §6; all `[ ]` must be `[x]`:
+
+- [ ] grill-me decisions recorded in compass
+- [ ] Draft compass + plans + `status.json` registered
+- [ ] @product-manager Task completed — compass / plans / specs edited
+- [ ] @architect Task completed — compass / specs edited
+- [ ] @writing-specialist Task completed — iteration docs edited
+- [ ] PM final lock: compass `status: locked`; Prepare gates pass (blocked plans documented)
+- [ ] **THEN**: git commit + push `iteration/<iteration-id>`
 
 ## 6. Integration Branch
 
+**Precondition**: §5 complete — compass `status: locked`; specialist Tasks returned; Prepare gates confirmed.
+
 - Create `iteration/<iteration-id>` from `main`
 - Register `spec_integration_branch` in `{HARNESS_DIR}/status.json`
 - Commit all documents to the integration branch and push to remote

package/harness-skills/mstar-branch-worktree/SKILL.md

@@ -105,16 +105,16 @@ description: Morning Star business-repo Git feature branches, same-repo concurre
 
 当 **`@project-manager` 在同一调度轮次内并发启动多个** subagent（含宿主侧「并行 Task / 并行 subagent」），且 **≥2 个承接方**可能对 **同一 Git 仓库的同一工作区（同一 cwd 检出目录）**产生写文件或 `git commit` 级改动时：
 
-- **必须**为每条并发写流使用 **独立检出目录**：以 **`git worktree`** 隔离（流程与目录安全要求见 Superpowers **`using-git-worktrees`**；未安装插件时仍须达到同等隔离效果，可 Read 该技能文件并按 `git worktree` 手册执行）。
+- **必须**为每条并发写流使用 **独立检出目录**：优先使用宿主原生 worktree/checkout 隔离能力；没有原生能力时使用 `git worktree`，并按本 skill 的目录、分支和 QC/QA 对齐规则执行。
 - **必须**与既有分支门禁一致：每个可写承接方的 Assignment 仍须含 PM 已批准的 **`Working branch`** / **`Branch policy`**；在某一 worktree 内 **不得**擅自 `checkout` 到未授权分支或私自新建分支。
-- **PM 须在 Assignment 中写清**各并发写流的 **检出约定**（例如预期 **`Worktree path`** / 命名规则，或「由承接方按 `using-git-worktrees` 创建并在 Completion Report 回报路径」），避免多代理默认共享同一目录导致互相覆盖、冲突或半写入状态。
+- **PM 须在 Assignment 中写清**各并发写流的 **检出约定**（例如预期 **`Worktree path`** / 命名规则，或「由承接方创建/使用隔离 worktree 并在 Completion Report 回报路径」），避免多代理默认共享同一目录导致互相覆盖、冲突或半写入状态。
 - **同仓、同一 plan、≥2 可写并行轨**：**推荐**在首次向各轨下发实现 Assignment **之前**，先由 PM 与用户确认 **`Branch policy`**，并 **明确 plan 集成分支与各轨 topic 分支的关系**（见下节 **「推荐默认编排：先建 plan 集成分支，再挂各 worktree」**），再为各轨约定 **`git worktree`**。这样 QC 前可把各轨 **自然归并**到同一条 **`HEAD`**，减少「多头分支、无合并靶」导致的误派。
 
 **可不强制新开 worktree** 的情形包括：并发流 **全部为只读**；各写入者针对 **不同 Git 仓库根**；或写入 **串行**（同一时刻仅一个代理持有该仓工作区）。
 
 ### 并发 subagent 与同仓工作树（对齐）
 
-当多个可写 subagent **并发**修改 **同一仓库** 时，**不得**共用同一检出目录作为写入 cwd。PM 在分派前应规划 **`git worktree`** 隔离（Superpowers **`using-git-worktrees`**），并在各承接方 Assignment 中写明 **`Working branch`** / **`Branch policy`** 及 **检出路径约定**（或要求回报实际 worktree 路径）。单分支决策权仍仅属 PM；worktree 只解决「目录与工作区隔离」，不替代分支授权。
+当多个可写 subagent **并发**修改 **同一仓库** 时，**不得**共用同一检出目录作为写入 cwd。PM 在分派前应规划 worktree/checkout 隔离，并在各承接方 Assignment 中写明 **`Working branch`** / **`Branch policy`** 及 **检出路径约定**（或要求回报实际 worktree 路径）。单分支决策权仍仅属 PM；worktree 只解决「目录与工作区隔离」，不替代分支授权。
 
 **同仓、同一 plan、多可写并行轨（推荐）**：在挂齐各轨 `git worktree` **之前**，先与用户确认并写明 **plan 集成分支**（从商定 `<base>` 创建）及各轨 **topic 分支** 如何从该线分出或如何 **merge 回** 该线；QC 前再将待一并验收的提交 **全部归并**到 PM 指定为 QC **`Working branch`** 的那条分支的 **`HEAD`**。分步说明与示例命名边界见下节 **「推荐默认编排：先建 plan 集成分支，再挂各 worktree」**。
 
@@ -137,7 +137,7 @@ description: Morning Star business-repo Git feature branches, same-repo concurre
 
 开发在 **feature 分支**上完成（往往在 **独立 worktree** 中实现）后，**QC 审查与 QA 验证针对的都是这份 feature**，而不是 `main` 或任意未对齐的默认 cwd。
 
-- **`@project-manager`** 分派 **QC** 时须在 Assignment 写明与待审实现一致的 **`Working branch`**，并写明 **`Review cwd` / `Worktree path`**：**优先**沿用开发 **Completion Report** 中回报的业务仓 **实现检出路径**（即「该 feature 的 worktree」）**当且仅当**该路径上的检出分支 **`HEAD` 已包含本轮待审的全部提交**（含曾发生在其他并行 worktree、现已归并到该分支的变更）。否则 **必须**改用 **集成完成后的** `Working branch` 与对应检出路径（或按 **`using-git-worktrees`** 在该分支上 **另开** 审查专用目录）。若开发未用 worktree，则写明单一明确的业务仓根路径。若审查需与开发目录 **物理分离** 但仍审 **同一分支**，可指示按 **`using-git-worktrees`** 在 **`Working branch`** 上 **另加** 一个 worktree 专供审查（只读使用业务仓）。**多流并行开发**时的前置归并、**推荐默认编排（plan 集成分支先行）** 与误派禁令见上一小节。
+- **`@project-manager`** 分派 **QC** 时须在 Assignment 写明与待审实现一致的 **`Working branch`**，并写明 **`Review cwd` / `Worktree path`**：**优先**沿用开发 **Completion Report** 中回报的业务仓 **实现检出路径**（即「该 feature 的 worktree」）**当且仅当**该路径上的检出分支 **`HEAD` 已包含本轮待审的全部提交**（含曾发生在其他并行 worktree、现已归并到该分支的变更）。否则 **必须**改用 **集成完成后的** `Working branch` 与对应检出路径（或在该分支上 **另开** 审查专用 worktree）。若开发未用 worktree，则写明单一明确的业务仓根路径。若审查需与开发目录 **物理分离** 但仍审 **同一分支**，可指示在 **`Working branch`** 上 **另加** 一个 worktree 专供审查（只读使用业务仓）。**多流并行开发**时的前置归并、**推荐默认编排（plan 集成分支先行）** 与误派禁令见上一小节。
 - **三票审同一功能（强制对齐）**：分派 **QC 三审**时，除上述字段外，**必须**在 **三份 Assignment 中逐字写入相同**的 **`plan_id`** 与 **`Review range` / `Diff basis`**：
   - **`plan_id`**：与 `{PLAN_DIR}/reports/<plan-id>/` 及主 **Plan Path** 一致；无 `{PLAN_DIR}` 流程时写 **`plan_id: N/A`**，并另给一行 **`Feature / scope label`**（不可歧义，足以与并行其它 feature 区分）。
   - **`Review range` / `Diff basis`**：明确本次审查所针对的 **diff/提交范围**（例如 `merge-base: origin/main` + `tip: HEAD`；或 `rev-range: <full-40>..<full-40>`；或一句 `equivalent to: git diff <merge-base>...HEAD`，以团队可复现为准）。**三名 reviewer 的 Assignment 间该字段必须完全一致**；**@qa-engineer** 验证同一 feature 时 **复用同一 `plan_id` 与同一 `Review range` / `Diff basis`**。**热修 / QC 单审**路径也须含 **同一组字段**，仅承接方份数为 1。

package/harness-skills/mstar-coding-behavior/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mstar-coding-behavior
-description: Morning Star (启明星) 跨角色通用编码行为准则 —— Think Before Coding（先读懂再改、显式假设、不静默猜测、读 imports/test/项目模式）、Simplicity First（YAGNI 优先不写代码、The Ladder 决策层级含依赖评估、删除优于添加、简洁优于聪明、5 项具名反模式速查、`simplify:` 标记天花板与升级路径、最小耐久切片）、Surgical Changes（改动可追溯、Bug 修根因先 grep 所有调用点、不顺手重构、不 piggyback）、Debugging（读完整报错与栈追踪、先复现、一步一测、根因分析、Bug 修复前先写复现测试、卡住时坦白）、Goal-Driven Execution（非平凡逻辑必留一个可运行检查、模糊请求转可验证结果、测行为不测实现、已有测试前后对比、不能测试说理由、Step → verify 微模板、分批留 roadmap）、Communication（说做了什么及为什么、标记顾虑、精确表达不确定性、不解释已知的、commit message 质量）。任何实现、调试、重构、审查任务都应优先 Read 本 skill；`@fullstack-dev` / `@frontend-dev` / `@fullstack-dev-2` / `@architect` / `@qa-engineer` / `@ops-engineer` / `@prompt-engineer` 动手前必读；QC 审查员核对变更是否只做了该做的手术时必读。本 skill 不覆盖分支门禁、QC/QA 路由、Assignment 权限、Done 所有权等不变量（那些以 `mstar-harness-core` 为准）。
+description: Morning Star (启明星) 跨角色通用编码行为准则 —— Think Before Coding（先读懂再改、显式假设、不静默猜测、读 imports/test/项目模式）、Simplicity First（YAGNI 优先不写代码、The Ladder 决策层级含依赖评估、删除优于添加、简洁优于聪明、5 项具名反模式速查、`simplify:` 标记天花板与升级路径、最小耐久切片）、Surgical Changes（改动可追溯、Bug 修根因先 grep 所有调用点、不顺手重构、不 piggyback）、Debugging（读完整报错与栈追踪、先复现、一步一测、根因分析、Bug 修复前先写复现测试、卡住时坦白）、Review Feedback Handling（先核实反馈再改、逐项处理、可用证据反驳错误建议）、Goal-Driven Execution（非平凡逻辑必留一个可运行检查、模糊请求转可验证结果、测行为不测实现、已有测试前后对比、不能测试说理由、Step → verify 微模板、分批留 roadmap）、Communication（说做了什么及为什么、标记顾虑、精确表达不确定性、不解释已知的、commit message 质量）。任何实现、调试、重构、审查任务都应优先 Read 本 skill；`@fullstack-dev` / `@frontend-dev` / `@fullstack-dev-2` / `@architect` / `@qa-engineer` / `@ops-engineer` / `@prompt-engineer` 动手前必读；QC 审查员核对变更是否只做了该做的手术时必读。本 skill 不覆盖分支门禁、QC/QA 路由、Assignment 权限、Done 所有权等不变量（那些以 `mstar-harness-core` 为准）。
 ---
 
 ## Load order（必读顺序）
@@ -166,7 +166,31 @@ Micro template:
 - **Test behavior, not implementation.** A test that checks whether a constructor sets properties is worthless. A test that checks whether validation actually rejects bad input is valuable. Focus on the interesting cases.
 - **If you cannot write a test, say why.** "I cannot easily test this because the database calls are tightly coupled to the business logic" is useful information that may signal a need for restructuring. Do not skip testing without an explanation.
 
-## 6) Communication
+## 6) Review Feedback Handling
+
+Core idea: review feedback is technical input, not an order to perform unverified edits.
+
+When receiving code review, QA, CI, or human feedback:
+
+1. Read all feedback before editing.
+2. Clarify ambiguous items before partial implementation.
+3. Verify each suggestion against codebase reality.
+4. Apply technically correct feedback one item at a time.
+5. Test each fix individually where practical.
+6. Push back with evidence when feedback is incorrect, obsolete, risky, out of scope, or violates YAGNI.
+
+Feedback priority:
+
+| Feedback type | Handling |
+|---|---|
+| Security, correctness, data loss, build/test failure | Fix or escalate before proceeding. |
+| Scope mismatch, reviewer misunderstanding, obsolete assumption | Verify and push back with evidence. |
+| Style-only suggestion | Apply only if it matches project conventions or is requested by the user/PM. |
+| New feature disguised as review | Route through PM/plan unless explicitly in scope. |
+
+Do not perform agreement. State the technical action, the verification result, or the technical reason for disagreement.
+
+## 7) Communication
 
 Core idea: how you communicate about code matters as much as the code itself.
 
@@ -178,8 +202,7 @@ Core idea: how you communicate about code matters as much as the code itself.
 
 ## Integration Notes
 
-- This skill is additive to `verification-before-completion` (见 `mstar-superpowers-align`) and other Morning Star controls.
-- It must not be used to bypass:
+- This skill must not be used to bypass:
   - branch constraints,
   - QC/QA gate definitions,
   - assignment authority,

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

@@ -211,6 +211,8 @@ If `CONCEPTS.md` doesn't exist yet, ask whether to seed it. A seed populates the
 
 2. If `plan_id` was provided, optionally update `status.json` metadata to reference this doc under `knowledge_refs`.
 
+**iteration-close gate**: `mstar-iteration` §3.2 #5 — **each** new doc in the compound round must complete this phase; do not skip for lightweight captures.
+
 ## Phase 7: Refresh trigger
 
 After capturing, check if the new learning suggests an older doc may now be stale (contradicted, superseded, or in a refactored domain). If so, recommend:

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

@@ -1,6 +1,6 @@
 ---
 name: mstar-dispatch-gates
-description: Morning Star 派发与委派门禁 —— 仅 PM 可增派 subagent、`Execute as` 与 `Delegation`、承接方反递归 NEVER 红线、同条消息 N 次 invoke、QC 三审禁止串行 rollout、Assignment 文案≠派发（invoke 条数须对齐）、未齐不发（emit zero until batch-ready）。**必须**在 `@project-manager` 每轮派发、QC 三审并发、双轨 implement、或 leaf 角色疑惑能否 Task 时 Read；所有非 PM 承接方动手前必读反递归与自检。同仓 worktree 与 QC 检出对齐见 `mstar-branch-worktree`。Superpowers 并行短语见 `mstar-superpowers-align`。宿主细则见 `mstar-host`（`references/parallel-dispatch.md` 与各宿主 reference）。
+description: Morning Star 派发与委派门禁 —— 仅 PM 可增派 subagent、`Execute as` 与 `Delegation`、承接方反递归 NEVER 红线、同条消息 N 次 invoke、QC 三审禁止串行 rollout、Assignment 文案≠派发（invoke 条数须对齐）、未齐不发（emit zero until batch-ready）。**必须**在 `@project-manager` 每轮派发、QC 三审并发、双轨 implement、或 leaf 角色疑惑能否 Task 时 Read；所有非 PM 承接方动手前必读反递归与自检。同仓 worktree 与 QC 检出对齐见 `mstar-branch-worktree`。宿主细则见 `mstar-host`（`references/parallel-dispatch.md` 与各宿主 reference）。
 ---
 
 ## Load order（必读顺序）
@@ -14,7 +14,7 @@ description: Morning Star 派发与委派门禁 —— 仅 PM 可增派 subagent
 > **先回到你 Assignment 最顶部的 `**IDENTITY**` 块重读一遍** —— 那里已经告诉你：你是谁、你不是谁、Task 工具不属于你。本节是那个身份断言的加固版。
 
 **身份断言（牢记，不动摇）：**
-- **你就是** `Execute as` 写的那个角色。你**不是 PM**，不是调度者，不是 `dispatching-parallel-agents` 的使用者。
+- **你就是** `Execute as` 写的那个角色。你**不是 PM**，不是调度者，不是 parallel-agent dispatch 的使用者。
 - Task/subagent 工具即使在你的工具列表里出现，它**不属于你**。把它当作你没见过的工具 —— 不是"不能用"，是"你没有"。
 - 所有工作由你**本人**在当前会话内完成（Read / Write / Edit / Shell / Grep / Glob）。任何"这样做更高效"的想法都不构成 dispatch 的理由。
 - 遇到超出能力范围的需求 → 写 `## Blocked` 回报 PM，**不是**尝试 dispatch。Blocked 是你能发出的正确信号，dispatch 不是。
@@ -27,7 +27,7 @@ description: Morning Star 派发与委派门禁 —— 仅 PM 可增派 subagent
 - **NEVER** 把 Assignment 里出现的 **任何** `@<role>`、反引号 `` `<role-id>` ``、**Handoff**、**QA note**、**Completion Report** 模板里的角色名、路由表下游角色当成「立刻 invoke」的指令；这些是**叙事 / 路由文档 / 后续 PM 编排意图**，不是命令。
 - **NEVER** 把「分解为多个计划 / 多 phase / 多 track」等**设计产物层面**的并行或拆分读成「应 invoke 与子会话数量对应的多个 subagent」。**纸面产物**由本会话写盘完成；并行**调度**由 PM 在后续轮次决定。
 - **NEVER** 因宿主**暴露**了 `Task` 或若干 `subagent_type` 名称就推断可以调用。**工具可用 ≠ 授权使用**；授权只来自 **`Delegation: allowed (...)`**。
-- **NEVER**（非 PM）主动执行 `dispatching-parallel-agents` 来分派子代理；需要并行时回报 PM。
+- **NEVER**（非 PM）主动执行 parallel-agent dispatch 来分派子代理；需要并行时回报 PM。
 - **DO NOT** 在 Assignment 缺少 `Execute as` / `Delegation` / `Who runs this turn` 时自行「补齐」为 PM；缺字段时按 **leaf executor** 解释：亲自完成或 **`Blocked`**。
 - **DO NOT** 用「Assignment 太长 / 像编排稿」当作分派依据；先交付本会话任务再回报，分派由 PM 下一轮决定。
 
@@ -47,7 +47,7 @@ description: Morning Star 派发与委派门禁 —— 仅 PM 可增派 subagent
 - 额外代理仅以 **`Delegation: allowed (...)`** 为准；未显式写时视为 **`Delegation: forbidden`**。
 - Assignment 正文中的 `@xxx` 默认按「文本引用」解释，**不**视为自动调用命令。
 - 承接方若判断必须增加 subagent，应先回报 **`Blocked`** 请 PM 重分派。
-- **Superpowers `subagent-driven-development`**：per-task 子步**勿**用 `@qc-specialist*`；用 `@general` / `generalPurpose` 或 PM 标明的 informal `@qa-engineer`。详见 **`mstar-superpowers-align`**。
+- Per-task informal review, when PM explicitly allows it, must not use `@qc-specialist*`; use `@general` / `generalPurpose` or PM-marked informal `@qa-engineer`. Formal QC remains `mstar-review-qc`.
 
 ## 并发分派完整性门禁（PM 强制）
 
@@ -70,11 +70,20 @@ description: Morning Star 派发与委派门禁 —— 仅 PM 可增派 subagent
 - **QC 三审**在 feature 开发完成后执行；三名 reviewer 共用同一组 `Review cwd` / `Working branch` / `plan_id` / `Review range` / `Diff basis`（**`mstar-branch-worktree`**）。
 - **同一 plan 多 batch**：默认整 plan 交付完成跑一轮完整三审；**fix 后默认 targeted re-review**（N = 被指派的 QC 席位数，同条消息发满 N）；**仅** Assignment 写明 **`QC re-review: full tri-review`** 时复跑三审且用新文件名（**`mstar-plan-artifacts/references/plan-files-and-reports.md`**、**`mstar-review-qc`**）。
 
+## iteration-start Review & Edit chain
+
+与 QC 三审同理：**dispatch-first** 适用于文档审查角色，不限于 implement/QC。
+
+- PM 写 compass/plans **初稿**；**@product-manager**、**@architect**、**@writing-specialist** 各通过 Task **直接编辑** compass / plans / specs（**不**另写 `reports/` 审查报告）。
+- PM 线程跳过派发、自行完成三角色全部编辑 = **反模式**（见 **`mstar-harness-core`** 反模式索引、`mstar-iteration` §1.6）。
+- Steps 5.1–5.3 须 **Task**（可并行）；PM lock（5.4）在 PM 线程完成。**不得**在 review chain 完成前 commit integration 分支。
+
 ## 反模式（派发）
 
 - QC 三审拆在多条消息或等 #1 返回再发 #2/#3。
 - 仅 1 次 invoke 却声称「并行三审已启动」。
 - 递归同角色 subagent；把 Handoff / 多轨编排措辞当 invoke。
+- iteration-start 在 Review & Edit chain 完成前 commit；PM 代做三角色全部编辑而不派发 Task。
 
 ## References
 

package/harness-skills/mstar-dispatch-gates/references/leaf-executor-checklist.md

@@ -16,7 +16,7 @@ Before any Task/subagent call (if I somehow forget the preamble):
 4. Is `subagent_type` equal to my `Execute as`? If yes → **forbidden** (recursive dispatch).
 5. Am I treating `@roles`, Handoff, QA note, Completion Report roles, or multi-plan/multi-track **design text** as invoke commands? If yes → **stop**; deliver in-session.
 6. Am I invoking because the tool exists? **Available ≠ authorized.**
-7. Need parallel work or PM-only `dispatching-parallel-agents`? → **`Blocked`**; PM dispatches on the next round.
+7. Need parallel work or PM-only dispatch? → **`Blocked`**; PM dispatches on the next round.
 
 If blocked, report: `## Blocked — recursive dispatch refused (<which NEVER or reason>)`
 

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

@@ -33,7 +33,7 @@ description: Morning Star (启明星) harness **强制全局入口** —— 信
 | 角色 | 始终 | 按任务追加（典型） |
 |------|------|-------------------|
 | **全部** | 本 skill | — |
-| **`@project-manager`** | 本 skill | `mstar-dispatch-gates`、`mstar-phase-gates`、`mstar-plan-conventions`、`mstar-superpowers-align`、`mstar-roles`；派 QC 前 `mstar-review-qc`；并行/审查 `mstar-branch-worktree`；plan/status/reports `mstar-plan-artifacts`；UI 类 plan Prepare 阶段 `mstar-design-md`（DESIGN.md 门禁）；迭代管理 `mstar-iteration`（iteration-start/drive/close 含 compound）；战略性工作 `mstar-strategy`。**不**读 `mstar-coding-behavior` |
+| **`@project-manager`** | 本 skill | `mstar-dispatch-gates`、`mstar-phase-gates`、`mstar-plan-conventions`、`mstar-roles`；派 QC 前 `mstar-review-qc`；并行/审查 `mstar-branch-worktree`；plan/status/reports `mstar-plan-artifacts`；UI 类 plan Prepare 阶段 `mstar-design-md`（DESIGN.md 门禁）；新建/大改 skill 时 `mstar-skill-authoring`；迭代管理 `mstar-iteration`（iteration-start/drive/close 含 compound）；战略性工作 `mstar-strategy`。**不**读 `mstar-coding-behavior` |
 | **实现/审查/QA/运维** | 本 skill + `mstar-coding-behavior` + 角色 ref | 有 git 写：`mstar-branch-worktree`；有 plan 路径：`mstar-plan-conventions`（路径符号节）；QC/QA：`mstar-review-qc`；改 status/residual：`mstar-plan-artifacts`；UI 任务：`mstar-design-md`（读取 DESIGN.md tokens）；写入知识库 `{KNOWLEDGE_DIR}`：`mstar-compound`（PM 触发） |
 | **leaf 承接方** | 上栏 + **`mstar-dispatch-gates`**（反递归节） | — |
 
@@ -71,7 +71,7 @@ PM 在 Assignment 写 **`Task category`**（主类 + 可选 `secondary`）：
 
 ## 长任务纪律
 
-可追踪清单（plan `tasks` 或 Todo）；偏离时 PM 拉回；完成前须可核对证据（**`mstar-superpowers-align`** · `verification-before-completion`）。
+可追踪清单（plan `tasks` 或 Todo）；偏离时 PM 拉回；完成前须可核对证据（实现侧自检见 **`mstar-coding-behavior`**；门禁证据见 **`mstar-phase-gates`** / **`mstar-review-qc`**）。
 
 **Durable Roadmap Gate**：凡声明“分批 / 后续 / next plan / later / temporary workaround”的非热修任务，必须在 `{PLAN_DIR}` 主 plan、CreatePlan mirror、`status.json`/residual、或 PM Task Board 中写清后续路线（批次、依赖、owner/触发条件、完成定义）。只在对话或 Completion Report 里说“以后做”不算可追踪，不能进入 implement GO 或 Done。
 
@@ -88,11 +88,11 @@ PM 在 Assignment 写 **`Task category`**（主类 + 可选 `secondary`）：
 | `mstar-plan-artifacts` | 主 plan、reports、`status.json`、residual、knowledge、Done 归档 |
 | `mstar-design-md` | DESIGN.md 设计系统规范 —— 创建/审计/维护 design tokens，三级检查清单，light/dark 双主题 |
 | `mstar-review-qc` | QC 工作流、模板、verdict、residual 留档、deep review 透镜 |
-| `mstar-coding-behavior` | Think / Simplicity / Surgical / Debugging / Goal-Driven / Communication |
+| `mstar-coding-behavior` | Think / Simplicity / Surgical / Debugging / Review Feedback / Goal-Driven / Communication |
 | `mstar-compound` | 知识结晶 —— 已解决问题→结构化知识文档，双轨（Bug/Knowledge），「是否值得结晶」自检清单，重叠检测，可发现性检查，CONCEPTS.md 协同 |
 | `mstar-compound-refresh` | 知识维护 —— 审查/更新/合并/删除 `{KNOWLEDGE_DIR}` 文档 |
 | `mstar-strategy` | `STRATEGY.md` 全局战略方向 —— 产品愿景、技术方向、决策原则 |
-| `mstar-superpowers-align` | Superpowers × harness 优先级与短语 |
+| `mstar-skill-authoring` | mstar-native skill authoring: trigger contracts, progressive disclosure, pressure scenarios, behavior-change evidence |
 | `mstar-roles` | 角色正文 hub |
 | `mstar-host` | 宿主适配（自动识别；`references/opencode.md` / `cursor.md` / `codex.md` / `parallel-dispatch.md`） |
 
@@ -114,7 +114,7 @@ Read **`mstar-host`** after this skill; detect host per its table, then Read the
 - 业务仓默认功能分支（Assignment `Branch policy` 例外）→ **`mstar-branch-worktree`**。
 - **Dev 三角**：`@fullstack-dev` 后端主导；UI → `@frontend-dev`；第二轨 → `@fullstack-dev-2`（`mstar-roles` PM 节）。
 - 工期仅 agent-oriented → **`mstar-plan-conventions`** · effort-estimation。
-- `writing-plans` 落盘 `{PLAN_DIR}`，非 `docs/superpowers/plans/`。
+- plan-writing artifacts land in `{PLAN_DIR}`, not external default plan directories.
 - PM Assignment 键名英文；任务正文可中文；产出/报告默认英文。
 
 ## 库文档（Context7）
@@ -139,6 +139,9 @@ Read **`mstar-host`** after this skill; detect host per its table, then Read the
 | 无证据宣称完成 | `mstar-coding-behavior` / verification |
 | CreatePlan 不落盘 / 无 `{HARNESS_DIR}` mirror | `mstar-host` · `cursor-plan-mode-bridge` |
 | 临时方案 / 后续计划只写在对话里 | `mstar-phase-gates` · Durable Roadmap Gate |
+| iteration-start commit before review chain | `mstar-iteration` §1.6；PM 模拟三角色编辑而不派发 Task |
+| Phase 3 折叠进 final plan closure / 跳过 §3.1 gate | `mstar-iteration` §3.0–§3.5；`iteration-drive` Phase 3 |
+| iteration-close 无 frontmatter completed / 漏 compound Phase 6 | `mstar-iteration` §3.0.5、§3.4、§3.2 #5 |
 
 ## 可选：OpenViking Memory
 

package/harness-skills/mstar-harness-core/references/open-harness-principles.md

@@ -13,9 +13,9 @@
 | **`clarify` 核心纪律** | 逐方面核对至共享理解；沿设计决策树逐枝、一次一决；能探索代码库则先探索；每问带推荐答案 | **`mstar-phase-gates`** SKILL.md（含 Phase Gate Playbook） |
 | **按任务类别选能力与模型** | 视觉/深读/快改/硬逻辑等用不同强项 | `mstar-harness-core` SKILL.md「Task category」；Assignment 字段 **`Task category`**；宿主侧按角色配置 model（如 OpenCode 的 `opencode.json`） |
 | **可验证编辑** | 减少「凭记忆 Patch」导致的漂移与损坏 | `mstar-phase-gates` SKILL.md「可验证编辑与上下文纪律」：读后再改、失败则重读 |
-| **持续推进与可核对完成** | 长任务有清单、有关门证据，避免空转 | `mstar-superpowers-align` 的 `verification-before-completion`；PM 对 `tasks`/Phase Gate 的拉回 |
+| **持续推进与可核对完成** | 长任务有清单、有关门证据，避免空转 | `mstar-phase-gates` / `mstar-review-qc`；实现侧自检见 `mstar-coding-behavior` |
 | **编码行为约束（轻量）** | 降低静默假设、过度设计与无关改动 | `mstar-coding-behavior`：Think Before Coding / Simplicity First / Surgical Changes / Goal-Driven Execution |
-| **并行与边界** | 多线任务不踩同一写归属、不绕过分支门禁；**开发**阶段同仓多可写并发须独立 **`git worktree`**；**QC / QA** 在 **同一检出**（`Review cwd`）与 **同一 `plan_id` + `Review range` / `Diff basis`** 上审查与验证，保证三票同一功能 | `mstar-branch-worktree`；`mstar-review-qc`；`mstar-superpowers-align` **`using-git-worktrees`** |
+| **并行与边界** | 多线任务不踩同一写归属、不绕过分支门禁；**开发**阶段同仓多可写并发须独立 **`git worktree`**；**QC / QA** 在 **同一检出**（`Review cwd`）与 **同一 `plan_id` + `Review range` / `Diff basis`** 上审查与验证，保证三票同一功能 | `mstar-branch-worktree`；`mstar-review-qc`；`mstar-dispatch-gates` |
 | **分层上下文（可选）** | 大仓库用目录级 `AGENTS.md` 降噪；根 `AGENTS.md` 维护边界见下文专节 | `mstar-harness-core` SKILL.md「分层上下文」；由业务项目维护者按需添加 |
 | **结构化澄清（按宿主）** | 向用户澄清/抉择时，**有 `question` 类能力则优先**；否则结构化正文；长问兜底 | `mstar-phase-gates` SKILL.md Prepare · `clarify`；当前宿主的 `mstar-host` skill；`mstar-roles` · `project-manager` |
 
@@ -71,6 +71,6 @@
 ## 延伸阅读
 
 - 按能力选配 MCP/skills：OpenCode → `mstar-host` `references/opencode.md`；其它宿主见 `mstar-host` 检测表
-- Superpowers 与门禁对齐：`mstar-superpowers-align`
+- Evidence and checkpoints: `mstar-phase-gates` / `mstar-review-qc`; implementation self-checks: `mstar-coding-behavior`
 - 库文档检索共享协议：`mstar-harness-core` `references/library-docs-protocol.md`
 - 跨角色编码行为准则（轻量、可复用）：`mstar-coding-behavior`

package/harness-skills/mstar-host/references/cursor-plan-mode-bridge.md

@@ -197,7 +197,7 @@ When `/pm` runs under Plan mode:
 
 ## Related skills
 
-- `mstar-plan-conventions` — discovery, init, `writing-plans` path gate
+- `mstar-plan-conventions` — discovery, init, plan-writing path gate
 - `mstar-plan-artifacts` — `status.json`, reports, checkboxes, residual
 - `mstar-phase-gates` — Prepare / Execute order
 - `mstar-roles/references/project-manager/dispatch-and-assignment.md` — Checkpoint: commit → Completion Report → Status Update

package/harness-skills/mstar-host/references/cursor.md

@@ -61,9 +61,9 @@ Enforcement: `rules/mstar-cursor-plan-mode.mdc` when plugin active.
 - No `question` tool: structured Markdown or Cursor UI.
 - “Question asked” ≠ clarify done; high-impact ambiguity → `Blocked` or escalation.
 
-## Superpowers
+## Execution Discipline
 
-If no Skill invocation tool: `mstar-superpowers-align` “plugin not installed”; **Read** upstream `SKILL.md` before execution.
+Implementation roles use `mstar-coding-behavior` for RCA, test-first checks, review feedback, and completion evidence. Plan checkpoints remain in `mstar-phase-gates`; external skill plugins are not required.
 
 ## Gotchas
 

package/harness-skills/mstar-host/references/opencode.md

@@ -8,7 +8,7 @@ Parallel PM dispatch: **`parallel-dispatch.md`** (read in dispatch rounds).
 
 - **Role shell**: `agents/<id>.md` referenced by `opencode.json` `agent.<id>` (frontmatter + role binding only).
 - **Role body**: `mstar-roles` `references/<id>.md` (or shared references + parameters).
-- Superpowers conflicts: `mstar-superpowers-align`.
+- Implementation evidence and RCA behavior: `mstar-coding-behavior`.
 
 ## OpenCode-specific capabilities
 
@@ -48,7 +48,7 @@ Aligned with `mstar-harness-core` `references/open-harness-principles.md`. Editi
 | **Repo graph** | Impact / PR risk | e.g. GitNexus |
 | **Browser / E2E** | Observable QA evidence | agent-browser, Playwright |
 | **Git workflow** | Atomic commits, branch closure | git-commit, finishing-a-development-branch |
-| **Systematic debugging** | RCA before fix | `mstar-superpowers-align` |
+| **Systematic debugging** | RCA before fix | `mstar-coding-behavior` |
 | **OpenViking memory** | Long-term memory tools | Only if `memsearch` present; `openviking-memory-plugin.md` |
 
 **Not recommended**: overlapping search MCPs; extra tools to mask missing harness baseline.