@mstar-harness/opencode 0.7.9 → 1.0.1

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

@@ -15,10 +15,21 @@
 | 类型 | 文件名（相对 `reports/<plan-id>/`） |
 |------|--------|
 | 架构/设计评审 | `<plan-id>-review.md`（或团队约定的 `review.md`） |
-| QC 并行报告 | `qc1.md`、`qc2.md`、`qc3.md`（与 `mstar-roles` `{report_suffix}` 一致） |
-| QC 汇总结论 | `qc-consolidated.md` |
+| QC 三审报告（**SDD 默认** `Execution mode: sdd`） | `qc1.md`、`qc2.md`、`qc3.md` |
+| QC 单席报告（**`inline` / hotfix 例外**） | `qc.md` |
+| QC 汇总结论（tri 模式） | `qc-consolidated.md` |
 
-## QC 分报告与 consolidated：可否只留一份？
+## SDD 运行时（不入 reports）
+
+Per-task briefs, implementer reports, and review diffs live under **`{SDD_DIR}`** (`mstar-plan-conventions`). Gitignored. Main plan may index `{SDD_DIR}` path only — do not paste SDD bodies into plan markdown.
+
+Plan template with Global Constraints / Interfaces → **`templates/plan.main.md`**.
+
+## QC 模式（L3 plan 级）
+
+职责分层 L1–L4 → **`mstar-review-qc/references/review-responsibility-boundaries.md`**。报告 basename 见上表；触发时机与 re-review 波次见下节 **§ QC 三审触发时机**。
+
+## QC 分报告与 consolidated（tri 模式）
 
 - **不要删除** `qc1.md`、`qc2.md`、`qc3.md` **只因为**已写入 `qc-consolidated.md`。`reports/<plan-id>/` 是**审计链**：分 reviewer 原文保留**证据出处、分歧与独立视角**；**consolidated** 是 PM 的**门控摘要**，二者**叠加**，**不互为替代**。
 - **极窄例外**（须团队显式采纳并承担审计缺口）：例如仓库体积极敏感时，仅保留 consolidated + 指向外部归档的链接——**不在**本默认 harness 中推荐；默认仍保留三份 `qc*.md`。
@@ -34,7 +45,8 @@
 
 ## 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 成本高。
+- **默认（SDD）**：同一 **`plan_id`** 下，**plan QC tri-review**（`qc-specialist` ×3 → `qc1`…`qc3` + consolidated）**仅在** dev team 按该 plan 约定范围全部交付、且 **L2 task reviewers** 均已通过后执行 **一次**。**不要**在每个中间 batch 跑完整三审。
+- **单席例外**：`Execution mode: inline` / hotfix → 交付完成后 **一次** `qc.md`（`QC mode: single`）。
 - **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`.

package/harness-skills/mstar-plan-artifacts/references/status-and-residuals.md

@@ -125,6 +125,9 @@ In old JSON, **`"severity": "warning"`** is read and rolled up as **`low`**. **F
 | `iteration_compass` | string | Optional `{ITERATION_DIR}/…` |
 | `iteration_refs` | string[] | Optional multiple compass paths |
 | `qc_status` / `tests` / `commits` | string | InReview/Done snapshots; not a substitute for `{PLAN_DIR}/reports/` |
+| `sdd_dir` | string | SDD scratch path, e.g. `{HARNESS_DIR}/sdd/<plan-id>/` (gitignored; `mstar-sdd`) |
+| `sdd_progress` | string | Optional pointer to `{SDD_DIR}/progress.md` ledger |
+| `task_commits` | array\<object\> | SDD recovery: `{ "task_id": "T1", "base": "<sha>", "head": "<sha>" }` per completed task |
 
 ### Optional delivery ledger (`phase` + `batches` + `verification`)
 

package/harness-skills/mstar-plan-artifacts/templates/plan.main.md

@@ -0,0 +1,54 @@
+# [Feature Name] Implementation Plan
+
+> **For agentic workers:** REQUIRED SUB-SKILL: Use `mstar-sdd` (recommended) or inline execution. Steps use checkbox (`- [ ]`) syntax.
+
+**Goal:** [One sentence]
+
+**Architecture:** [2–3 sentences]
+
+**Tech Stack:** [Key technologies]
+
+**Execution:** mstar-sdd | inline
+
+## Global Constraints
+
+[Project-wide requirements — version floors, naming, exact values — copied verbatim from spec. Every task implicitly includes this section.]
+
+---
+
+### Task 1: [Component Name]
+
+**Files:**
+- Create: `exact/path/to/file`
+- Modify: `exact/path/existing.py`
+- Test: `tests/path/test.py`
+
+**Interfaces:**
+- Consumes: [signatures from earlier tasks]
+- Produces: [what later tasks rely on]
+
+- [ ] **Step 1: Write the failing test**
+
+```python
+# complete test code
+```
+
+- [ ] **Step 2: Run test — expect FAIL**
+
+Run: `pytest tests/path/test.py -v`
+
+- [ ] **Step 3: Minimal implementation**
+
+- [ ] **Step 4: Run test — expect PASS**
+
+- [ ] **Step 5: Commit**
+
+## Plan self-review (PM before locked)
+
+1. **Spec coverage:** every spec requirement maps to a task
+2. **Placeholder scan:** no TBD, no "add tests" without code
+3. **Type consistency:** names match across tasks
+
+## SDD runtime (ephemeral)
+
+When using `mstar-sdd`, artifacts live under `{SDD_DIR}` (see `mstar-plan-conventions`). Do not duplicate briefs/reports in this file.

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

@@ -11,7 +11,8 @@ description: Morning Star (启明星) harness 计划目录约定 —— `{HARNES
 |-----------------|------|
 | `mstar-plan-artifacts` | 主 plan、reports、`status.json`、residual、InReview/QC 波次、knowledge |
 | `mstar-branch-worktree` | Assignment 写分支 / worktree / QC 检出 |
-| `mstar-review-qc` | 派 QC 三审（PM 同轮必读） |
+| `mstar-review-qc` | 派 QC（PM 同轮必读；SDD 强制 tri） |
+| `mstar-sdd` | PM 执行 `Execution mode: sdd` 的 implement 波次 |
 
 ## 路径符号（SSOT）
 
@@ -19,6 +20,7 @@ description: Morning Star (启明星) harness 计划目录约定 —— `{HARNES
 |------|------|
 | `{HARNESS_DIR}` | `.mstar/` |
 | `{PLAN_DIR}` | `{HARNESS_DIR}/plans/` |
+| `{SDD_DIR}` | `{HARNESS_DIR}/sdd/<plan-id>/`（SDD 运行时 scratch；gitignore） |
 | `{ITERATION_DIR}` | `{HARNESS_DIR}/iterations/` |
 | `{KNOWLEDGE_DIR}` | `{HARNESS_DIR}/knowledge/` |
 | `{SPECS_DIR}` | `specs/` 优先，否则 `designs/` |
@@ -51,8 +53,9 @@ description: Morning Star (启明星) harness 计划目录约定 —— `{HARNES
 PM 在需要持久化追踪时：
 
 1. 建 `.mstar/`、`plans/`、`status.json`（空模板见 **`mstar-plan-artifacts/templates/status.empty.json`**）
-2. 可选 `notes.json`（模板 **`mstar-plan-artifacts/templates/notes.empty.json`**）、`reports/README.md`、`knowledge/`、`iterations/`、`specs/`
-3. Git：团队交付 **勿** ignore 整个 `{HARNESS_DIR}`（handoff 需 clone 可达）
+2. 可选 `notes.json`（模板 **`mstar-plan-artifacts/templates/notes.empty.json`**）、`reports/README.md`、`knowledge/`、`iterations/`、`specs/`、`sdd/`（空目录占位；运行时 per-plan 子目录由 `mstar-sdd/scripts/sdd-workspace` 创建）
+3. 项目根 `.gitignore` 追加 `.mstar/sdd/`（或 `.agents/sdd/` legacy）— CLI `init` 可自动添加
+4. Git：团队交付 **勿** ignore 整个 `{HARNESS_DIR}`（handoff 需 clone 可达）
 
 步骤与 `{HARNESS_DIR}/AGENTS.md` 分层 → **`references/harness-bootstrap-and-agents-layering.md`**。
 

package/harness-skills/mstar-plan-conventions/references/artifact-storage-paths.md

@@ -13,7 +13,8 @@
 | **知识文档** | `.mstar/knowledge/<category>/<slug>.md` | `mstar-compound`（写）、`mstar-compound-refresh`（读写） |
 | **知识索引** | `.mstar/knowledge/README.md` | `mstar-compound`（写）、`mstar-compound-refresh`（读写） |
 | **主 plan** | `.mstar/plans/<plan-id>-<name>.md` | PM / `mstar-plan-artifacts` |
-| **QC 报告** | `.mstar/plans/reports/<plan-id>/qcN.md` | `mstar-review-qc` |
+| **QC 报告** | `.mstar/plans/reports/<plan-id>/qc1.md`…`qc3.md` + consolidated（**SDD 默认**）；`qc.md`（inline 例外） | `mstar-review-qc` |
+| **SDD scratch** | `{HARNESS_DIR}/sdd/<plan-id>/`（gitignored） | `mstar-sdd` |
 | **status.json** | `.mstar/status.json` | `mstar-plan-artifacts` |
 | **迭代 compass** | `.mstar/iterations/<iteration-id>-delivery-compass.md` | `mstar-iteration`（读写） |
 | **迭代索引** | `.mstar/iterations/README.md` | `mstar-iteration`（读写） |

package/harness-skills/mstar-plan-conventions/references/harness-bootstrap-and-agents-layering.md

@@ -14,7 +14,7 @@
 
 1. 创建 `{HARNESS_DIR}`（推荐 `.mstar/`）与 `{PLAN_DIR}`（推荐 `.mstar/plans/`）。
 2. 初始化 `status.json`：从 **`mstar-plan-artifacts/templates/status.empty.json`** 复制；residual canonical 见 **`mstar-plan-artifacts` SKILL.md**；字段与生命周期见 **`mstar-plan-artifacts/references/status-and-residuals.md`**。
-3. 初始化可选 `notes.json`（**`mstar-plan-artifacts/templates/notes.empty.json`**）与 `plans/reports/README.md`。
+3. 初始化可选 `notes.json`（**`mstar-plan-artifacts/templates/notes.empty.json`**）与 `plans/reports/README.md`；`sdd/` 空目录占位（per-plan 子目录由 `mstar-sdd/scripts/sdd-workspace` 创建；项目根 `.gitignore` 须含 `.mstar/sdd/`）。
 4. **Profile B**（统一 Done 压缩）时另建 `{HARNESS_DIR}/archived/plans/` 与 `archived/plans-done.json`（自 **`mstar-plan-artifacts/templates/plans-done.empty.json`** 复制；schema 仅 `{ "plans": [] }`，见 **`mstar-plan-artifacts/references/done-compaction.md`**）。
 5. 可选：创建 `{ITERATION_DIR}`（`iterations/` + `README.md`）与 `{KNOWLEDGE_DIR}`（`knowledge/` + `README.md`）；内容边界见 `mstar-plan-conventions` SKILL.md 与 `references/knowledge-and-designs.md`。
 6. 创建 `{HARNESS_DIR}/AGENTS.md`（harness 子树规则）：符号表可复述 `{HARNESS_DIR}`、`{PLAN_DIR}`、`{ITERATION_DIR}`、`{KNOWLEDGE_DIR}`、`{SPECS_DIR}` 与 `docs/` 分工；新项目推荐 `.mstar/AGENTS.md`，已有项目可继续使用 `.agents/AGENTS.md`。

package/harness-skills/mstar-review-qc/SKILL.md

@@ -1,22 +1,22 @@
 ---
 name: mstar-review-qc
-description: Morning Star QC/QA review baseline — tri-review workflow, checklists, report template (YAML frontmatter + Findings + Verdict), reports at `reports/<plan-id>/qc1.md` (no plan-id prefix in basename), targeted re-review after fixes, full-tri `qcN-rev2.md` exception, residual gate. Use when `@qc-specialist*` review, `@qa-engineer` verifies, or `@project-manager` dispatches/consolidates QC.
+description: Morning Star QC/QA review baseline — **SDD plans: mandatory plan QC tri-review** (`qc1`…`qc3` + consolidated); inline/hotfix single-seat (`qc.md`); checklists, report template, targeted re-review, residual gate. Per-task review is **`mstar-sdd`** task reviewers (L2). Use when `qc-specialist*` review, `qa-engineer` verifies, or `project-manager` dispatches/consolidates QC.
 ---
 
 ## Load order（必读顺序）
 
 **在同一会话或任务中首次 Read 本 skill 时：必须先 Read `mstar-harness-core` skill（SKILL.md），并按需 Read **`mstar-branch-worktree`**（`Review cwd` / `Working branch` / `Review range`）。** 本 skill 只定义 QC/QA **工作流与报告形态**；派发与三审同消息规则见 **`mstar-dispatch-gates`**；**同仓 worktree 与单一待审 `HEAD`** 以 **`mstar-branch-worktree`** 为准。冲突时 **以 `mstar-harness-core` 为准**。
 
-**摘要**：`mstar-harness-core` — QC-QA 检出与并行门禁；本 skill — 审查清单、报告模板、verdict 与 residual 留档契约。
+**摘要**：`mstar-harness-core` — QC-QA 检出与派发门禁；本 skill — 审查清单、报告模板、verdict 与 residual 留档契约。职责分层 → **`references/review-responsibility-boundaries.md`**。
 
 # Morning Star QC Review Baseline（QC 审查基线）
 
-本 skill 定义所有 QC 审查员的共享基线。三份 QC 角色提示词在流程、门禁与要点上应与本 skill 一致且彼此对齐：**共用正文以`mstar-roles` skill 的 `qc-specialist-shared`为准**；`-2` / `-3` 仅保留 frontmatter、开场白中的 Reviewer 编号、`## 并行审查时本 reviewer 的侧重` 一节，以及 Completion Report 模板里的 **Agent** 名。
+本 skill 定义所有 QC 审查员的共享基线。**`Execution mode: sdd` 时：plan 级强制 tri-review**（QC#1/#2/#3 交叉审整分支 → `qc1`…`qc3` + `qc-consolidated.md`）。**`inline` / hotfix** 可用单席 `qc.md`。三审共用正文以 **`mstar-roles`** `qc-specialist-shared` 为准。
 
 ## 分派时机（与 plan / batch 对齐）
 
-- **默认**：`@project-manager` 在 **该 plan 的实现范围已由 dev team 全部交付**、准备进入预合并门禁时，分派完整 QC 三审。**同一 `plan_id` 下多 batch 滚动实现时，不默认每 batch 跑一轮全套三审**（避免 `reports/<plan-id>/` 多套报告与范围串线）；中间阶段靠自检与 PM 协调，**显式增量三审**须在 Assignment 写明（见 `mstar-plan-conventions` `references/plan-files-and-reports.md`「QC 三审触发时机」）。
-- **同仓多 worktree 并行开发**：一轮 QC 三审仍只对应 **一套** `Review cwd` + `Working branch` + `Review range` / `Diff basis`（三票逐字相同）。若成果曾分布在 **未合并** 的多条分支或多个 `HEAD`，PM **须先**完成 Git 归并到 **单一**待审分支再派 QC；**不得**指望 reviewer 自行在多个开发 worktree 之间拼凑审查范围。**推荐** PM 在并行开发开始前已建立 **plan 集成分支** 作为各轨 merge 靶（见 `mstar-branch-worktree` 同节 **「推荐默认编排：先建 plan 集成分支，再挂各 worktree」**）。细则见 `mstar-branch-worktree` **「多 worktree 并行开发与 QC / QA 的门禁衔接」**。
+- **`Execution mode: sdd`**（单 plan 与 iteration 均适用）：全部 task + L2 task reviewers 完成后 → **强制 tri-review**（`QC mode: full tri-review`，**N=3**）。Assignment 须含 **branch review-package** 路径。PM 汇总 `qc-consolidated.md`。
+- **`Execution mode: inline`**：单席 `qc-specialist` → `qc.md`（**N=1**），或按 hotfix 路由跳过。
 - **After `Request Changes` (default)**：**Targeted re-review** — PM dispatches only QC seats that **raised** blocking findings for this fix round; each updates **the same** `{PLAN_DIR}/reports/<plan-id>/qcN.md` (e.g. `qc1.md` — no `<plan-id>` prefix in basename) (add `## Revalidation`, update verdict). **Do not** spawn `qcN-rev2.md` files on this path. Artifact naming and PM consolidated updates → **`mstar-plan-artifacts/references/plan-files-and-reports.md`** § QC 三审触发时机.
 - **Full tri re-review (exception)**：Assignment must say **`QC re-review: full tri-review`**; then new basenames (`qc1-rev2.md` … `qc-consolidated-rev2.md`); PM marks **active wave** in consolidated decision.
 

package/harness-skills/mstar-review-qc/references/review-responsibility-boundaries.md

@@ -0,0 +1,41 @@
+# Review responsibility boundaries (1.0.0+)
+
+## Four layers (orthogonal — do not collapse)
+
+| Layer | Who | When | Scope | Input |
+|-------|-----|------|-------|--------|
+| **L1** Implementer | dev subagent | Per task | Write code + TDD evidence | `task-N-brief.md` |
+| **L2** Task reviewer | PM-dispatched subagent (SDD) | Per task, after implementer | Spec + quality for **one task** | brief, report, **task-level** diff |
+| **L3** Plan QC tri (cross-review) | `qc-specialist` + `qc-specialist-2` + `qc-specialist-3` | After **all** tasks on branch | Integration, regression, contract drift — **independent lenses, same branch diff** | Branch `review-package` MERGE_BASE..HEAD |
+| **L4** QA | `qa-engineer` | After QC gate | Acceptance, residual, Done | QC reports + plan + `status.json` |
+
+**SDD rule:** Layers L1–L2 run **per task** (serial). Layer L3 is **mandatory full tri-review** (`N=3`) whenever **`Execution mode: sdd`** — single-plan **and** iteration **and** multi-plan iteration. Layer L3 is **not** optional “final single review”.
+
+**Non-SDD (`Execution mode: inline`):** hotfix / single-stream — plan QC may be **single-seat** (`qc.md`) or skipped per PM routing.
+
+Per-task spec/quality is **done** in L2 before L3. QC seats do not re-derive each task from scratch; they cross-review the **whole branch** for gaps L2 could not see.
+
+## Plan QC tri (SDD mandatory)
+
+- Assignment: **`QC mode: full tri-review`** (implicit when `Execution mode: sdd`; PM may state explicitly).
+- **N=3** same dispatch message: QC#1 architecture/maintainability → `qc1.md`; QC#2 security/correctness → `qc2.md`; QC#3 performance/reliability → `qc3.md`.
+- PM **`qc-consolidated.md`** — cross-review synthesis; PM gate input.
+- Dispatch must include **Review package path** (branch diff file).
+- **NEVER** substitute a single `qc-specialist` for L3 when SDD was used, unless user override: `QC mode: single — override: <reason>`.
+
+## Plan QC single-seat (inline / exception only)
+
+- Report: `{PLAN_DIR}/reports/<plan-id>/qc.md`
+- `Execution mode: inline` hotfix paths; or explicit override on SDD plan.
+- `N=1`; no `qc-consolidated.md` required.
+
+## Fix waves
+
+| After | Fix dispatch |
+|-------|----------------|
+| Task review Critical/Important | Task fix subagent → task re-review (L2) |
+| Plan QC Critical/Important | **One** fix subagent with **complete** finding list → **targeted** QC re-review (listed seats) |
+
+## Minor findings
+
+Task reviewer Minor → `{SDD_DIR}/progress.md` § Minor. Plan QC Minor → `qcN.md` + optional residual via PM.

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

@@ -60,13 +60,17 @@ Role `references/*.md` files include explicit **`NEVER`** sections (anti-recursi
 
 ### QC reviewer (`qc-specialist*` family)
 
+**Default (SDD):** plan QC tri-review — `qc-specialist` / `qc-specialist-2` / `qc-specialist-3` → `qc1`…`qc3` + `qc-consolidated.md` when **`Execution mode: sdd`**.
+
+**Exception (`inline` / hotfix):** single-seat → `qc.md` (`QC mode: single`).
+
 | role_id | reviewer_index | focus | report_suffix |
 | --- | --- | --- | --- |
 | `qc-specialist` | `1` | Architecture coherence and maintainability risk | `qc1` → `{PLAN_DIR}/reports/<plan-id>/qc1.md` |
 | `qc-specialist-2` | `2` | Security and correctness risk | `qc2` → `…/qc2.md` |
 | `qc-specialist-3` | `3` | Performance and reliability risk | `qc3` → `…/qc3.md` |
 
-PM consolidated: `…/qc-consolidated.md` (same folder; no `<plan-id>` basename prefix). Naming SSOT: `mstar-plan-artifacts/references/plan-files-and-reports.md`.
+PM consolidated (tri mode): `…/qc-consolidated.md` (same folder; no `<plan-id>` basename prefix). Naming SSOT: `mstar-plan-artifacts/references/plan-files-and-reports.md`.
 
 ## Maintenance Rules
 

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

@@ -72,6 +72,12 @@ The **`**You are a leaf executor. You MUST NOT:**`** section (previously just pr
 
 **Execute as**: <role-id>
 **Delegation**: forbidden | allowed (...)
+**Execution mode**: sdd | inline | N/A
+**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**: `{HARNESS_DIR}/sdd/<plan-id>/` | N/A
+**Model tier**: fast | standard | capable | N/A
+**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
 **Primary**: <route type>
 **Task category**: `visual` | `deep` | `quick` | `logic` | `ops` | `docs`
@@ -158,3 +164,17 @@ The **`**You are a leaf executor. You MUST NOT:**`** section (previously just pr
 
 For host behavior details (dispatch turn shape, paste-only failure mode, invoke-count discipline),
 read `mstar-host` → the active host reference and `references/parallel-dispatch.md` as host SSOT for dispatch.
+
+## SDD vs inline implement Assignment（PM）
+
+| Mode | Who loads `mstar-sdd` | Assignment shape |
+|------|----------------------|------------------|
+| **`Execution mode: sdd`**（多 task 默认；iteration Phase 2 默认） | **PM** before first implement dispatch | **Per task**：one implementer dispatch + one **fresh** task reviewer；prompt 只含 `{SDD_DIR}/task-N-brief.md` + report 路径 |
+| **`SDD implementer session: sticky`** | PM | Task 1: `fresh` or start sticky + `implementer-session.json`; Task 2+: host **resume** + continuation prompt — **still** per-task review |
+| **`Execution mode: inline`**（hotfix / 单 task） | PM optional | One leaf Assignment；可含完整 scope，但仍须 canonical 字段 |
+
+**NEVER（SDD）**：
+
+- 把整份 plan 或 T1–Tn 全文贴进 **一个** `fullstack-dev` leaf Assignment。
+- 省略 `Execution mode` / `SDD dir` / `Model tier` 却期望 SDD 产物（`progress.md`、per-task review）。
+- 期望 leaf `fullstack-dev` 载入 `mstar-sdd` 并自编排 per-task 循环 — **编排仅 PM**（`iteration-drive` / `mstar-iteration` §2.4–2.5）。

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

@@ -2,33 +2,42 @@
 
 Use this reference when PM is dispatching QC, consolidating review verdicts, or managing residual findings lifecycle.
 
-## QC Tri-Review Minimal Flow
-
-0. Pre-dispatch read gate: read `mstar-review-qc` for this round.
-1. Dispatch three independent QC assignments.
-2. Collect reports and verify alignment fields:
-   - `plan_id`
-   - `Review range / Diff basis` — use `metadata.target_branch` or PM-specified base ref for merge-base; **do not** assume `origin/main` in formal iterations (`mstar-iteration` §2.3)
-   - `Review cwd / Worktree path`
-   - `Working branch`
-3. Verify runtime identity/model mapping for three distinct QC roles.
-4. De-duplicate findings and resolve conflicts by evidence strength.
-5. Emit one consolidated gate decision.
-6. After dev fixes blocking items:
-   - **Default**: **Targeted QC re-review** — dispatch only QC seats that **raised** blocking findings (consolidated table, R# `source` e.g. `QC-#2` → `qc-specialist-2`, or originating `qcN.md` / `F-###`). Assignment: `QC re-review: targeted — reviewers: <role-ids>`. Same `plan_id` + `Review range` / `Diff basis` unless PM narrows to fix commits (must still be copy-pasteable for QA).
-   - Each targeted QC **edits the same** `qc1.md` / `qc2.md` / `qc3.md` (per seat); PM **edits the same** `qc-consolidated.md`. **Do not** re-dispatch all three by default.
-   - **Exception**: `QC re-review: full tri-review` → three parallel QC again + new `qc1-rev2.md` … files (see `mstar-plan-artifacts/references/plan-files-and-reports.md`).
-   - Then **QA** when the gate requires sign-off (same checkout fields as initial review).
+**Layer SSOT (L1–L4):** `mstar-review-qc/references/review-responsibility-boundaries.md`. Dispatch mechanics → **`mstar-dispatch-gates`**; QC checklists / verdict → **`mstar-review-qc`**.
+
+## SDD path: mandatory plan QC tri-review (L3)
+
+**When:** `Execution mode: sdd` — **all** multi-task implement flows (single plan **or** `mstar-iteration` Phase 2).
+
+**Per-task (L2):** task reviewer only — **not** `qc-specialist`. One reviewer subagent per task (spec + quality on task diff).
+
+**After all tasks (L3):** see **`mstar-review-qc/references/review-responsibility-boundaries.md`** · **`mstar-dispatch-gates`** (N=3 same message, branch review-package, `qc1`…`qc3` + consolidated). PM checklist:
+
+0. Pre-dispatch: read `mstar-review-qc`.
+1. `review-package MERGE_BASE HEAD` → branch diff under `{SDD_DIR}` or PM path.
+2. Dispatch **three** QC seats in **one** message (**N=3**); alignment fields text-identical across reports and Assignment.
+3. PM writes `qc-consolidated.md`; after fixes → targeted re-review (default) or `QC re-review: full tri-review` for new wave files.
+
+**NEVER** end an SDD plan with only a single final `qc-specialist` unless user override: `QC mode: single — override: <reason>`.
+
+## Inline / hotfix: single-seat QC (exception)
+
+**When:** `Execution mode: inline` or explicit hotfix routing.
+
+1. Branch review-package path on dispatch.
+2. **One** `qc-specialist` → `qc.md` (**N=1**).
+3. Targeted re-review updates same `qc.md`.
 
 ## QC / Residual NEVER (PM)
 
-- **NEVER** consolidate tri-review into `Approve` when any QC report’s `plan_id`, `Review range / Diff basis`, `Review cwd / Worktree path`, or `Working branch` **differs** from the PM Assignment text (character-level mismatch).
-- **NEVER** register or rewrite residual `severity` values outside the machine enum in `mstar-plan-artifacts`.
-- **NEVER** drop residual tracking to chat-only when `Approve with residuals` applies—canonical open list lives under `{HARNESS_DIR}/status.json` `residual_findings[<plan-id>]`.
-- **NEVER** archive or delete open residual rows from `status.json` without the documented close + `{HARNESS_DIR}/archived/residuals/` workflow.
-- **NEVER** treat “two of three QC reports arrived” as sufficient for a **full parallel tri-review wave**—missing reviewer => `Blocked` or explicit PM decision, not silent `Approve`.
-- **NEVER** re-dispatch all three QC reviewers after a routine fix round when only one or two seats had blocking findings—use **targeted re-review** unless Assignment declares **`QC re-review: full tri-review`**.
-- **NEVER** create `qc1-rev2.md` (etc.) for **targeted** re-review; update the original `qcN.md` in place.
+- **NEVER** dispatch plan QC without a **branch** review-package file path (MERGE_BASE..HEAD).
+- **NEVER** use single-seat `qc.md` after **`Execution mode: sdd`** without documented user override.
+- **NEVER** dispatch only QC#2 and QC#3 while skipping QC#1 on initial SDD tri wave — full **N=3** cross-review required (all three seats).
+- **NEVER** consolidate tri-review into `Approve` when any QC report's alignment fields differ from Assignment (character-level).
+- **NEVER** register or rewrite residual `severity` outside `mstar-plan-artifacts` machine enum.
+- **NEVER** drop residual tracking to chat-only when `Approve with residuals` applies.
+- **NEVER** treat "two of three QC reports arrived" as sufficient — missing seat → `Blocked`.
+- **NEVER** re-dispatch all three after routine fix when only one or two had blockers — **targeted re-review** unless `QC re-review: full tri-review`.
+- **NEVER** create `qc1-rev2.md` for **targeted** re-review; update original `qcN.md` in place.
 
 ## Consolidated Decision Template
 

package/harness-skills/mstar-roles/references/project-manager/routing-and-dev-allocation.md

@@ -80,7 +80,8 @@ Document override as `Dev owner tie-break: single id — <reason>`.
 - `frontend-dev` + `fullstack-dev` can run in parallel once interface contract is clear.
 - `fullstack-dev` + `fullstack-dev-2` can run in parallel when module boundaries are explicit.
 - Same-repo multi-writer concurrency requires branch + worktree isolation.
-- QC tri-review defaults to one full tri-review wave per plan completion (unless explicit incremental QC gate is declared).
+- **SDD implement** (`Execution mode: sdd`, default multi-task): per-task **task reviewer** (L2) + plan **QC tri-review** (L3, N=3).
+- **Inline / hotfix**: single-seat QC or skip per routing table.
 
 ## Routing / allocation NEVER (PM)
 

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

@@ -7,7 +7,8 @@ Before any non-trivial PM action, read in order:
 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-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)
+6. **`mstar-sdd`** when implement uses **`Execution mode: sdd`**
+7. **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).
 
@@ -56,11 +57,11 @@ Pick one `Primary` route per Assignment; attach additional gates as needed.
 
 | Task type | Default route |
 | --- | --- |
-| Large feature | `explore -> product-manager -> architect -> dev -> QC tri-review -> qa-engineer -> ops-engineer` |
-| Medium feature | `explore -> (architect optional) -> dev -> QC tri-review -> qa-engineer` |
-| Small feature | `dev -> QC tri-review -> qa-engineer` |
-| Bug fix | `explore -> RCA brief -> dev -> QC tri-review -> qa-engineer` |
-| High-ambiguity bug | `explore -> RCA -> (architect optional) -> dev -> QC tri-review -> qa-engineer` |
+| Large feature | `explore -> product-manager -> architect -> dev (SDD) -> QC tri-review -> qa-engineer -> ops-engineer` |
+| Medium feature | `explore -> (architect optional) -> dev (SDD) -> QC tri-review -> qa-engineer` |
+| Small feature | `dev (SDD) -> QC tri-review -> qa-engineer` |
+| Bug fix | `explore -> RCA brief -> dev (SDD) -> QC tri-review -> qa-engineer` |
+| High-ambiguity bug | `explore -> RCA -> (architect optional) -> dev (SDD) -> QC tri-review -> qa-engineer` |
 | Hotfix | `single dev -> QC single-review -> qa-engineer fast verify` |
 | Product docs only | `product-manager` (QC may be skipped with explicit reason) |
 | Tech spec only | `architect` (QC may be skipped with explicit reason) |
@@ -78,7 +79,9 @@ Detailed conflict priority and dev allocation:
 
 ## Non-Bypass Constraints
 
-- Code-development plans require QC tri-review by default (hotfix single-review exception only).
+- Code-development plans with **`Execution mode: sdd`** (default for multi-task): **mandatory plan QC tri-review** (`qc1`…`qc3` + consolidated) after all task reviewers complete.
+- **`Execution mode: inline`**: hotfix single-seat QC (`qc.md`) or explicit skip rules unchanged.
+- Multi-task implement defaults to **`Execution mode: sdd`** + `mstar-sdd`; hotfix may use `inline`.
 - Runtime/behavior change requires QA by default.
 - Report-only QA may skip QC tri-review only when no implementation/test/config artifact is committed.
 - Product-docs-only and tech-spec-only can skip QC tri-review only with explicit `QC: skipped — <reason>`.
@@ -135,9 +138,15 @@ Before first implement dispatch (non-hotfix):
 
 If any fail -> do not dispatch implement.
 
-### PM entry sessions (`/pm` or OpenCode PM switch)
+### PM entry sessions
 
-When the session entered via **`/pm`**, **`pm` skill**, or OpenCode PM orchestration, follow **`skills/pm/SKILL.md`** — especially **Host entry**, **iteration branch policy**（`iteration_base_branch` / `spec_integration_branch` / `target_branch`）, **Autonomous Execute**（status.json backlog, per-plan feature branches）, and **Dispatch-first**. Routing, gates, Task Board, QC, and templates remain in this file and topic `mstar-*` skills.
+| Entry | Next reads |
+|-------|------------|
+| **`/pm`** or **`pm` skill** (Codex, Cursor; OpenCode when no command) | This shim → **`project-manager.md`** § Required Reading + topic skills on demand |
+| **Cursor / OpenCode** **`commands/`** (`iteration-start`, `iteration-drive`, `mstar-bootstrap`) | Command **Boot** + **`project-manager.md`** — iteration lifecycle only; **not** required for ordinary per-plan PM |
+| **OpenCode** (no command, not `/pm`) | `project-manager` + `mstar-host` → `opencode.md` |
+
+**Dispatch-first**, iteration branch policy（`iteration_base_branch` / `spec_integration_branch` / `target_branch`）, Autonomous Execute → **`mstar-iteration`** §2. Routing, gates, Task Board, QC, templates → this file + topic `mstar-*` skills.
 
 ---
 
@@ -176,7 +185,7 @@ Anti-patterns:
 - Q6: Is `Task category` aligned with route?
 - 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?
+- Q9: For QC (single or tri), are alignment fields text-identical across reviewers and Assignment? SDD / tri: `Execution mode: sdd` or explicit `QC mode: full tri-review`; inline: `QC mode: single` or skip reason.
 - 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?
@@ -285,7 +294,7 @@ Minimum invariants:
   - `references/project-manager/routing-and-dev-allocation.md`
 - Dispatch mechanics + anti-recursion + templates:
   - `references/project-manager/dispatch-and-assignment.md`
-- QC tri-review + residual lifecycle:
+- QC (SDD → mandatory tri; inline → single) + residual lifecycle:
   - `references/project-manager/qc-and-residuals.md`
 - Plan/status initialization + lifecycle:
   - `references/project-manager/plan-management.md`

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

@@ -24,9 +24,11 @@ Behavior is shared; reviewer identity is parameterized.
 
 ## Role Mission
 
-You are QC reviewer #{reviewer_index}, dispatched by `project-manager`.
+You are QC reviewer #{reviewer_index} (or the sole reviewer when `QC mode: single`), dispatched by `project-manager`.
 Your output is a structured QC report plus completion report.
 
+**Default (SDD):** plan QC tri on whole-branch review-package (`QC mode: full tri-review`). **Exception:** `Execution mode: inline` → single-seat `qc.md`.
+
 ## Non-Recursive Dispatch Rule (Hard)
 
 **You ARE `{role_id}`, a QC reviewer — not a PM, not a dispatcher.**
@@ -42,7 +44,7 @@ Your Assignment's IDENTITY block at the top already established this. Reinforcin
 
 If any item below matches, **stop** and return `Blocked` to `project-manager` instead of improvising:
 
-- **NEVER** invoke another QC seat (`qc-specialist` / `qc-specialist-2` / `qc-specialist-3`) or `{role_id}` again, nor `qa-engineer` / dev / `architect` / `project-manager`, to “split” **this** review unless `Delegation: allowed (...)` lists them. PM launches **initial** tri-review with **three** separate assignments/invokes; **targeted re-review** lists only the seats PM assigned.
+- **NEVER** invoke another QC seat or `{role_id}` again, nor `qa-engineer` / dev / `architect` / `project-manager`, to split **this** review unless `Delegation: allowed (...)` lists them. PM launches initial tri (**N=3**) when **`Execution mode: sdd`** or Assignment says **`QC mode: full tri-review`**. Single-seat only for `inline` / explicit override. **Targeted re-review** lists only seats PM assigned.
 - **NEVER** ask the user for permission to submit a report, present “notify PM?” choosers, or stall after a completed review—when requirements are met, emit **Completion Report v2** in the **same** assistant turn (with a real **Git** line when commits are required).
 - **NEVER** modify business implementation/tests, `{HARNESS_DIR}/status.json` residual lifecycle fields, `{HARNESS_DIR}/archived/`, or any path outside the host write whitelist for QC (typically `{PLAN_DIR}/reports/**/*.md` only).
 - **NEVER** `git add .` or stage unrelated paths when committing QC reports—stage **only** the report files you changed.
@@ -89,7 +91,7 @@ Use severity and formatting standards from `mstar-review-qc`; machine `severity`
 
 ## Report path (required)
 
-Write under **`{PLAN_DIR}/reports/<plan-id>/`** using basename **`{report_suffix}.md`** (e.g. `qc1.md`, `qc2.md`, `qc3.md`). **Do not** prefix the filename with `<plan-id>` — the folder already scopes the plan. PM consolidated report: **`qc-consolidated.md`** in the same directory.
+Write under **`{PLAN_DIR}/reports/<plan-id>/`** using basename **`{report_suffix}.md`** (**SDD default / tri**: `qc1.md`, `qc2.md`, `qc3.md`; **inline exception**: `qc.md`). **Do not** prefix the filename with `<plan-id>` — the folder already scopes the plan. PM consolidated report (`qc-consolidated.md`) applies to **tri mode**; single-seat may use `qc.md` alone as gate input.
 
 ## Targeted re-review (same report file)
 

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

@@ -0,0 +1,126 @@
+---
+name: mstar-sdd
+description: Morning Star subagent-driven development (SDD) — file handoff, per-task implementer + task reviewer (L2), progress ledger, branch review-package for plan QC tri (L3). **Implementer session** `fresh` (default) or **`sticky`** (same dev subagent across tasks — `references/sticky-implementer-session.md`). **Must** Read when project-manager runs `Execution mode: sdd` (multi-task plan, single-plan, or iteration Phase 2), dispatches SDD implementer/reviewer subagents, or prepares review-package paths. Leaf implementer/reviewer subagents skip PM sections via SUBAGENT-STOP in dispatch prompts.
+---
+
+## Load order
+
+**Before first Read:** `mstar-harness-core` → `mstar-dispatch-gates`. Path symbols → **`mstar-plan-conventions`** (`{SDD_DIR}`). Plan QC after SDD → **`mstar-review-qc`**. On conflict, **`mstar-harness-core` wins**.
+
+<SUBAGENT-STOP>
+If you were dispatched as an SDD implementer or task reviewer, skip PM orchestration sections. Follow your dispatch prompt only.
+</SUBAGENT-STOP>
+
+## When to use
+
+- Plan locked; tasks mostly independent; PM orchestrates in-session
+- Assignment has **`Execution mode: sdd`**
+- **Not** for hotfix inline work (`Execution mode: inline`) or leaf self-dispatch
+
+## Core principle
+
+**Default:** fresh implementer subagent per task + task review (spec + quality) + plan-level QC on whole branch = quality with isolated context.
+
+**Optional:** **`SDD implementer session: sticky`** — same implementer subagent across sequential tasks on one plan/branch; **task reviewers stay fresh per task**. SSOT → **`references/sticky-implementer-session.md`**.
+
+**Narration:** at most one short line between tool calls — ledger and file paths carry the record.
+
+**Continuous execution:** do not check in with the human between tasks. Stop only for BLOCKED, genuine ambiguity, or all tasks complete.
+
+## Pre-flight plan scan
+
+Before Task 1, scan plan once for:
+
+- tasks contradicting Global Constraints
+- plan-mandated items that review rubric would flag as defects
+
+Batch all findings for the human in one message. If clean, proceed silently.
+
+## Per-task loop (PM only)
+
+1. Record `BASE_SHA` (never use `HEAD~1` later)
+2. `sdd-workspace <plan-id>` → `SDD_DIR`
+3. `task-brief <plan> N` → brief file
+4. Dispatch implementer:
+   - **`SDD implementer session: fresh`** (default) — new subagent; templates: `references/implementer-prompt.md`
+   - **`SDD implementer session: sticky`** — first task: same as fresh + write `{SDD_DIR}/implementer-session.json` with `host_agent_id`; later tasks: host **resume** + `references/implementer-continuation-prompt.md` (see **`references/sticky-implementer-session.md`**)
+5. On `DONE`: `review-package BASE HEAD` → diff file
+6. Dispatch **fresh** task reviewer (brief, report, diff, Global Constraints) — `references/task-reviewer-prompt.md` — **never** sticky resume for reviewers
+7. Fix loop for Critical/Important; re-review until approved
+8. Append `progress.md`; update `status.json` `task_commits[]` and `implementer-session.json` `last_task` if sticky
+9. Next task
+
+**Never** dispatch multiple implementers in parallel (write conflicts).
+
+Detail: **`references/file-handoffs.md`**.
+
+## Implementer statuses
+
+| Status | PM action |
+|--------|-----------|
+| DONE | review-package → task reviewer |
+| DONE_WITH_CONCERNS | read concerns; fix scope issues before review |
+| NEEDS_CONTEXT | provide context; re-dispatch |
+| BLOCKED | more context, higher tier, split task, or escalate human — **never** same-model blind retry |
+
+## Reviewer ⚠️ items
+
+`⚠️ Cannot verify from diff` does not block other findings. PM must resolve each before task complete.
+
+## Model tier
+
+| Tier | Use |
+|------|-----|
+| fast | Transcription (complete code in plan); 1–2 file mechanical |
+| standard | Prose implementer; task reviewer (floor) |
+| capable | Integration judgment; plan QC on large branch diff |
+
+**Turn count beats token price:** use `standard` floor for reviewers and prose implementers. **Always name model on dispatch** — omitted model inherits session default (often most expensive).
+
+Host mapping → **`mstar-host`** references (`model` / Task field).
+
+## After all tasks
+
+1. `review-package MERGE_BASE HEAD` → branch diff in `{SDD_DIR}`
+2. PM dispatches **plan QC tri-review (L3)** — **`QC mode: full tri-review`**, **N=3** — with branch review-package path → **`mstar-review-qc`** · **`mstar-dispatch-gates`**. Layer SSOT → **`mstar-review-qc/references/review-responsibility-boundaries.md`**. PM writes `qc-consolidated.md`. **Mandatory whenever `Execution mode: sdd`** (single-plan or iteration).
+3. Critical/Important QC findings → **one** fix dispatch (full list), then targeted re-review
+4. QA gate → **`mstar-review-qc`** / `mstar-harness-core` Done rules
+
+## Progress ledger
+
+At start: `cat {SDD_DIR}/progress.md`. Tasks marked complete are DONE — do not re-dispatch after compaction.
+
+Append on clean review: `Task N: complete (<base>..<head>, review clean)`.
+
+Minor findings → `## Minor (for plan QC)` section in same file.
+
+## Red flags (NEVER)
+
+- Parallel implementer dispatches
+- Paste plan, diffs, or task history into dispatch prompts
+- Dispatch reviewer without diff file
+- `HEAD~1` as review BASE
+- Pre-judge reviewer ("do not flag", "at most Minor")
+- Skip task review or accept missing verdict
+- Re-dispatch tasks listed complete in ledger
+- PM thread implements instead of subagent dispatch
+- Sticky **resume** for task reviewers
+- Resume implementer without `host_agent_id` in `implementer-session.json`
+
+## Scripts
+
+From repo: `skills/mstar-sdd/scripts/` (bundled in OpenCode as `harness-skills/mstar-sdd/scripts/`).
+
+| Script | Usage |
+|--------|--------|
+| `sdd-workspace` | `PLAN_ID` → creates `{SDD_DIR}`, prints path |
+| `task-brief` | `PLAN_FILE TASK_N [OUTFILE]` |
+| `review-package` | `BASE HEAD [OUTFILE]` |
+
+## References
+
+- `references/file-handoffs.md` — paths and fix-loop evidence
+- `references/sticky-implementer-session.md` — `fresh` vs `sticky`, ledger, host resume, micro-batch fallback
+- `references/implementer-prompt.md`
+- `references/implementer-continuation-prompt.md`
+- `references/task-reviewer-prompt.md`