@mstar-harness/opencode 3.2.5 → 3.3.0

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

@@ -105,7 +105,7 @@ PM 在 Assignment 写 **`Task category`**（主类 + 可选 `secondary`）：
 | `mstar-compound-refresh` | 知识维护 —— 审查/更新/合并/删除 `{KNOWLEDGE_DIR}` 文档；**项目知识 bootstrap**（无/残旧 STRATEGY.md、CONCEPTS.md、`{KNOWLEDGE_DIR}`）→ `references/project-knowledge-bootstrap.md` |
 | `mstar-strategy` | `STRATEGY.md` 全局战略方向 —— 产品愿景、技术方向、决策原则 |
 | `mstar-skill-authoring` | 通用 skill 撰写门控（SkillsBench 六原则）：trigger 契约、紧凑 5 问 body、渐进披露、paired 证据 |
-| `mstar-audit` | Variant carrier：common core（hard rules、recon、vet、variant dispatch）+ SKILL.md `## Plan output (all variants)`（Status block、plan files、handoff）+ `references/codebase-audit.md`（full-audit 变体：9 类别 fan-out、effort、scope variants、Phase 4 excerpt/reconcile、audit index 模板）+ `references/pr-review.md`（`pr` 变体）；`audit-playbook` + `finding-format` + `plan-quality-bar` |
+| `mstar-audit` | Variant carrier：common core（hard rules、recon、vet、variant dispatch）+ SKILL.md `## Plan output (all variants)`（Status block、plan files、handoff）+ `references/codebase-audit.md`（full-audit 变体：9 类别 fan-out、effort、scope variants、Phase 4 excerpt/reconcile、audit index 模板）+ `references/security-review.md`（security 深查：exploitability 门槛、FP 纪律、LLM/供应链面）+ `references/pr-review.md`（`pr` 变体）；`audit-playbook` + `finding-format` + `plan-quality-bar` |
 | `mstar-roles` | 角色正文 hub |
 | `mstar-host` | 宿主适配（自动识别；`references/opencode.md` / `cursor.md` / `codex.md` / `kimi.md` / `parallel-dispatch.md`） |
 

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

@@ -1,19 +1,20 @@
 ---
 name: mstar-roles
-description: Morning Star role prompt hub — `agents/*.md` shells plus full behavior in `references/*.md`, each with a **Required Skill Dependencies** list (which `mstar-*` topic skills to load after `mstar-harness-core`). Always load for any Morning Star role (`project-manager`, `product-manager`, `architect`, `code-reviewer`, `fullstack-dev`, `fullstack-dev-2`, `frontend-dev`, `qa-engineer`, `qc-specialist*`, `ops-engineer`, `writing-specialist`, `prompt-engineer`). Cross-role **Role → typical topic skills** summary in this SKILL.md; per-role lists in `references/*.md` are authoritative for that role's session. Full topic skill index → **`mstar-harness-core`**.
+description: Morning Star role prompt hub — `agents/*.md` shells plus full behavior in `references/*.md`. Role files are **identity-first** (mission / responsibilities / NEVER rules); topic `mstar-*` skills appear only as **PM-activated skill presets** (Assignment `Skill presets:` field), not default dependencies. Always load for any Morning Star role (`project-manager`, `product-manager`, `architect`, `code-reviewer`, `fullstack-dev`, `fullstack-dev-2`, `frontend-dev`, `qa-engineer`, `qc-specialist*`, `ops-engineer`, `writing-specialist`, `prompt-engineer`). Cross-role **Role → skill presets** summary in this SKILL.md; per-role preset menus in `references/*.md` are authoritative once PM activates them. Full topic skill index → **`mstar-harness-core`**.
 ---
 
-## Load Order (Required)
+## Load Order
 
 When a Morning Star role starts work in a session:
 
-1. Read `mstar-harness-core` first (SKILL.md), then **only** the topic `mstar-*` skills required for this role/task (see matrix below — do not read all topic skills by default).
-2. Read this `mstar-roles` skill.
-3. Resolve role mapping and parameter table below.
-4. Read the corresponding `references/<role>.md` file — each role file lists **Required Skill Dependencies** for that role (canonical per-role load list).
-5. Expand placeholders from role parameters before execution.
+1. Read this `mstar-roles` skill; resolve role mapping and parameter tables below.
+2. Read the corresponding `references/<role>.md` file — **identity-first**: mission, scope, and NEVER rules come before any skill list.
+3. Load topic skills per the Assignment **`Skill presets:`** field, following that role's **Skill Preset (PM-Activated)** section. Omitted on an implementation / QC / QA round ⇒ the role's `standard` preset applies by default; explicit `Skill presets: none` (or a trivial route) ⇒ execute from identity + assignment alone without topic skills. Whenever `mstar-harness-core` is loaded, it remains the global entry (state machine, gates, routing).
+4. Expand placeholders from role parameters before execution.
 
-If any conflict appears, `mstar-harness-core` remains the authoritative source for lifecycle, gates, routing, and invariants. The table below is the cross-role summary; when a role file lists different **on-demand** skills, follow the role file for that session.
+If any conflict appears, `mstar-harness-core` remains the authoritative source for lifecycle, gates, routing, and invariants. The table below summarizes each role's preset menu; when a role file's preset section differs, follow the role file for that session.
+
+Exception: `project-manager` is the core orchestrator and keeps **required reading** (not a preset) — see `references/project-manager.md`.
 
 ## Role Reference Mapping
 
@@ -34,14 +35,16 @@ If any conflict appears, `mstar-harness-core` remains the authoritative source f
 | `writing-specialist` | `references/writing-specialist.md` | — |
 | `prompt-engineer` | `references/prompt-engineer.md` | — |
 
-### Role → typical topic skills (after `mstar-harness-core`)
+### Role → skill presets (PM-activated)
+
+PM-owned activation with a safe default: omitted `Skill presets:` on an implementation / QC / QA round means `standard`; explicit `none` runs identity-only. Rows summarize each role's preset menu — role-owned files (e.g. `references/qc-specialist/`, `references/qa-engineer/acceptance-gate.md`) are excluded; they always load with the reference.
 
-| Role | Typical adds |
+| Role | Preset menu |
 | --- | --- |
 | `project-manager` | `mstar-dispatch-gates`, `mstar-phase-gates`, `mstar-conventions`, `mstar-roles` ref; + `references/project-manager/qa-trigger-matrix.md` for QA gate tiers; + `mstar-review-qc` before QC; + `mstar-branch-worktree` / `mstar-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-conventions` (minimal); `mstar-design-md` when implementing styled UI |
-| `qc-specialist*` | `mstar-branch-worktree`, `mstar-artifacts` (review bundle paths); `references/qc-specialist/` (workflow, checklist, template, lenses); `mstar-design-md` when reviewing UI |
-| `qa-engineer` | `mstar-branch-worktree`, `mstar-artifacts` (closing R#); `references/qa-engineer/acceptance-gate.md`; `mstar-design-md` when verifying visual output |
+| `qc-specialist*` | Presets: `mstar-branch-worktree`, `mstar-artifacts` (review bundle paths); `mstar-design-md` when reviewing UI. Role-owned (never gated): `references/qc-specialist/` workflow/checklist/template (+ lenses on demand) |
+| `qa-engineer` | Presets: `mstar-branch-worktree`, `mstar-artifacts` (closing R#); `mstar-design-md` when verifying visual output. Role-owned (never gated): `references/qa-engineer/acceptance-gate.md` |
 | `architect`, `product-manager` | `mstar-phase-gates` (Prepare), `mstar-artifacts` (knowledge/specs); `mstar-design-md` (creator + design intent); `mstar-strategy` (STRATEGY.md creation/maintenance) |
 | `code-reviewer` | `mstar-sdd` (per-task review mode); `mstar-audit` (audit mode: full workflow); `mstar-conventions` (paths); `mstar-artifacts` (plan-quality-bar for audit plans) |
 | `ops-engineer` | `mstar-coding-behavior`, `mstar-branch-worktree` |
@@ -83,11 +86,12 @@ PM consolidated (tri mode): `{SDD_DIR}/review/qc-consolidated.md` (same folder;
 - Edit behavior in `references/*.md`.
 - Edit role family parameters in this file.
 - Keep shared-family roles (`fullstack-dev*`, `qc-specialist*`) on one shared reference file.
+- Role references stay **identity-first**: mission / responsibilities / NEVER rules before any skill list; topic-skill loads live only in the **Skill Preset (PM-Activated)** section.
 - Add new roles by updating mapping, parameters (if needed), and adding corresponding `agents/*.md` shell.
 
 ## Workflow
 
-加载顺序：Read `mstar-harness-core` → Read 本 skill（角色映射 + 参数表）→ 解析对应 `references/<role>.md` → 展开角色参数（`role_id` / `track` / `reviewer_index` 等）→ 按该角色文件的 Required Skill Dependencies 追加加载 → 执行。映射 / 参数表与磁盘 `references/*.md` 布局不符时先修再继续。
+加载顺序：Read 本 skill（角色映射 + 参数表）→ 解析对应 `references/<role>.md`（身份优先：mission / NEVER / responsibilities 在前）→ 按 Assignment 的 `Skill presets:` 字段加载专题 skill：实质轮次（implementation / QC / QA）缺省即默认该角色的 `standard` 预设；显式 `none`（或 trivial 路由）则以身份 + Assignment 执行。映射 / 参数表与磁盘 `references/*.md` 布局不符时先修再继续。
 
 ## Evidence
 

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

@@ -1,14 +1,3 @@
-## Required Skill Dependencies
-
-**Hub matrix:** `mstar-roles` SKILL.md.
-
-**Always:** `mstar-harness-core`, `mstar-dispatch-gates`, `mstar-phase-gates` (Prepare: specify/clarify/plan), `mstar-conventions` (`{PLAN_DIR}`, plan-writing path).
-
-**Typically:** `mstar-artifacts` (specs, **`{ITERATION_DIR}/<id>/` package**); `mstar-coding-behavior`. Boundaries → **`mstar-iteration/references/iteration-artifact-boundaries.md`**.
-
-**On demand:** `mstar-branch-worktree` (when committing architecture docs to the business repo); `mstar-design-md` (when the plan involves UI work / design tokens — read DESIGN.md for design specs).
-
-**Host:** `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`).
 
 ## Role Mission
 
@@ -102,6 +91,15 @@ Do not create your own branch strategy.
 ## Effort (agent-oriented)
 ```
 
+## Skill Preset (PM-Activated)
+
+Topic skills below are **presets activated by PM**, not unconditional role dependencies — the identity, responsibilities, and NEVER rules above stand alone. Loading follows the Assignment **`Skill presets:`** field: omitted on an implementation / QC / QA round ⇒ the `standard` preset below applies by default; explicit `Skill presets: none` (or a trivial route) ⇒ work from identity + assignment and do not self-load topic skills. When active, load in order (**hub matrix:** `mstar-roles` SKILL.md):
+
+1. `mstar-harness-core` → `mstar-dispatch-gates` → `mstar-phase-gates` (Prepare: specify/clarify/plan) → `mstar-conventions` (`{PLAN_DIR}`, plan-writing path)
+2. Typically: `mstar-artifacts` (specs, **`{ITERATION_DIR}/<id>/` package**); `mstar-coding-behavior`. Boundaries → **`mstar-iteration/references/iteration-artifact-boundaries.md`**
+3. On demand: `mstar-branch-worktree` (committing architecture docs to the business repo); `mstar-design-md` (plan involves UI work / design tokens — read DESIGN.md for design specs)
+4. Host: `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`)
+
 ## Completion Report
 
 Template (`{role_id}` = `architect`) → **`references/_shared/leaf-executor-core.md`**「Completion Report」。

package/harness-skills/mstar-roles/references/code-reviewer.md

@@ -2,21 +2,6 @@
 
 Read-only review/assessment seat with three modes: **Mode A — SDD task reviewer (default, L2)**, **Mode B — audit executor (`Task category: audit`)**, and **Mode C — PR review (`pr` variant)**.
 
-## Required Skill Dependencies
-
-**Hub matrix:** `mstar-roles` SKILL.md.
-
-**Always:** `mstar-harness-core` (mandatory entry), `mstar-dispatch-gates` (leaf anti-recursion).
-
-**By mode:**
-
-- Mode A (SDD task reviewer): `mstar-sdd` → `references/task-reviewer-prompt.md`, `references/file-handoffs.md`
-- Mode B (audit executor): `mstar-audit` SKILL.md (common core) + `references/codebase-audit.md` (full-audit variant detail)
-- Mode C (PR review): `mstar-audit` SKILL.md (common core) + `references/pr-review.md` (`pr` variant detail) + `mstar-branch-worktree` (worktree isolation)
-
-**Paths:** `mstar-conventions`; add `mstar-artifacts` (plan-quality-bar) when writing audit plans.
-
-**Host:** `mstar-host` (detect; active host reference).
 
 ## Role Mission
 
@@ -112,6 +97,18 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 - Preferred: read-only review reports (Mode A) and audit plans (Mode B) in the paths above
 - Do not own: implementation (L1), formal QC gates (L3), acceptance / re-run verification (L4)
 
+## Skill Preset (PM-Activated)
+
+Topic skills below are **presets activated by PM**, not unconditional role dependencies — the identity, mode definitions, and NEVER rules above stand alone. Loading follows the Assignment **`Skill presets:`** field (the assigned **mode** selects the mode preset): omitted on an implementation / review round ⇒ the `standard` preset below applies by default; explicit `Skill presets: none` (or a trivial route) ⇒ work from identity + assignment and do not self-load topic skills. When active, load in order (**hub matrix:** `mstar-roles` SKILL.md):
+
+1. `mstar-harness-core` (mandatory entry) → `mstar-dispatch-gates` (leaf anti-recursion)
+2. By mode:
+   - Mode A (SDD task reviewer): `mstar-sdd` → `references/task-reviewer-prompt.md`, `references/file-handoffs.md`
+   - Mode B (audit executor): `mstar-audit` SKILL.md (common core) + `references/codebase-audit.md`
+   - Mode C (PR review): `mstar-audit` SKILL.md + `references/pr-review.md` + `mstar-branch-worktree` (worktree isolation)
+3. Paths: `mstar-conventions`; add `mstar-artifacts` (plan-quality-bar) when writing audit plans
+4. Host: `mstar-host` (detect; active host reference)
+
 ## Completion Report
 
 Template (`{role_id}` = `code-reviewer`) → **`references/_shared/leaf-executor-core.md`**「Completion Report」.

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

@@ -1,14 +1,3 @@
-## Required Skill Dependencies
-
-**Hub matrix:** `mstar-roles` SKILL.md.
-
-**Always:** `mstar-harness-core`, `mstar-coding-behavior`, `mstar-dispatch-gates`.
-
-**Typically:** `mstar-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).
-
-**Host:** `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`).
 
 ## Role Mission
 
@@ -62,6 +51,15 @@ If plan drift appears during implementation, request plan write-back before cont
 - Same-repo concurrent writes require worktree isolation
 - Do not self-decide branch pivots to default branch
 
+## Skill Preset (PM-Activated)
+
+Topic skills below are **presets activated by PM**, not unconditional role dependencies — the identity, responsibilities, and NEVER rules above stand alone. Loading follows the Assignment **`Skill presets:`** field: omitted on an implementation / QC / QA round ⇒ the `standard` preset below applies by default; explicit `Skill presets: none` (or a trivial route) ⇒ work from identity + assignment and do not self-load topic skills. When active, load in order (**hub matrix:** `mstar-roles` SKILL.md):
+
+1. `mstar-harness-core` → `mstar-coding-behavior` → `mstar-dispatch-gates`
+2. Typically: `mstar-conventions` (paths + spec metadata)
+3. On demand: `mstar-branch-worktree` (repo writes); `mstar-phase-gates` (Execute / hotfix when referenced in assignment); `mstar-design-md` (styled UI — read DESIGN.md tokens before writing components)
+4. Host: `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`)
+
 ## Completion Report
 
 Template (`{role_id}` = `frontend-dev`) → **`references/_shared/leaf-executor-core.md`**「Completion Report」。

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

@@ -8,17 +8,6 @@ Behavior is shared; track identity is parameterized.
 - `{role_id}`: `fullstack-dev` or `fullstack-dev-2`
 - `{track}`: `primary` or `parallel_secondary`
 
-## Required Skill Dependencies
-
-**Hub matrix:** `mstar-roles` SKILL.md.
-
-**Always:** `mstar-harness-core`, `mstar-coding-behavior`, `mstar-dispatch-gates` (leaf anti-recursion before any Task/subagent).
-
-**Typically:** `mstar-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).
-
-**Host:** `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`).
 
 ## Role Mission
 
@@ -81,6 +70,15 @@ If plan drift appears, request plan update before continuing.
 3. Test implementation for assigned scope
 4. Self-verification and evidence generation
 
+## Skill Preset (PM-Activated)
+
+Topic skills below are **presets activated by PM**, not unconditional role dependencies — the identity, responsibilities, and NEVER rules above stand alone. Loading follows the Assignment **`Skill presets:`** field: omitted on an implementation / QC / QA round ⇒ the `standard` preset below applies by default; explicit `Skill presets: none` (or a trivial route) ⇒ work from identity + assignment and do not self-load topic skills. When active, load in order (**hub matrix:** `mstar-roles` SKILL.md):
+
+1. `mstar-harness-core` → `mstar-coding-behavior` → `mstar-dispatch-gates` (leaf anti-recursion before any Task/subagent)
+2. Typically: `mstar-conventions` (path symbols + `metadata.primary_spec` / `spec_refs`)
+3. 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` (task includes UI implementation — read DESIGN.md for design tokens)
+4. Host: `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`)
+
 ## Completion Report
 
 Template (fill `{role_id}` = `{role_id}`) → **`references/_shared/leaf-executor-core.md`**「Completion Report」。

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

@@ -1,14 +1,3 @@
-## Required Skill Dependencies
-
-**Hub matrix:** `mstar-roles` SKILL.md.
-
-**Always:** `mstar-harness-core`, `mstar-coding-behavior`, `mstar-dispatch-gates`, `mstar-branch-worktree` (repo writes, production-touching branches).
-
-**Typically:** `mstar-conventions` (paths).
-
-**On demand:** `mstar-phase-gates` (hotfix compressed path when assignment says hotfix).
-
-**Host:** `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`).
 
 ## Role Mission
 
@@ -65,6 +54,15 @@ When assignment is marked `high-risk`:
 ## Monitoring Checks
 ```
 
+## Skill Preset (PM-Activated)
+
+Topic skills below are **presets activated by PM**, not unconditional role dependencies — the identity, responsibilities, and NEVER rules above stand alone. Loading follows the Assignment **`Skill presets:`** field: omitted on an implementation / QC / QA round ⇒ the `standard` preset below applies by default; explicit `Skill presets: none` (or a trivial route) ⇒ work from identity + assignment and do not self-load topic skills. When active, load in order (**hub matrix:** `mstar-roles` SKILL.md):
+
+1. `mstar-harness-core` → `mstar-coding-behavior` → `mstar-dispatch-gates` → `mstar-branch-worktree` (repo writes, production-touching branches)
+2. Typically: `mstar-conventions` (paths)
+3. On demand: `mstar-phase-gates` (hotfix compressed path when assignment says hotfix)
+4. Host: `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`)
+
 ## Completion Report
 
 Template (`{role_id}` = `ops-engineer`) → **`references/_shared/leaf-executor-core.md`**「Completion Report」。

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

@@ -1,14 +1,3 @@
-## Required Skill Dependencies
-
-**Hub matrix:** `mstar-roles` SKILL.md.
-
-**Always:** `mstar-harness-core`, `mstar-dispatch-gates`, `mstar-phase-gates` (Prepare / clarify), `mstar-conventions` (`{PLAN_DIR}`, plan-writing path).
-
-**Typically:** `mstar-artifacts` (specs, **`{ITERATION_DIR}/<id>/` package** — not knowledge @ start); `mstar-coding-behavior`. Boundaries → **`mstar-iteration/references/iteration-artifact-boundaries.md`**.
-
-**On demand:** `mstar-branch-worktree` (when committing product docs to the business repo); `mstar-design-md` (when the plan involves UI work / design tokens — read DESIGN.md for design specs).
-
-**Host:** `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`).
 
 ## Role Mission
 
@@ -95,6 +84,15 @@ If writing files to business repo, use only PM-assigned `Working branch` / `Bran
 
 - **NEVER** embed human calendar estimates (person-days, FTE, “waiting for review X days”) inside **Effort (agent-oriented)** fields; keep agent-only sizing per `mstar-conventions` `references/effort-estimation.md`.
 
+## Skill Preset (PM-Activated)
+
+Topic skills below are **presets activated by PM**, not unconditional role dependencies — the identity, responsibilities, and NEVER rules above stand alone. Loading follows the Assignment **`Skill presets:`** field: omitted on an implementation / QC / QA round ⇒ the `standard` preset below applies by default; explicit `Skill presets: none` (or a trivial route) ⇒ work from identity + assignment and do not self-load topic skills. When active, load in order (**hub matrix:** `mstar-roles` SKILL.md):
+
+1. `mstar-harness-core` → `mstar-dispatch-gates` → `mstar-phase-gates` (Prepare / clarify) → `mstar-conventions` (`{PLAN_DIR}`, plan-writing path)
+2. Typically: `mstar-artifacts` (specs, **`{ITERATION_DIR}/<id>/` package** — not knowledge @ start); `mstar-coding-behavior`. Boundaries → **`mstar-iteration/references/iteration-artifact-boundaries.md`**
+3. On demand: `mstar-branch-worktree` (committing product docs to the business repo); `mstar-design-md` (plan involves UI work / design tokens — read DESIGN.md for design specs)
+4. Host: `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`)
+
 ## Completion Report
 
 Template (`{role_id}` = `product-manager`) → **`references/_shared/leaf-executor-core.md`**「Completion Report」。

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

@@ -10,6 +10,7 @@ The concise gate summary remains in `references/project-manager.md`.
 - In tool hosts (OpenCode / Cursor Task / Codex with callable multi-agent tools), Markdown-only Assignment is not dispatch.
 - For parallel batch with `N >= 2`, dispatch turn must emit all `N` invokes in one message when host supports it.
 - **Same-repo writable parallel tracks**: tool concurrency and worktree isolation are **separate gates**. Before implement invokes, complete **`mstar-branch-worktree`** → **`references/parallel-writable-pre-dispatch.md`**.
+- **Skill preset activation is PM-owned**: topic skills are presets in each role's `Skill Preset (PM-Activated)` section (`mstar-roles/references/<role>.md`), not self-loaded defaults. Omitting the `Skill presets:` field applies its documented default (`standard` on implementation / QC / QA rounds); identity-only execution requires explicit `Skill presets: none`.
 
 ## Executor Anti-Recursion Rules
 
@@ -77,6 +78,7 @@ The **`**You are a leaf executor. You MUST NOT:**`** section (previously just pr
 **SDD implementer session**: fresh | sticky | N/A — **default `fresh`**; `sticky` reuses same implementer subagent across tasks (reviewers stay fresh). See `mstar-sdd/references/sticky-implementer-session.md`
 **SDD dir**: absolute `<control_worktree_path>/{HARNESS_DIR}/sdd/<plan-id>/` when L1 lease gate active | `{HARNESS_DIR}/sdd/<plan-id>/` when waived / single checkout | N/A
 **Model tier**: fast | standard | capable | N/A
+**Skill presets**: `standard` | <explicit skill list> | none — activates the `Execute as` role's preset from its `Skill Preset (PM-Activated)` section; default `standard` for implementation / QC / QA rounds unless the route is trivial
 **QC mode**: full tri-review | single | N/A — **default `full tri-review` when `Execution mode: sdd`**; `single` only for `inline` / override
 **Review package path**: <branch-review diff file> | N/A
 **Who runs this turn (executor lock)**: only `Execute as` role for this message

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

@@ -1,16 +1,3 @@
-## Required Skill Dependencies
-
-**Hub matrix:** `mstar-roles` SKILL.md.
-
-**Always:** `mstar-harness-core`, `mstar-dispatch-gates`.
-
-**When editing harness text:** read **all** topic skills you touch — at minimum `mstar-phase-gates`, `mstar-conventions`, `mstar-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-conventions` (path symbols in examples).
-
-**Host:** `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`).
 
 ## Role Mission
 
@@ -59,6 +46,16 @@ When creating a new skill, making a major skill rewrite, changing frontmatter `d
 - Redundancy removed before adding new constraints
 - At least one replayable scenario exists for regression check
 
+## Skill Preset (PM-Activated)
+
+Topic skills below are **presets activated by PM**, not unconditional role dependencies — the identity, responsibilities, and NEVER rules above stand alone. Loading follows the Assignment **`Skill presets:`** field: omitted on an implementation / QC / QA round ⇒ the `standard` preset below applies by default; explicit `Skill presets: none` (or a trivial route) ⇒ work from identity + assignment and do not self-load topic skills. When active, load in order (**hub matrix:** `mstar-roles` SKILL.md):
+
+1. `mstar-harness-core` → `mstar-dispatch-gates`
+2. Harness-text editing trigger (activation implies): read **all** topic skills you touch — at minimum `mstar-phase-gates`, `mstar-conventions`, `mstar-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
+3. New skill / major skill rewrite / trigger-description change (activation implies): MUST read `mstar-skill-authoring` before editing
+4. Typically: `mstar-conventions` (path symbols in examples)
+5. Host: `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`)
+
 ## Completion Report
 
 Template (`{role_id}` = `prompt-engineer`) → **`references/_shared/leaf-executor-core.md`**「Completion Report」。

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

@@ -1,15 +1,3 @@
-## Morning Star Skills (Required Reading)
-
-Before any non-trivial QA assignment, read in order:
-
-1. `mstar-harness-core` (entry, state machine, Done authority)
-2. `mstar-coding-behavior` (verification discipline)
-3. `mstar-dispatch-gates` + `mstar-branch-worktree` (anti-recursion; checkout alignment with QC)
-4. Host adapter: `mstar-host` (detect; Read `references/opencode.md`, `cursor.md`, or `codex.md`)
-5. **`references/qa-engineer/acceptance-gate.md`** (L4 execution)
-6. **On demand:** `mstar-artifacts` (closing R#); `mstar-conventions` (paths); `mstar-design-md` (UI verify against DESIGN.md); `mstar-phase-gates` (when Assignment references verification phase); review bundle files and QC consolidated inputs named in Assignment
-
-Full cross-role matrix: `mstar-roles` SKILL.md.
 
 This file is a compact QA role shell.
 Detailed L4 procedures: `references/qa-engineer/*.md`.
@@ -61,6 +49,14 @@ When Assignment provides a report path, write report-only output under `{SDD_DIR
 ## Recommended owners
 ```
 
+## Skill Preset (PM-Activated)
+
+External topic skills below are **presets activated by PM**, not unconditional role dependencies — the L4 acceptance identity and NEVER rules above stand alone, and role-owned `references/qa-engineer/acceptance-gate.md` is always part of this role (never preset-gated). Loading follows the Assignment **`Skill presets:`** field: omitted on an implementation / QC / QA round ⇒ the `standard` preset below applies by default; explicit `Skill presets: none` (or a trivial route) ⇒ work from identity + assignment and do not self-load topic skills. When active, load in order (**hub matrix:** `mstar-roles` SKILL.md):
+
+1. `mstar-harness-core` → `mstar-coding-behavior` → `mstar-dispatch-gates` + `mstar-branch-worktree` (anti-recursion; checkout alignment with QC)
+2. Host adapter: `mstar-host` (detect; Read `references/opencode.md`, `cursor.md`, or `codex.md`)
+3. On demand: `mstar-artifacts` (closing R#); `mstar-conventions` (paths); `mstar-design-md` (UI verify against DESIGN.md); `mstar-phase-gates` (Assignment references verification phase); review bundle files and QC consolidated inputs named in Assignment
+
 ## Completion Report
 
 Template (`{role_id}` = `qa-engineer`) → **`references/_shared/leaf-executor-core.md`**「Completion Report」。

package/harness-skills/mstar-roles/references/qc-specialist-shared.md

@@ -10,23 +10,6 @@ Behavior is shared; reviewer identity is parameterized.
 - `{focus}`
 - `{report_suffix}`
 
-## Required Skill Dependencies
-
-**Hub matrix:** `mstar-roles` SKILL.md.
-
-Before any non-trivial QC assignment, read in order:
-
-1. `mstar-harness-core`
-2. `mstar-dispatch-gates` + `mstar-branch-worktree`
-3. `mstar-artifacts` (review bundle paths and naming)
-4. Host: `mstar-host` → active host reference
-5. **`references/qc-specialist/reviewer-workflow.md`**
-6. **`references/qc-specialist/reviewer-checklist.md`**
-7. **`references/qc-specialist/report-template.md`**
-8. **On demand:** `references/qc-specialist/deep-review-lenses.md`; `mstar-conventions` (paths); `mstar-design-md` (UI vs DESIGN.md)
-
-This file is a compact QC reviewer shell.
-Detailed execution: `references/qc-specialist/*.md`.
 
 ## Role Mission
 
@@ -106,6 +89,16 @@ generated_at: "YYYY-MM-DD"
 Verdict enumeration and rules (incl. `Unconfirmed` semantics) → **`references/qc-specialist/report-template.md`**.
 ```
 
+## Skill Preset (PM-Activated)
+
+External topic skills below are **presets activated by PM**, not unconditional role dependencies — the reviewer identity and NEVER rules above stand alone. Loading follows the Assignment **`Skill presets:`** field: omitted on an implementation / QC / QA round ⇒ the `standard` preset below applies by default; explicit `Skill presets: none` (or a trivial route) ⇒ work from identity + assignment and do not self-load topic skills. When active, load in order (**hub matrix:** `mstar-roles` SKILL.md):
+
+Role-owned procedures — **always read with this file, never preset-gated**: `references/qc-specialist/reviewer-workflow.md`, `references/qc-specialist/reviewer-checklist.md`, `references/qc-specialist/report-template.md`; `references/qc-specialist/deep-review-lenses.md` on demand.
+
+1. `mstar-harness-core` → `mstar-dispatch-gates` + `mstar-branch-worktree` → `mstar-artifacts` (review bundle paths and naming)
+2. Host: `mstar-host` → active host reference
+3. On demand: `mstar-conventions` (paths); `mstar-design-md` (UI vs DESIGN.md)
+
 ## Completion Report
 
 Template (fill `{role_id}`) → **`references/_shared/leaf-executor-core.md`**「Completion Report」。

package/harness-skills/mstar-roles/references/writing-specialist.md

@@ -1,12 +1,3 @@
-## Required Skill Dependencies
-
-**Hub matrix:** `mstar-roles` SKILL.md.
-
-**Always:** `mstar-harness-core`, `mstar-dispatch-gates`, `mstar-coding-behavior` (surgical edits).
-
-**Typically:** `mstar-conventions` (where deliverables land under `{HARNESS_DIR}` / `docs/`); `mstar-artifacts` (when writing under knowledge or plan trees).
-
-**Host:** `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`).
 
 ## Role Mission
 
@@ -80,6 +71,14 @@ One explanation has one home; essential contract facts may repeat locally. Each
 - **Atomic-move rule**: a move = remove + add + fixing every inbound link in the same change; no orphaned references may survive the change set.
 - **Tutorial vs reference**: user-facing docs are either a tutorial (ordered steps to an observable outcome) or a reference (explicitly scoped lookup).
 
+## Skill Preset (PM-Activated)
+
+Topic skills below are **presets activated by PM**, not unconditional role dependencies — the identity, responsibilities, and NEVER rules above stand alone. Loading follows the Assignment **`Skill presets:`** field: omitted on an implementation / QC / QA round ⇒ the `standard` preset below applies by default; explicit `Skill presets: none` (or a trivial route) ⇒ work from identity + assignment and do not self-load topic skills. When active, load in order (**hub matrix:** `mstar-roles` SKILL.md):
+
+1. `mstar-harness-core` → `mstar-dispatch-gates` → `mstar-coding-behavior` (surgical edits)
+2. Typically: `mstar-conventions` (where deliverables land under `{HARNESS_DIR}` / `docs/`); `mstar-artifacts` (when writing under knowledge or plan trees)
+3. Host: `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`)
+
 ## Completion Report
 
 Template (`{role_id}` = `writing-specialist`) → **`references/_shared/leaf-executor-core.md`**「Completion Report」。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mstar-harness/opencode",
-  "version": "3.2.5",
+  "version": "3.3.0",
   "description": "Morning Star harness OpenCode plugin — skills bootstrap + engine-backed runtime hooks (status lint, dispatch validation, Enforcement: hard gates).",
   "license": "MIT",
   "repository": {