@mstar-harness/opencode 0.6.4 → 0.6.6

package/harness-agents/qc-specialist-2.md

@@ -5,13 +5,17 @@ tools:
   edit: true
   bash: true
 permission:
-  # `edit` covers write/patch/multiedit. Only `.md` under resolved `{PLAN_DIR}/reports/` (three possible roots — match project layout).
+  # `edit` covers write/patch/multiedit. Only `.md` under resolved `{PLAN_DIR}/reports/` (default + legacy roots).
   edit:
     "*": deny
+    ".mstar/plans/reports/*.md": allow
+    ".mstar/plans/reports/**/*.md": allow
     ".agents/plans/reports/*.md": allow
     ".agents/plans/reports/**/*.md": allow
     ".plans/reports/*.md": allow
     ".plans/reports/**/*.md": allow
+    ".worktrees/**/.mstar/plans/reports/*.md": allow
+    ".worktrees/**/.mstar/plans/reports/**/*.md": allow
     ".worktrees/**/.agents/plans/reports/*.md": allow
     ".worktrees/**/.agents/plans/reports/**/*.md": allow
     ".worktrees/**/.plans/reports/*.md": allow

package/harness-agents/qc-specialist-3.md

@@ -5,13 +5,17 @@ tools:
   edit: true
   bash: true
 permission:
-  # `edit` covers write/patch/multiedit. Only `.md` under resolved `{PLAN_DIR}/reports/` (three possible roots — match project layout).
+  # `edit` covers write/patch/multiedit. Only `.md` under resolved `{PLAN_DIR}/reports/` (default + legacy roots).
   edit:
     "*": deny
+    ".mstar/plans/reports/*.md": allow
+    ".mstar/plans/reports/**/*.md": allow
     ".agents/plans/reports/*.md": allow
     ".agents/plans/reports/**/*.md": allow
     ".plans/reports/*.md": allow
     ".plans/reports/**/*.md": allow
+    ".worktrees/**/.mstar/plans/reports/*.md": allow
+    ".worktrees/**/.mstar/plans/reports/**/*.md": allow
     ".worktrees/**/.agents/plans/reports/*.md": allow
     ".worktrees/**/.agents/plans/reports/**/*.md": allow
     ".worktrees/**/.plans/reports/*.md": allow

package/harness-agents/qc-specialist.md

@@ -5,13 +5,17 @@ tools:
   edit: true
   bash: true
 permission:
-  # `edit` covers write/patch/multiedit. Only `.md` under resolved `{PLAN_DIR}/reports/` (three possible roots — match project layout).
+  # `edit` covers write/patch/multiedit. Only `.md` under resolved `{PLAN_DIR}/reports/` (default + legacy roots).
   edit:
     "*": deny
+    ".mstar/plans/reports/*.md": allow
+    ".mstar/plans/reports/**/*.md": allow
     ".agents/plans/reports/*.md": allow
     ".agents/plans/reports/**/*.md": allow
     ".plans/reports/*.md": allow
     ".plans/reports/**/*.md": allow
+    ".worktrees/**/.mstar/plans/reports/*.md": allow
+    ".worktrees/**/.mstar/plans/reports/**/*.md": allow
     ".worktrees/**/.agents/plans/reports/*.md": allow
     ".worktrees/**/.agents/plans/reports/**/*.md": allow
     ".worktrees/**/.plans/reports/*.md": allow

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

@@ -1,6 +1,6 @@
 ---
 name: mstar-coding-behavior
-description: Morning Star (启明星) 跨角色通用编码行为准则 —— Think Before Coding（显式假设、不静默猜测）、Simplicity First（最小实现、拒绝投机抽象）、Surgical Changes（只改与任务直接相关的行、不顺手重构、不 piggyback）、Goal-Driven Execution（把模糊请求转为可验证结果、Step → verify 微模板、证据驱动的完成声明）。任何实现、调试、重构、审查任务都应优先 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（显式假设、不静默猜测）、Simplicity First（最小耐久切片，拒绝未登记临时方案）、Surgical Changes（只改与任务直接相关的行、不顺手重构、不 piggyback）、Goal-Driven Execution（把模糊请求转为可验证结果、Step → verify 微模板；分批必须留 roadmap）。任何实现、调试、重构、审查任务都应优先 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（必读顺序）
@@ -43,16 +43,24 @@ Quick check:
 
 ## 2) Simplicity First
 
-Core idea: implement the minimum that satisfies the request and acceptance criteria.
+Core idea: implement the smallest durable slice that satisfies the request and acceptance criteria.
 
 - Do not add features, flags, or configurability that were not requested.
 - Avoid introducing new abstractions for single-use logic.
-- Prefer straightforward local fixes over framework-level reshaping.
+- Prefer straightforward local fixes over framework-level reshaping **only when they fit the target design**.
 - Reject speculative error handling for impossible paths unless required by project policy.
+- Do not confuse "minimum" with "temporary." A small implementation must still align with the long-term target state, stable interfaces, and known follow-up plan.
+- If a workaround is necessary, label it as `temporary`, explain why it is unavoidable, and record the removal path in the plan/status artifact before claiming the task is complete.
 
 Default rule:
 
-- If 200 lines can be 50 with the same behavior and clarity, prefer the smaller solution.
+- If 200 lines can be 50 with the same behavior, clarity, and durable architecture, prefer the smaller solution.
+
+Durability check:
+
+- Can this slice be extended by the next batch without undoing its core shape?
+- Are deferred items captured in an existing roadmap / task board / residual tracker, not just mentioned in chat?
+- Would a reviewer understand whether this is the final approach, a staged slice, or a temporary workaround?
 
 ## 3) Surgical Changes
 
@@ -74,8 +82,10 @@ Core idea: convert vague requests into verifiable outcomes and iterate until ver
 
 - Define concrete success criteria before major edits.
 - For multi-step tasks, use brief `Step -> verify` checkpoints.
+- For split delivery, maintain a durable roadmap: current slice, later slices, dependencies, owner/trigger, and completion condition.
 - Prefer evidence-backed completion claims (tests, command output, reproducible checks).
 - If verification fails, loop on diagnosis and fix before declaring completion.
+- Do not finish with "next plan / later / follow-up" only in prose. If the work is not fully complete, the remaining work must be written to the plan/status artifact or the task must report `Partial` / `Blocked`.
 
 Micro template:
 

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

@@ -71,6 +71,8 @@ PM 在 Assignment 写 **`Task category`**（主类 + 可选 `secondary`）：
 
 可追踪清单（plan `tasks` 或 Todo）；偏离时 PM 拉回；完成前须可核对证据（**`mstar-superpowers-align`** · `verification-before-completion`）。
 
+**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。
+
 ## 专题 skill 索引
 
 | Skill | 职责 |
@@ -127,7 +129,8 @@ Read **`mstar-host`** after this skill; detect host per its table, then Read the
 | residual 只写 plan 不写 SSOT | `mstar-plan-artifacts` |
 | 角色文件塞流程长文 | 用专题 skill |
 | 无证据宣称完成 | `mstar-coding-behavior` / verification |
-| CreatePlan 不落盘 / 无 `.agents` mirror | `mstar-host` · `cursor-plan-mode-bridge` |
+| CreatePlan 不落盘 / 无 `{HARNESS_DIR}` mirror | `mstar-host` · `cursor-plan-mode-bridge` |
+| 临时方案 / 后续计划只写在对话里 | `mstar-phase-gates` · Durable Roadmap Gate |
 
 ## 可选：OpenViking Memory
 

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

@@ -1,6 +1,6 @@
 # Codex host reference
 
-Load when **`mstar-host`** detection resolves **codex** (Codex app/CLI session, Codex plugin installed from `.codex-plugin/plugin.json`, or Codex tool namespaces such as `functions.*`, `codex_app.*`, `tool_search`, `image_gen`, or Browser plugin tools).
+Load when **`mstar-host`** detection resolves **codex** (Codex app/CLI session, Codex plugin installed from `.codex-plugin/plugin.json`, Codex custom agents linked from `codex/agents/*.toml`, or Codex tool namespaces such as `functions.*`, `codex_app.*`, `tool_search`, `image_gen`, or Browser plugin tools).
 
 Parallel PM dispatch: read **`parallel-dispatch.md`** only when Codex exposes an actual multi-agent / Task-style invocation tool. If no callable invoke tool exists, Assignment Markdown is coordination text only; do **not** claim subagent dispatch.
 
@@ -8,8 +8,9 @@ Parallel PM dispatch: read **`parallel-dispatch.md`** only when Codex exposes an
 
 - Plugin source: `.codex-plugin/plugin.json`.
 - Runtime skills: repo `skills/` mounted by the Codex plugin (`"skills": "./skills/"`).
+- Custom agent source: repo `codex/agents/*.toml`; CLI/manual install links these into `~/.codex/agents/` or project `.codex/agents/`.
 - `/pm`: shared force entry via the `pm` skill; after that, role behavior comes from `mstar-roles`.
-- Role files under `agents/` are for hosts that load agent shells; Codex role execution should load `mstar-roles` references directly.
+- Role files under root `agents/` are for hosts that load OpenCode/Cursor-style agent shells; Codex uses `codex/agents/*.toml` and still loads `mstar-roles` references directly.
 - Tool and plugin availability can be lazy-loaded or session-dependent. Use the tools actually present in the current session; do not infer capability from documentation alone.
 
 ## Skill loading
@@ -30,8 +31,8 @@ Use skill names in prompts and references. Avoid absolute local paths unless the
 
 ## Dispatch and role execution
 
-- **No invoke tool = no dispatch**: printing `## Assignment` does not start another Codex worker.
-- If Codex exposes multi-agent tools, PM may dispatch through those tools and must follow `parallel-dispatch.md`.
+- **No invoke tool / no linked custom agent = no dispatch**: printing `## Assignment` does not start another Codex worker.
+- If Codex exposes custom-agent / multi-agent tools and matching Morning Star agents are linked, PM may dispatch through those tools and must follow `parallel-dispatch.md`.
 - If no invoke tool is present, use single-session role execution: state the active role, load that role reference, complete the assignment, and return Completion Report v2.
 - QC tri-review is only "parallel" when three distinct callable reviewer sessions are actually launched in one dispatch turn. Without that, run a clearly labeled serial/manual review path or return `Blocked` for PM rerouting.
 - Leaf executors still follow `mstar-dispatch-gates`: no recursive Task/subagent calls unless Assignment says `Delegation: allowed (...)`.
@@ -51,6 +52,6 @@ Use skill names in prompts and references. Avoid absolute local paths unless the
 
 ## Gotchas
 
-- Codex plugin install gives skills, not automatic OpenCode-style named role invocations.
+- Codex plugin install gives skills; Morning Star role subagents require custom agent TOML files linked from `codex/agents/`.
 - Tool discovery (`tool_search`) can reveal capabilities, but availability is not authorization; Assignment `Delegation` still controls use.
 - Session plans, chat summaries, and UI todos are not durable harness SSOT unless mirrored to `{HARNESS_DIR}`.

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

@@ -4,7 +4,7 @@
 
 ## Purpose
 
-Cursor **Plan mode** uses **CreatePlan** and built-in plan todos for session UX. Morning Star **SSOT** lives on disk under **`{HARNESS_DIR}`** (default `.agents/`). This reference defines **dual-write**: mirror every durable plan artifact to the repo; never treat the Cursor plan URI alone as the handoff surface.
+Cursor **Plan mode** uses **CreatePlan** and built-in plan todos for session UX. Morning Star **SSOT** lives on disk under **`{HARNESS_DIR}`** (default `.mstar/`, legacy `.agents/`). This reference defines **dual-write**: mirror every durable plan artifact to the repo; never treat the Cursor plan URI alone as the handoff surface.
 
 ## Priority (hard)
 
@@ -23,7 +23,7 @@ Cursor **Plan mode** uses **CreatePlan** and built-in plan todos for session UX.
 ## Before the first CreatePlan
 
 1. **Read** (minimum): `mstar-plan-conventions`, `mstar-plan-artifacts` (SKILL.md); Prepare gates from `mstar-phase-gates` if not hotfix.
-2. **Discover** `{HARNESS_DIR}` / `{PLAN_DIR}` per `mstar-plan-conventions` (prefer `.agents/` + `.agents/plans/`).
+2. **Discover** `{HARNESS_DIR}` / `{PLAN_DIR}` per `mstar-plan-conventions` (prefer `.mstar/` + `.mstar/plans/`; reuse legacy `.agents/` only when already present and `.mstar/` is absent).
 3. **Initialize** if absent (see checklist below).
 
 ### Harness initialization checklist
@@ -58,7 +58,7 @@ Add one object to `status.json` → `plans[]`:
 {
   "id": "<plan-id>",
   "status": "Todo",
-  "file": ".agents/plans/<plan-id>-<short-name>.md",
+        "file": ".mstar/plans/<plan-id>-<short-name>.md",
   "metadata": {
     "primary_spec": "<spec-id or path if known>",
     "description": "<one-line summary>"
@@ -66,12 +66,13 @@ Add one object to `status.json` → `plans[]`:
 }
 ```
 
-Set `updated_at` on `status.json` to today (`YYYY-MM-DD`). Commit harness files in the **business repo** when the project tracks `.agents/` (default).
+Set `updated_at` on `status.json` to today (`YYYY-MM-DD`). Commit harness files in the **business repo** when the project tracks `{HARNESS_DIR}` (default).
 
 ### `mirror-plan` minimum content
 
 - YAML or markdown frontmatter with `plan_id`, title, status (`Todo` / `InProgress` — not `Done` unless PM/QA authority).
 - **Task list** as markdown checkboxes (`- [ ]` / `- [x]`) matching CreatePlan implement todos.
+- **Roadmap / deferred scope** section when delivery is staged, partial, or uses a temporary workaround.
 - Link: “SSOT status: `{HARNESS_DIR}/status.json` → `plans[]` / `residual_findings`.”
 
 After **CreatePlan**, keep CreatePlan body and mirror file **in sync** when scope changes (update both in the same coordination round).
@@ -84,9 +85,9 @@ Use this structure in CreatePlan `plan` markdown; mirror the same sections into
 # Plan: <title>
 
 **plan_id**: <plan-id>
-**HARNESS_DIR**: .agents/
-**Plan file (SSOT)**: .agents/plans/<plan-id>-<short-name>.md
-**status.json**: .agents/status.json
+**HARNESS_DIR**: .mstar/
+**Plan file (SSOT)**: .mstar/plans/<plan-id>-<short-name>.md
+**status.json**: .mstar/status.json
 
 ## Prepare gates
 
@@ -94,13 +95,21 @@ Use this structure in CreatePlan `plan` markdown; mirror the same sections into
 - clarify: [done|n/a]
 - plan: [done|in progress]
 
+## Roadmap / deferred scope
+
+- Target state: <complete outcome>
+- Current slice: <what this plan/batch delivers>
+- Later slices: <batch/order/owner or trigger>
+- Deferred scope / temporary workaround removal: <tracking location or N/A>
+- Final Done definition: <condition for full completion>
+
 ## Tasks (mirror as checkboxes in SSOT plan file)
 
 ### Bootstrap (fixed prefix — complete before implement)
 
-1. harness-init — init .agents/, status.json, reports/, archived/residuals/
+1. harness-init — init .mstar/, status.json, reports/, archived/residuals/
 2. spec-register — register plan_id in status.json; spec stub if applicable
-3. mirror-plan — write .agents/plans/<plan-id>-<short-name>.md
+3. mirror-plan — write .mstar/plans/<plan-id>-<short-name>.md
 
 ### Implement
 
@@ -144,6 +153,7 @@ Before switching from Plan to Agent for implementation (or declaring Plan phase
 - [ ] `status.json` contains `plans[]` entry with matching `id` and `file`
 - [ ] Bootstrap todos `harness-init`, `spec-register`, `mirror-plan` are **done**
 - [ ] CreatePlan implement todos reference **task ids** traceable to SSOT plan checkboxes
+- [ ] If staged/partial/temporary, CreatePlan and SSOT plan both contain `Roadmap / deferred scope`
 - [ ] **Plan Path** for any Assignment uses the SSOT path, not the Cursor plan URI
 
 If any item fails → **Blocked**; finish harness sync before implement.
@@ -177,12 +187,13 @@ When `/pm` runs under Plan mode:
 
 | Anti-pattern | Fix |
 |--------------|-----|
-| CreatePlan only, no `.agents/` files | Run bootstrap todos; Write mirror plan + status.json |
+| CreatePlan only, no `{HARNESS_DIR}` files | Run bootstrap todos; Write mirror plan + status.json |
 | Todo done, no commit | Commit per task; paste `git log -1` evidence |
 | Drift between CreatePlan and SSOT plan | Update both in same round |
 | Cursor plan URI as Plan Path | Use `{PLAN_DIR}/...` path |
 | Skip `spec-register` | Add `plans[]` row before implement |
 | Build starts coding in the parent session | Resume PM context; dispatch implement work or block on missing Assignment |
+| Follow-up only in chat / no roadmap section | Add `Roadmap / deferred scope` to CreatePlan and SSOT plan before implement |
 
 ## Related skills
 

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

@@ -11,7 +11,7 @@ Parallel PM dispatch: **`parallel-dispatch.md`** (Task tool uses same turn model
 
 ## Plan mode × harness dual-write
 
-When **Plan mode** is active, **CreatePlan is session UX**; SSOT is **`{HARNESS_DIR}`** (default `.agents/`) — `{PLAN_DIR}/<plan-id>-<name>.md`, `{HARNESS_DIR}/status.json`.
+When **Plan mode** is active, **CreatePlan is session UX**; SSOT is **`{HARNESS_DIR}`** (default `.mstar/`, legacy `.agents/`) — `{PLAN_DIR}/<plan-id>-<name>.md`, `{HARNESS_DIR}/status.json`.
 
 Before first **CreatePlan**: Read `mstar-plan-conventions`, `mstar-plan-artifacts`, Prepare gates from `mstar-phase-gates` when not hotfix. Full procedure: **`cursor-plan-mode-bridge.md`**.
 

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

@@ -1,6 +1,6 @@
 ---
 name: mstar-phase-gates
-description: Morning Star (启明星) Spec-Driven 双阶段门禁 —— Prepare（`specify → clarify → plan`）、Execute（`plan(locked) → tasks → implement`）、意图门禁、clarify 核心纪律（共享理解 / 先探索 / 每问推荐答案）、hotfix 压缩路径、可验证编辑、Phase Gate 最小证据。**必须**在 PM 判定 gate、首次 implement 派单前、产品/架构参与 Prepare、或解释为何不能跳过 plan/clarify 时 Read；`@project-manager` 每轮编排非 hotfix 任务必读；`@product-manager` / `@architect` 写规格与锁 plan 时必读 Prepare 节；实现角色 Read Execute 与 hotfix 例外即可。Task category 与 `quick` 禁豁免规则仍在 `mstar-harness-core`。并行 Superpowers 短语见 `mstar-superpowers-align`。
+description: Morning Star (启明星) Spec-Driven 双阶段门禁 —— Prepare（`specify → clarify → plan`）、Execute（`plan(locked) → tasks → implement`）、意图门禁、长期目标优先、分批 roadmap 强制落盘、clarify 核心纪律（共享理解 / 先探索 / 每问推荐答案）、hotfix 压缩路径、可验证编辑、Phase Gate 最小证据。**必须**在 PM 判定 gate、首次 implement 派单前、产品/架构参与 Prepare、或解释为何不能跳过 plan/clarify 时 Read；`@project-manager` 每轮编排非 hotfix 任务必读；`@product-manager` / `@architect` 写规格与锁 plan 时必读 Prepare 节；实现角色 Read Execute 与 hotfix 例外即可。Task category 与 `quick` 禁豁免规则仍在 `mstar-harness-core`。并行 Superpowers 短语见 `mstar-superpowers-align`。
 ---
 
 ## Load order（必读顺序）
@@ -19,13 +19,15 @@ description: Morning Star (启明星) Spec-Driven 双阶段门禁 —— Prepare
     1. **能查库则查库**：若问题可通过探索代码库（实现、配置、`{SPECS_DIR}`、`{KNOWLEDGE_DIR}`、`{ITERATION_DIR}` 等）得到答案，**先探索、不向用户提问**。
     2. **每问带推荐**：每个仍需用户确认的问题，须给出**推荐答案**（及简短理由），便于快速对齐。
     3. **收口摘要**：`clarify` 结束前列出：已决事项、仍 open 的假设、对 `plan` 的约束。
-- **`plan`** — 技术方案、模块边界/接口契约、风险与回滚点、验证计划。
+- **`plan`** — 技术方案、长期目标状态、模块边界/接口契约、风险与回滚点、验证计划。
   - **意图门禁**：锁 plan 前须能书面写清**真实目标 / 成功判据 / 非目标**三项；否则 Prepare 未通过。
+  - **长期方案优先**：默认先设计目标状态，再裁剪本轮可交付切片；不得以“临时方案 / 混合方案 / 以后再说”替代目标设计。
+  - **Durable Roadmap Gate**：若本轮只做部分范围，plan 必须写明 roadmap（批次、依赖、暂缓项、owner/触发条件、最终完成定义）。只有一句“后续再做 / next plan”视为未通过 plan gate。
 
 ### B. Execute：`plan(locked) → tasks → implement`
 
 - **`plan(locked)`** — 冻结基线；实现中出现新约束时**先回写 plan 再继续**。
-- **`tasks`** — 含依赖顺序、并行标记、完成判据；每任务可追踪到 plan 与验收标准。
+- **`tasks`** — 含依赖顺序、并行标记、完成判据；每任务可追踪到 plan、roadmap 批次与验收标准。
   - **并行标签**：若 PM 将 ≥2 条实现轨 **同时** 分派，须在 `Superpowers` 中写入 `dispatching-parallel-agents`；同仓 ≥2 可写并发时叠 `using-git-worktrees`（见 **`mstar-superpowers-align`** 与 **`mstar-branch-worktree`**）。
 - **`implement`** — 按 tasks 顺序执行并提交自检证据；完成进入 `InReview`；遵循 **`mstar-coding-behavior`**。
 
@@ -65,8 +67,9 @@ description: Morning Star (启明星) Spec-Driven 双阶段门禁 —— Prepare
   - **`clarify` 核心纪律**（见 **`mstar-phase-gates` SKILL.md** Prepare · `clarify`）：逐方面核对至共享理解；沿设计决策树逐枝、一次一决；能探索代码库则先探索；每问附推荐答案；阶段末汇总已决与仍 open 假设。
 - `plan`
   - 目标：给出可执行技术方案与风险控制。
-  - 最小产物：方案、模块边界/接口契约、风险与回滚、验证计划。
+  - 最小产物：目标状态、方案、模块边界/接口契约、风险与回滚、验证计划。
   - **准入**：能书面写出真实目标、成功判据、非目标后再锁 plan（同 `SKILL.md`）。
+  - **分批准入**：若计划不是一次性交付完整范围，须写 `Roadmap / Batch Plan`：本批做什么、后续批次做什么、依赖顺序、暂缓项、owner/触发条件、最终 Done 定义；缺失则 `blocked`。
 
 ### B. Execute
 
@@ -77,7 +80,7 @@ description: Morning Star (启明星) Spec-Driven 双阶段门禁 —— Prepare
   - 最小动作：在 plan 或 notes 记录当前锁定版本（日期或 hash）。
 - `tasks`
   - 目标：把 plan 拆成可执行任务与依赖顺序。
-  - 最小产物：任务列表、并行标记、完成判据、映射到验收标准。
+  - 最小产物：任务列表、并行标记、完成判据、映射到验收标准与 roadmap 批次。
   - **PM**：若并行标记对应「多轨同时 implement」，在对外 **Status Update** 与实现 Assignment 的 **`Superpowers`** 中写入 **`dispatching-parallel-agents`**（或同义短语）；同仓多可写并发时叠 **`using-git-worktrees`**（见 `mstar-superpowers-align`）。
 - `implement`
   - 目标：按任务执行并提交证据，进入审查。
@@ -108,10 +111,11 @@ description: Morning Star (启明星) Spec-Driven 双阶段门禁 —— Prepare
 2. `clarify` 是否完成（高影响歧义是否收敛）？
 3. 意图门禁是否满足（真实目标 / 成功判据 / 非目标已写明）？
 4. `plan` 是否完成并可引用？
-5. `tasks` 是否完成？
-6. Assignment 是否含 **`Task category`**（实现类任务）并与 Owner 一致？
-7. 若中途出现 plan drift，是否先回写再继续？
-8. 实现说明中是否体现"最小解法 + 手术式改动 + 可验证检查"？
+5. 若分批/暂缓/临时绕行，roadmap 是否落在 plan/status 中，而不是只在对话里？
+6. `tasks` 是否完成？
+7. Assignment 是否含 **`Task category`**（实现类任务）并与 Owner 一致？
+8. 若中途出现 plan drift，是否先回写再继续？
+9. 实现说明中是否体现"最小耐久切片 + 手术式改动 + 可验证检查"？
 
 任一项为「否」时，`Gate decision` 必须是 `blocked`。
 

package/harness-skills/mstar-plan-artifacts/references/knowledge-and-designs.md

@@ -22,10 +22,10 @@
 
 ## `{ITERATION_DIR}`（可选·迭代/版本级 compass）
 
-- **物理路径**：`**{ITERATION_DIR}/**`（推荐布局下常为 `**.agents/iterations/**`，与 `{KNOWLEDGE_DIR}`、`{PLAN_DIR}` 并列）。
+- **物理路径**：`**{ITERATION_DIR}/**`（推荐布局下常为 `**.mstar/iterations/**`，与 `{KNOWLEDGE_DIR}`、`{PLAN_DIR}` 并列；legacy 项目可继续为 `.agents/iterations/`）。
 - **放什么**：某一**交付版本或迭代**的范围、里程碑、验收、风险、program 备注；命名示例 `v1.15-delivery-compass-v1.md`、`*-program-compass-*.md`；遗留非标准 `v1.*` 规划快照可保留于此并列入索引。
 - **不放什么**：可跨版本复用的实现 SSOT（进 `{KNOWLEDGE_DIR}`）；冻结产品/API 规范（进 `{SPECS_DIR}`）；单 plan 的 QC 留档（进 `{PLAN_DIR}/reports/`）。
-- **索引**：**必须**维护 `**{ITERATION_DIR}/README.md**`：至少 **Document**、**Version / iteration**、**Description**；可按「Delivery compasses」与「Legacy artifacts」分表（参考 Nexus `.agents/iterations/README.md`）。
+- **索引**：**必须**维护 `**{ITERATION_DIR}/README.md**`：至少 **Document**、**Version / iteration**、**Description**；可按「Delivery compasses」与「Legacy artifacts」分表。
 - **与 plan 的链接**：在 `**plans[].metadata**` 中可用 `**iteration_compass**`（单文件）或 `**iteration_refs**`（`string[]`）登记仓库内相对路径；PM 在 Assignment 点名本轮须读的 compass。
 - **维护**：`@product-manager` / `@architect` 起草；`**@project-manager**` 维护 README 与 metadata 挂接；compass 定稿后**少改多版本**（新版本优先新文件名 `v<N>` 或新 compass 文件）。
 
@@ -44,7 +44,7 @@
 
 ## 与 `status.json` 的链接
 
-- 某 plan 的**权威设计输入**在知识库、迭代 compass 或规格目录中时，在 `**plans[].metadata**` 中登记路径，推荐使用已列标准键：`**primary_spec**`（单文件）、`**spec_refs**`（`string[]`）、`**iteration_compass**` / `**iteration_refs**`（迭代级，可选）。路径为**仓库内相对路径**（推荐布局下常写作 `**.agents/knowledge/....md**`、`**.agents/iterations/....md**` 或 `**.agents/specs/....md**`；兼容旧目录时也可为 `**.agents/designs/....md**`）。
+- 某 plan 的**权威设计输入**在知识库、迭代 compass 或规格目录中时，在 `**plans[].metadata**` 中登记路径，推荐使用已列标准键：`**primary_spec**`（单文件）、`**spec_refs**`（`string[]`）、`**iteration_compass**` / `**iteration_refs**`（迭代级，可选）。路径为**仓库内相对路径**（推荐布局下常写作 `**.mstar/knowledge/....md**`、`**.mstar/iterations/....md**` 或 `**.mstar/specs/....md**`；兼容旧目录时也可为 `.agents/...`）。
 - 执行方在 **implement 前**须按 metadata 读取这些文件，并与主 plan 核对；不得在未读链接文档的情况下**静默偏离**其中已写明的决策（若需偏离，先回写 knowledge 或 plan 并走 PM/architect 门禁）。
 
 ## 维护规则
@@ -83,4 +83,4 @@
 
 **维护**：`**@project-manager`**（或与 Assignment 一致的可写角色）；`**@qc-specialist***` 宿主白名单通常**不含**本目录——审查结论仍以 `**reports/`** 为准，散文由 PM/实现方据结论整理。
 
-**关闭与归档**：当该条从 **open 列表**（根级 **`residual_findings[<plan-id>]`**；若仅存 legacy 侧则从该处）移除并**追加**至 `**{HARNESS_DIR}/archived/residuals/<plan-id>.json`** 时，应将对应 `**.md**` 一并收口：可迁入 `**{HARNESS_DIR}/archived/knowledge/**`（若视为历史考据）、或团队约定的 `**{HARNESS_DIR}/archived/residuals/**` 子路径（与 `**.json**` 同批变更可追溯）；并在归档条目的 `**closure_evidence` / `closure_note**`（或团队约定字段）中**写明散文最终路径**。勿长期保留「JSON 已关闭而散文仍留在 `residuals/` 且声称仍 open」的状态。
+**关闭与归档**：当该条从 **open 列表**（根级 **`residual_findings[<plan-id>]`**；若仅存 legacy 侧则从该处）移除并**追加**至 `**{HARNESS_DIR}/archived/residuals/<plan-id>.json`** 时，应将对应 `**.md**` 一并收口：可迁入 `**{HARNESS_DIR}/archived/knowledge/**`（若视为历史考据）、或团队约定的 `**{HARNESS_DIR}/archived/residuals/**` 子路径（与 `**.json**` 同批变更可追溯）；并在归档条目的 `**closure_evidence` / `closure_note**`（或团队约定字段）中**写明散文最终路径**。勿长期保留「JSON 已关闭而散文仍留在 `residuals/` 且声称仍 open」的状态。

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

@@ -44,7 +44,7 @@
 - **并行 vs 串行**：不同 `plan_id` **相互独立**时，可 **并行**派发多组三审（每组各自的 Assignment 与 `reports/<plan-id>/`）；若 PM 选择串行，须在 Status Update 写明顺序——**每组仍须完整三审 + QA**，不是「一个大 QC」混审。
 - **读 skill**：书写或派发 QC 相关 Assignment 前，PM **必须** Read **`mstar-review-qc`** skill（`mstar-plan-conventions` 不重复 QC 清单与 verdict 规则）。见 `mstar-plan-conventions` SKILL.md **QC pre-dispatch gate** 与 **InReview 与 QC+QA** 小节。
 
-**QC 落盘与宿主权限**：`@qc-specialist` / `@qc-specialist-2` / `@qc-specialist-3` 在支持路径白名单的宿主上（如 OpenCode 的 **`permission.edit`**），**仅可** Write/Edit **`{PLAN_DIR}/reports/`** 下 **`.md`**（全局 agent 提示词中已配置 `.agents/plans/reports/**`、`.plans/reports/**`、`plans/reports/**` 相对路径）。报告文件**必须**以 YAML **frontmatter** 开头（键见各 QC agent 提示词）。**若** 项目的 `{PLAN_DIR}` 不落在上述三种根下，须在**项目级**宿主配置（如 OpenCode）中为 QC 角色追加对应的 `edit` allow 规则。
+**QC 落盘与宿主权限**：`@qc-specialist` / `@qc-specialist-2` / `@qc-specialist-3` 在支持路径白名单的宿主上（如 OpenCode 的 **`permission.edit`**），**仅可** Write/Edit **`{PLAN_DIR}/reports/`** 下 **`.md`**（全局 agent 提示词中已配置 `.mstar/plans/reports/**`、`.agents/plans/reports/**`、`.plans/reports/**`、`plans/reports/**` 相对路径）。报告文件**必须**以 YAML **frontmatter** 开头（键见各 QC agent 提示词）。**若** 项目的 `{PLAN_DIR}` 不落在上述根下，须在**项目级**宿主配置（如 OpenCode）中为 QC 角色追加对应的 `edit` allow 规则。
 
 **QC 报告与 Git**：报告落盘后，各 QC 角色须在业务仓内对**本次报告文件**执行 **`git add` + `git commit`**（细则与 bash 权限见 `agents/qc-specialist*.md`）；**禁止**仅落盘不提交导致 `clone` 后不可见。**PM / architect / product-manager** 对 **`{HARNESS_DIR}`** / **`{PLAN_DIR}`** 与主 plan 的创建与更新亦须在业务仓内 **commit**（见 `agents/project-manager.md` Plan 初始化与 PM 职责、`agents/architect.md` / `agents/product-manager.md` Git 小节）。
 

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

@@ -241,10 +241,10 @@ Prefer **`archived/residuals/`**; migrate and delete history key when possible.
 ### Query open and archived (examples)
 
 ```bash
-# Replace .agents with your resolved {HARNESS_DIR}.
-jq '.residual_findings["01-data-infrastructure"] // .metadata.residual_findings["01-data-infrastructure"]' .agents/status.json
-jq '.entries[] | select(.id == "R1")' .agents/archived/residuals/01-data-infrastructure.json
-bash skills/mstar-plan-artifacts/scripts/tech-debt-rollup.sh .agents/status.json
+# Replace .mstar with your resolved {HARNESS_DIR}; legacy projects may use .agents.
+jq '.residual_findings["01-data-infrastructure"] // .metadata.residual_findings["01-data-infrastructure"]' .mstar/status.json
+jq '.entries[] | select(.id == "R1")' .mstar/archived/residuals/01-data-infrastructure.json
+bash skills/mstar-plan-artifacts/scripts/tech-debt-rollup.sh .mstar/status.json
 ```
 
 (`//` right-hand side = legacy read path.)
@@ -277,8 +277,8 @@ Append-only log for merge closure, batch archive, `tech_debt_summary` refresh, e
 **Compute (canonical):** run the read-only script (do **not** hand-count):
 
 ```bash
-# From repo root; pass path to status.json if not .agents/status.json
-bash skills/mstar-plan-artifacts/scripts/tech-debt-rollup.sh .agents/status.json
+# From repo root; pass path to status.json if not .mstar/status.json
+bash skills/mstar-plan-artifacts/scripts/tech-debt-rollup.sh .mstar/status.json
 ```
 
 - Prints computed `total_open`, `by_severity`, `by_target`, `by_plan`.
@@ -328,11 +328,11 @@ Before merge/PR, **`@project-manager`** (or delegate) should verify: `plans[].st
 
 - Read: accept `id` or `plan_id`.
 - Write: one canonical key (prefer `id`).
-- Document canonical key in `.agents/AGENTS.md` if migrating.
+- Document canonical key in `{HARNESS_DIR}/AGENTS.md` if migrating.
 
 ## Common queries
 
 ```bash
-jq '.plans[] | select(.id == "01-data-infrastructure")' .agents/status.json
-jq '.residual_findings["01-data-infrastructure"] // .metadata.residual_findings["01-data-infrastructure"]' .agents/status.json
+jq '.plans[] | select(.id == "01-data-infrastructure")' .mstar/status.json
+jq '.residual_findings["01-data-infrastructure"] // .metadata.residual_findings["01-data-infrastructure"]' .mstar/status.json
 ```

package/harness-skills/mstar-plan-artifacts/scripts/tech-debt-rollup.sh

@@ -3,7 +3,7 @@
 # Does not write status.json — PM applies output manually.
 set -euo pipefail
 
-STATUS_FILE="${1:-.agents/status.json}"
+STATUS_FILE="${1:-.mstar/status.json}"
 
 if [[ ! -f "$STATUS_FILE" ]]; then
   echo "error: status file not found: $STATUS_FILE" >&2

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

@@ -1,6 +1,6 @@
 ---
 name: mstar-plan-conventions
-description: Morning Star (启明星) harness 计划目录约定 —— `{HARNESS_DIR}` / `{PLAN_DIR}` / `{ITERATION_DIR}` / `{KNOWLEDGE_DIR}` / `{SPECS_DIR}` 发现与初始化、`docs/` 与 harness 子树边界、未启用 plan 时的工作方式、Spec 集成分支与多 Plan 实现分支（merge 靶与 PR 合 main）、Superpowers `writing-plans` 落盘门限、工期预估（agent-oriented）。**必须**在读写 `.agents/`、初始化 harness、编排含 plan 的任务、或对齐 `metadata.primary_spec` 时 Read；`@project-manager` 开 plan 任务前必读。plan 文件 / status / residual / reports / knowledge → **`mstar-plan-artifacts`**；分支与 QC 检出 → **`mstar-branch-worktree`**。
+description: Morning Star (启明星) harness 计划目录约定 —— `{HARNESS_DIR}` / `{PLAN_DIR}` / `{ITERATION_DIR}` / `{KNOWLEDGE_DIR}` / `{SPECS_DIR}` 发现与初始化（默认 `.mstar/`，兼容 `.agents/`）、`docs/` 与 harness 子树边界、未启用 plan 时的工作方式、Spec 集成分支与多 Plan 实现分支（merge 靶与 PR 合 main）、Superpowers `writing-plans` 落盘门限、工期预估（agent-oriented）。**必须**在读写 `.mstar/` / `.agents/`、初始化 harness、编排含 plan 的任务、或对齐 `metadata.primary_spec` 时 Read；`@project-manager` 开 plan 任务前必读。plan 文件 / status / residual / reports / knowledge → **`mstar-plan-artifacts`**；分支与 QC 检出 → **`mstar-branch-worktree`**。
 ---
 
 ## Load order（必读顺序）
@@ -17,7 +17,7 @@ description: Morning Star (启明星) harness 计划目录约定 —— `{HARNES
 
 | 符号 | 默认 |
 |------|------|
-| `{HARNESS_DIR}` | `.agents/` |
+| `{HARNESS_DIR}` | `.mstar/` |
 | `{PLAN_DIR}` | `{HARNESS_DIR}/plans/` |
 | `{ITERATION_DIR}` | `{HARNESS_DIR}/iterations/` |
 | `{KNOWLEDGE_DIR}` | `{HARNESS_DIR}/knowledge/` |
@@ -25,11 +25,12 @@ description: Morning Star (启明星) harness 计划目录约定 —— `{HARNES
 
 ### 解析顺序（找到即停）
 
-1. `.agents/` → `{HARNESS_DIR}=.agents/`, `{PLAN_DIR}=.agents/plans/`
-2. 否则 `.plans/` 或 `plans/` → 遗留同目录 `{HARNESS_DIR}={PLAN_DIR}`
-3. 皆无 → 未启用 plan；进度走对话与 Completion Report
+1. `.mstar/` → `{HARNESS_DIR}=.mstar/`, `{PLAN_DIR}=.mstar/plans/`
+2. 否则 `.agents/` → legacy `{HARNESS_DIR}=.agents/`, `{PLAN_DIR}=.agents/plans/`
+3. 否则 `.plans/` 或 `plans/` → 遗留同目录 `{HARNESS_DIR}={PLAN_DIR}`
+4. 皆无 → 未启用 plan；进度走对话与 Completion Report
 
-并存时 **`.agents/` 优先**。
+并存时 **`.mstar/` 优先**；仅当项目已有 `.agents/` 且无 `.mstar/` 时继续沿用 `.agents/`。
 
 `{SPECS_DIR}`：有 `specs/` 用之；否则 `designs/`；皆无则建议新建 `specs/`。
 
@@ -49,11 +50,11 @@ description: Morning Star (启明星) harness 计划目录约定 —— `{HARNES
 
 PM 在需要持久化追踪时：
 
-1. 建 `.agents/`、`plans/`、`status.json`（空模板见 **`mstar-plan-artifacts/templates/status.empty.json`**）
+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 可达）
 
-步骤与 `.agents/AGENTS.md` 分层 → **`references/harness-bootstrap-and-agents-layering.md`**。
+步骤与 `{HARNESS_DIR}/AGENTS.md` 分层 → **`references/harness-bootstrap-and-agents-layering.md`**。
 
 ## Spec 驱动的分支模型（多 Plan · 同一 Spec）
 

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

@@ -12,12 +12,12 @@
 
 ## Bootstrap 最小步骤
 
-1. 创建 `{HARNESS_DIR}`（推荐 `.agents/`）与 `{PLAN_DIR}`（推荐 `.agents/plans/`）。
+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`。
 4. 可选：创建 `{ITERATION_DIR}`（`iterations/` + `README.md`）与 `{KNOWLEDGE_DIR}`（`knowledge/` + `README.md`）；内容边界见 `mstar-plan-conventions` SKILL.md 与 `references/knowledge-and-designs.md`。
-5. 创建 `.agents/AGENTS.md`（harness 子树规则）：符号表可复述 `{HARNESS_DIR}`、`{PLAN_DIR}`、`{ITERATION_DIR}`、`{KNOWLEDGE_DIR}`、`{SPECS_DIR}` 与 `docs/` 分工（参考 Nexus `.agents/AGENTS.md`）。
-6. 校准根 `AGENTS.md`：只保留仓库级长期约束，显式引用 `.agents/AGENTS.md` 作为 harness SSOT。
+5. 创建 `{HARNESS_DIR}/AGENTS.md`（harness 子树规则）：符号表可复述 `{HARNESS_DIR}`、`{PLAN_DIR}`、`{ITERATION_DIR}`、`{KNOWLEDGE_DIR}`、`{SPECS_DIR}` 与 `docs/` 分工；新项目推荐 `.mstar/AGENTS.md`，已有项目可继续使用 `.agents/AGENTS.md`。
+6. 校准根 `AGENTS.md`：只保留仓库级长期约束，显式引用 `{HARNESS_DIR}/AGENTS.md` 作为 harness SSOT。
 7. 仅在确有稳定边界时新增目录级 `AGENTS.md`（如 `contracts/`、`gateway/`、`sdk/`）。
 
 ## 三层 `AGENTS.md` 职责切分
@@ -27,7 +27,7 @@
 - 放：仓库身份、技术边界、构建/测试接口、安全与分支策略、规格路由表。
 - 不放：动态状态、当前批次进展、R# 明细、QC 单次结论。
 
-### `.agents/AGENTS.md`（harness 层）
+### `{HARNESS_DIR}/AGENTS.md`（harness 层）
 
 - 放：`{HARNESS_DIR}`/`{PLAN_DIR}`/`{ITERATION_DIR}`/`{KNOWLEDGE_DIR}`/`{SPECS_DIR}` 契约、`docs/` 与 harness 子树内容边界、状态推进门禁、QC/QA 对齐规则、residual 生命周期、Done compaction profile。
 - 不放：语言/框架编码细节、业务模块实现约束。
@@ -56,7 +56,7 @@
 1. Current user instruction
 2. Root `AGENTS.md`
 3. This file
-4. `.agents/AGENTS.md`
+4. `{HARNESS_DIR}/AGENTS.md`
 
 ## Boundary Rules
 - ...
@@ -74,7 +74,7 @@
   修正：迁移到 `status.json` 的 `plans[].metadata` 与 `notes.json`。
 
 - 反模式：每个子目录复制一份完整 harness 规则。  
-  修正：保留一行引用 `.agents/AGENTS.md`，仅写本目录增量约束。
+  修正：保留一行引用 `{HARNESS_DIR}/AGENTS.md`，仅写本目录增量约束。
 
 - 反模式：目录级规则未声明 Source Priority，冲突时不可裁决。  
   修正：统一四级优先级模板并在每个目录级文件开头声明。

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

@@ -30,6 +30,7 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 - **NEVER** infer you may call `Task` / subagents because the host **lists** `subagent_type` names (`architect`, `fullstack-dev`, …). **Tool availability ≠ delegation authorization**; only **`Delegation: allowed (...)`** grants callees.
 - **NEVER** load and execute Superpowers `dispatching-parallel-agents` yourself to fan out child agents; that skill is **PM-orchestration-only** (see `mstar-superpowers-align`). If parallel runners are needed, report to PM for re-dispatch.
 - **NEVER** treat `Gate Decision: blocked` (material, high-impact ambiguities still open) as permission to hand off “ready for implement” architecture—finish clarify, update the package, or return `Blocked` to PM.
+- **NEVER** use a temporary, mixed, or partial design as the selected approach unless the target architecture and staged roadmap are written in the assigned plan/spec. “Later” without a tracking location is `Blocked`, not a handoff.
 - **NEVER** edit application implementation source, automated tests, CI workflows, Dockerfiles, or secrets-bearing runtime configuration unless the assignment explicitly limits you to doc-only placeholders **and** PM recorded the risk acceptance.
 - **NEVER** persist planning artifacts from `writing-plans` (or equivalent) under upstream `docs/superpowers/plans/`; only `{PLAN_DIR}` per `mstar-plan-conventions`.
 
@@ -79,6 +80,9 @@ Do not create your own branch strategy.
 - Option A: summary + trade-offs
 - Option B: summary + trade-offs
 - Selected Approach: why
+- Long-term Target State
+- Durable Slice for This Batch
+- Roadmap if Split: batches + dependencies + deferred scope + final Done definition
 - Module Boundaries
 - API/Data Contracts
 - Risks and Rollback
@@ -92,6 +96,8 @@ Do not create your own branch strategy.
 # Architecture: <System/Module>
 
 ## Overview
+## Long-term Target State
+## Staged Roadmap
 ## Architecture Diagram
 ## Tech Stack
 ## Module Breakdown

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

@@ -33,6 +33,7 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 - **NEVER** point `writing-plans` output to upstream `docs/superpowers/plans/`; use `{PLAN_DIR}` per `mstar-plan-conventions`.
 - **NEVER** offload PRD/product-doc drafting to `@explore`; short read-only orientation only per `mstar-harness-core`.
 - **NEVER** label a Prepare package as “ready for implement” while `Gate Decision: blocked` for material ambiguities—resolve, document waivers with PM, or return `Blocked`.
+- **NEVER** split delivery by saying “later / follow-up / next phase” without writing the product roadmap, deferred scope, and final completion definition in the assigned plan/spec.
 
 ## Superpowers (When Enabled)
 
@@ -69,6 +70,8 @@ If writing files to business repo, use only PM-assigned `Working branch` / `Bran
 - User Value
 - Scope
 - Non-goals
+- Target State
+- Roadmap if Split
 - Draft DoD
 
 ### Clarify
@@ -86,6 +89,9 @@ If writing files to business repo, use only PM-assigned `Working branch` / `Bran
 ## Target Users
 ## User Stories
 ## Acceptance Criteria
+## Target State
+## Roadmap / Release Slices
+## Deferred Scope and Tracking
 ## Priority
 ## Effort (agent-oriented)
 ```

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

@@ -53,6 +53,7 @@ For assignees (non-PM):
 **Delegation**: forbidden | allowed (...)
 **Why this agent**: <role-fit>
 **PM Task Board coverage**: <task ids>
+**Roadmap / deferred scope**: <required when staged, partial, or temporary; otherwise N/A>
 **Task**: <concrete work aligned with coverage>
 **Checkpoint Comment Rule**: commit -> Completion Report v2 -> PM Status Update -> next batch
 **Why batching is safe**: <required when batching >=3 IDs>

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

@@ -7,8 +7,8 @@ Use this reference for `{HARNESS_DIR}` / `{PLAN_DIR}` initialization, status syn
 Follow `mstar-plan-conventions` for canonical discovery.
 Preferred layout:
 
-- `{HARNESS_DIR}`: `.agents/`
-- `{PLAN_DIR}`: `.agents/plans/`
+- `{HARNESS_DIR}`: `.mstar/` by default; existing `.agents/` projects remain valid.
+- `{PLAN_DIR}`: `.mstar/plans/` by default; existing `.agents/plans/` projects remain valid.
 
 Legacy fallbacks:
 

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

@@ -116,6 +116,7 @@ If any item below matches, fix the dispatch/plan state or mark `Blocked`—do **
 - **NEVER** point QC at a single dev worktree/`Review cwd` that cannot contain **all** claimed changes from parallel tracks until Git integration lands on one `Working branch` `HEAD` (`mstar-branch-worktree` QC/QA alignment).
 - **NEVER** label `QA: skipped` for report-only QA—still dispatch `@qa-engineer` with report-only mode; QC skip rules are separate and explicit.
 - **NEVER** let non-PM/non-QA roles mark plan `Done`.
+- **NEVER** accept “temporary workaround”, “follow-up later”, “next plan”, or “split into batches” as narrative-only scope management. If work is deferred or staged, write the roadmap/tracking location before implement GO or Done.
 
 ---
 
@@ -127,7 +128,8 @@ Before first implement dispatch (non-hotfix):
 2. `clarify` done (no unresolved high-impact ambiguity)
 3. `plan` done and referenceable
 4. `tasks` + PM Task Board ready for non-trivial plan
-5. New constraints discovered are written back to plan first
+5. Roadmap written when delivery is split, deferred, or temporary
+6. New constraints discovered are written back to plan first
 
 If any fail -> do not dispatch implement.
 
@@ -177,6 +179,7 @@ Anti-patterns:
 - Q11: For non-trivial plan, is PM Task Board published with coverage?
 - Q12: In invoke-based hosts, were matching invokes actually issued?
 - Q13: With **>=2 independent** backend/fullstack units, are owners spread across `fullstack-dev` and `fullstack-dev-2` (parallel or rotated), or is `single_stream_justified: yes` recorded with a real reason?
+- Q14: If this is partial/staged/temporary, is the roadmap/tracking location written in the plan/status artifacts rather than only in prose?
 
 ---
 
@@ -195,6 +198,8 @@ Pre-implement Gate Check:
 - non_trivial_plan: yes|no
 - PM_Task_Board_published: yes|no
 - batch_strategy_defined: yes|no
+- roadmap_written: yes|no|n/a
+- roadmap_location: <Plan section / PM Task Board / status.json / residual id / n/a>
 - assignment_batch_index: <e.g. 1/3>
 - coverage_ids: <e.g. T1,T2>
 - reason_if_single_assignment: <required when only one batch>
@@ -208,6 +213,8 @@ Hard block when:
 
 - Non-trivial plan has required field = `no`
 - Harness-active non-hotfix flow lacks on-disk main plan or status registration
+- `assignment_batch_index` is not `1/1` but `roadmap_written` is not `yes`
+- Any temporary workaround or deferred scope lacks a durable tracking location
 - `Task category: quick` is used on non-trivial work
 - **>=2 independent** backend/fullstack units on the task board but `single_stream_justified: no` with no spread across `fullstack-dev` / `fullstack-dev-2` and no documented single-id override
 
@@ -218,6 +225,7 @@ Hard block when:
 Before first implement dispatch:
 
 - Publish PM Task Board with ID/owner/deps/parallel/coverage mapping
+- If delivery spans batches, include the full roadmap: batch order, deferred scope, dependencies, owner/trigger, and final Done definition
 - Every implement Assignment declares `PM Task Board coverage`
 - Default batch size 1-2 IDs; `>=3` requires `Why batching is safe`
 - Completion rhythm: commit -> Completion Report v2 -> PM Status Update -> next dispatch

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mstar-harness/opencode",
-  "version": "0.6.4",
+  "version": "0.6.6",
   "description": "Morning Star harness OpenCode plugin (skills bootstrap and agent loading).",
   "license": "MIT",
   "repository": {