mstar-iteration

mstar-iteration（迭代管理）

Load order

Read mstar-harness-core first. Path symbols → mstar-conventions. Per-plan gates → mstar-phase-gates. Knowledge crystallization → mstar-compound. Phase 2 implement 波次（进入 per-plan implement 前）→ mstar-sdd + mstar-dispatch-gates；Phase 2 QC 前 → mstar-review-qc。Git/worktree 载体（有 git 写或 lease 时）→ mstar-branch-worktree。Phase 1 角色派发 preflight（每次 invoke 前的 assignment preflight；enforcement: hard fail-fast）→ references/command-shared-invariants.md（本 skill 直接触发时不依赖 command 层）。On conflict, mstar-harness-core wins.

Phase 1 roadmap/milestone reads and Phase 3 close updates → mstar-project-governance, the sole owner of project roadmap/milestone read/write rules.

Phase detail 不在本 skill 正文：按下方 Phase route map 只加载当前动作对应的一行 detail——禁止无条件通读全部 phase references。

The primary coordinator owns all rows of the selected iteration and dispatches ordinary leaf tasks. Row configuration remains revisable during active execution; progress records the start and review states, and direct complete verifies QC/QA and the actual serial merge before writing Done. No row-specific PM launch or binding is required. Command entry accepts no arguments; reject nonempty arguments instead of broadening their scope.

设计思路

mstar 实践模式通常是：一次迭代锁定几个 spec 点（specify + clarify），产生多个 plan，每个 plan 含多个 tasks。per-plan 生命周期有完整的闭环（Prepare → Execute → QC → Done）。Compound 不是 per-plan 活动——它是迭代级收口，在迭代内所有 plan Done 后，沉淀一轮知识。

本 skill 管理迭代 Phase 1–6（command 层可聚合编排，但 不得反向引用 command 名；第三方 helper 仅由 command 按需发现）：

Phase 1: start
     ↓
Phase 2: Autonomous Execute  —— [per-plan lifecycle × N]
     ↓
Phase 3: iteration-close
     ↓
Phase 4: PR delivery（开 PR）
     ↓
Phase 5: PR merge-ready loop —— 至 mergeable + CI 全绿 + reviews resolved
         ├ reviewed-auto：跑 PR 级 review loop（mstar-pr-loop）→ 当前 head 上 settled、已 posted 的 ship it，**并且**（仅当存在挂载的外部 review bot；无 bot 时记 N/A）外部 AI review（§5.1b）在当前 head 达到其通过线（Greptile 5/5）、不失败、无 blocking finding = merge 授权
         └ owner-gated：停在 merge-ready → 等人类 owner 对当前 PR head 的书面批准
     ↓
Phase 6: post-merge close —— merge 授权完成、PR merged 后 §6.1–§6.4
     ↓
迭代交付完成