cowork-flow 0.0.37 → 0.0.39

package/template/.zcode/scaffold/.cowork-flow/spec/runtime/rules.json

@@ -11,7 +11,11 @@
       "fix_hint": "创建 .cowork-flow/changes/<slug>/proposal.md 并填写目标、用户价值、范围边界",
       "source_file": ".cowork-flow/workflow.md",
       "source_excerpt": "定义 L1（增量）、L2（结构性）和 L3（重大）三级工作",
-      "enforcement": "validate_rules"
+      "enforcement": "validate_rules",
+      "validator": "runtime.l2_required_file",
+      "parameters": {
+        "filename": "proposal.md"
+      }
     },
     {
       "id": "R-WF-002",
@@ -23,7 +27,11 @@
       "fix_hint": "创建 .cowork-flow/changes/<slug>/spec.md 并填写功能规格",
       "source_file": ".cowork-flow/workflow.md",
       "source_excerpt": "L2（结构性）",
-      "enforcement": "validate_rules"
+      "enforcement": "validate_rules",
+      "validator": "runtime.l2_required_file",
+      "parameters": {
+        "filename": "spec.md"
+      }
     },
     {
       "id": "R-WF-003",
@@ -35,7 +43,11 @@
       "fix_hint": "创建 .cowork-flow/changes/<slug>/design.md 并填写技术设计",
       "source_file": ".cowork-flow/workflow.md",
       "source_excerpt": "L2（结构性）",
-      "enforcement": "validate_rules"
+      "enforcement": "validate_rules",
+      "validator": "runtime.l2_required_file",
+      "parameters": {
+        "filename": "design.md"
+      }
     },
     {
       "id": "R-WF-004",
@@ -47,7 +59,9 @@
       "fix_hint": "在 change.yaml 中添加 plan 字段指向 .cowork-flow/plans/ 下的计划文件",
       "source_file": ".cowork-flow/workflow.md",
       "source_excerpt": "L2（结构性）",
-      "enforcement": "validate_rules"
+      "enforcement": "validate_rules",
+      "validator": "runtime.l2_plan_link",
+      "parameters": {}
     },
     {
       "id": "R-WF-005",
@@ -59,7 +73,25 @@
       "fix_hint": "在 change.yaml 中添加 tasks 字段指向相关任务目录",
       "source_file": ".cowork-flow/workflow.md",
       "source_excerpt": "L2（结构性）",
-      "enforcement": "validate_rules"
+      "enforcement": "validate_rules",
+      "validator": "runtime.l2_task_link",
+      "parameters": {}
+    },
+    {
+      "id": "R-WF-006",
+      "type": "phase_gate",
+      "severity": "block",
+      "scope": "task_start",
+      "condition": "L2 任务必须有有效的 decision-review.jsonl",
+      "message": "L2 decision review evidence is missing or invalid",
+      "fix_hint": "按 .cowork-flow/spec/protocols/decision-review.md 写入已接受的结构化记录",
+      "source_file": ".cowork-flow/spec/protocols/decision-review.md",
+      "source_excerpt": "L2 task start requires accepted structured decision evidence",
+      "enforcement": "validate_rules",
+      "validator": "runtime.l2_decision_review",
+      "parameters": {
+        "filename": "decision-review.jsonl"
+      }
     },
     {
       "id": "R-WF-007",
@@ -71,7 +103,13 @@
       "fix_hint": "运行 ./.cowork-flow/run task review [task-dir] 进入检查阶段，然后运行验证命令",
       "source_file": ".cowork-flow/workflow.md",
       "source_excerpt": "先验证再完成",
-      "enforcement": "validate_rules"
+      "enforcement": "validate_rules",
+      "validator": "runtime.task_status",
+      "parameters": {
+        "allowed_statuses": [
+          "review"
+        ]
+      }
     },
     {
       "id": "R-WF-008",
@@ -83,7 +121,14 @@
       "fix_hint": "创建 <task-dir>/decision-anchor.md，至少包含 ## 目标和 ## 验收标准",
       "source_file": ".cowork-flow/spec/contracts/decision-anchor.md",
       "source_excerpt": "每个任务必须有决策锚点",
-      "enforcement": "validate_rules"
+      "enforcement": "validate_rules",
+      "validator": "runtime.decision_anchor",
+      "parameters": {
+        "required_sections": [
+          "目标",
+          "验收标准"
+        ]
+      }
     },
     {
       "id": "R-AG-002",
@@ -95,7 +140,9 @@
       "fix_hint": "规格文件只能由主会话修改，子代理应专注于实现任务",
       "source_file": ".cowork-flow/spec/contracts/subagent-dispatch.md",
       "source_excerpt": "cowork-* 固定代理是叶子执行者",
-      "enforcement": "validate_implementation"
+      "enforcement": "validate_implementation",
+      "validator": "implementation.spec_files",
+      "parameters": {}
     },
     {
       "id": "R-AG-005",
@@ -107,7 +154,9 @@
       "fix_hint": "通过 ./.cowork-flow/run task add-context <dir> implement <path> <reason> 登记所有需要修改的文件",
       "source_file": ".cowork-flow/spec/contracts/decision-anchor.md",
       "source_excerpt": "implement.jsonl 是任务的权威文件白名单",
-      "enforcement": "validate_implementation"
+      "enforcement": "validate_implementation",
+      "validator": "implementation.allowed_files",
+      "parameters": {}
     },
     {
       "id": "R-AG-006",
@@ -119,7 +168,9 @@
       "fix_hint": "保持代码简单直接，只有在确认需要复用时才进行抽象",
       "source_file": "AGENTS.md",
       "source_excerpt": "不为一次性代码做抽象",
-      "enforcement": "validate_implementation"
+      "enforcement": "validate_implementation",
+      "validator": "implementation.premature_abstraction",
+      "parameters": {}
     }
   ]
 }

package/template/.zcode/scaffold/.cowork-flow/spec/schemas/rules.schema.json

@@ -15,7 +15,7 @@
       "description": "Array of rules",
       "items": {
         "type": "object",
-        "required": ["id", "type", "severity", "scope", "condition", "message", "fix_hint", "source_file", "enforcement"],
+        "required": ["id", "type", "severity", "scope", "condition", "message", "fix_hint", "source_file", "enforcement", "validator", "parameters"],
         "anyOf": [
           {"required": ["source_anchor"]},
           {"required": ["source_excerpt"]}
@@ -69,6 +69,15 @@
             "type": "string",
             "enum": ["validate_rules", "validate_implementation"],
             "description": "Runtime surface responsible for enforcing this rule. Must have a corresponding validator module."
+          },
+          "validator": {
+            "type": "string",
+            "pattern": "^[a-z][a-z0-9_]*(\\.[a-z][a-z0-9_]*)+$",
+            "description": "Registered validator capability key. Multiple rules may reuse the same capability."
+          },
+          "parameters": {
+            "type": "object",
+            "description": "Validator-specific configuration validated by the registered capability."
           }
         },
         "additionalProperties": false

package/template/.zcode/scaffold/.cowork-flow/workflow.md

@@ -14,7 +14,7 @@ changes -> brainstorming -> read spec -> plan -> tasks -> implement -> check ->
 2. brainstorming：对changes需求做头脑风暴,确定目标、范围、验收标准、范围边界、被拒方案、实现方案、检查方案。
 3. read spec: 读取项目规范
 4. plan：构建开发计划。
-5. tasks：根据plan拆分具体执行任务、明确 PRD、整理 `implement.jsonl` / `check.jsonl`。
+5. tasks：根据plan拆分具体执行任务、明确 `decision-anchor.md`、整理 `implement.jsonl` / `check.jsonl`。
 6. implement：主会话通过当前宿主适配器派发 `cowork-implement`，按 `.cowork-flow/spec/contracts/subagent-dispatch.md` 执行固定代理派发协议。
 7. check：主会话通过当前宿主适配器派发 `cowork-check`，按 `.cowork-flow/spec/contracts/subagent-dispatch.md` 执行固定代理派发协议。
 8. complete：主会话做最终验证、同步规格、归档、记录会话、提交。
@@ -31,7 +31,7 @@ changes -> brainstorming -> read spec -> plan -> tasks -> implement -> check ->
 
 ## 1.2 需求澄清与头脑风暴门禁
 
-1. 新需求先判断清晰度。只读问题、单步且目标/范围/验收标准都清楚的小改可以绕过；否则必须先进入 `brainstorming`，在写 PRD、计划或固定代理派发前收束方向。
+1. 新需求先判断清晰度。只读问题、单步且目标/范围/验收标准都清楚的小改可以绕过；否则必须先进入 `brainstorming`，在写决策锚点、计划或固定代理派发前收束方向。
 2. 以下情况触发头脑风暴：
     - 目标、用户价值或期望行为不清楚。
     - 范围边界、非目标或影响面不清楚。
@@ -39,7 +39,7 @@ changes -> brainstorming -> read spec -> plan -> tasks -> implement -> check ->
     - 涉及 L1/L2 行为变化，或影响架构、接口、数据、权限、发布迁移。
     - 验收标准缺失、风险未知，或关键假设需要暴露。
 
-3. `brainstorming` 输出至少包括：目标、非目标、关键假设、范围边界、推荐方向、被拒方案、验收标准、开放问题/阻塞。只有方向和验收标准清楚后，才进入 PRD、计划或固定代理派发。
+3. `brainstorming` 输出至少包括：目标、非目标、关键假设、范围边界、推荐方向、被拒方案、验收标准、开放问题/阻塞。只有方向和验收标准清楚后，才进入决策锚点、计划或固定代理派发。
 
 ## 2. 状态文件
 
@@ -70,6 +70,15 @@ changes -> brainstorming -> read spec -> plan -> tasks -> implement -> check ->
 
 `task finish` 只清理当前会话任务指针，不改变 `task.json.status`。
 
+## 2.1 运行时权威边界与旧资产清理
+
+1. `scripts/commands/` 只负责参数解析和输出；任务、上下文、归档和 runtime context 业务流程由 `scripts/application/` 编排。
+2. JSON 状态写入统一经过 `scripts/common/storage/`，显式使用 UTF-8、修订检查和可恢复 Unit of Work。
+3. 宿主资产、平台识别、同步保护和 obsolete cleanup 清单以 `spec/runtime/host-assets.json` 为权威来源；禁止在命令层维护第二套平台集合。
+4. init/sync 必须先构建和验证 Asset Plan，再通过 staging、备份和 rollback 提交；`.cowork-flow/.version` 最后更新。
+5. 旧 task/session/runtime-context 只允许在带保护测试的读取边界保留；旧受管资产只允许由 sync 的 obsolete cleanup 删除。新写入必须使用当前 schema、当前目录和共享 Hook 核心。
+6. 未完成事务、损坏状态或未知 schema 不能静默继续写入；无法安全恢复时 fail-closed 并保留诊断现场。
+
 ## 3. 固定代理
 
 固定代理只执行主会话派发的叶子任务。子代理是执行者，子任务是工作单元。
@@ -91,17 +100,13 @@ changes -> brainstorming -> read spec -> plan -> tasks -> implement -> check ->
 - 固定 `cowork-*` 代理是叶子执行者；不得再派发、等待、列出或取消其他代理。
 - 通用 `worker`、`default` 或 `explorer` 只能作为 advisory work，不能满足正式实现或检查完成条件。
 
-## 3.2 手动 Party Mode
-
-Party Mode 是用户手动触发的 advisory roundtable。主会话可通过当前宿主适配器创建 fresh child contexts，收集真实讨论子代理的证据、分歧、风险和可测验收信号，再由主会话综合结论。
-
-Party Mode 不能推进任务状态，不能满足正式实现或检查完成条件，也不能替代 `cowork-implement` 或 `cowork-check`。轮次上限、继续/停止条件、输出 schema 和可配置默认值由 party-mode skill 定义；正式子代理协议仍以 `.cowork-flow/spec/contracts/subagent-dispatch.md` 为准。
+## 3.2 Party Mode
 
-## 3.2.1 手动 Party Mode V2
+Party Mode 是用户手动触发的 runtime board advisory workflow。主会话通过 `party-mode` 入口启动 `party-v2` runtime；Python runtime 控制看板、当前轮视图、schema 校验、轮次上限、纠偏事件和最终报告。
 
-Party Mode V2 是用户手动触发的 runtime board advisory workflow。Python runtime 控制看板、当前轮视图、schema 校验、轮次上限、纠偏事件和最终报告；子代理通过 board API 交流，主持人只监控 runtime status、执行宿主适配器动作和记录偏题纠正。
+Party Mode 子代理通过 board API 交流，主持人只监控 runtime status、执行宿主适配器动作和记录偏题纠正。Party Mode 不能推进任务状态，不能满足正式实现或检查完成条件，也不能替代 `cowork-implement` 或 `cowork-check`。
 
-Party Mode V2 仍不能推进任务状态，不能满足正式实现或检查完成条件，也不能替代 `cowork-implement` 或 `cowork-check`。V2 runtime 只输出 host-neutral next actions，宿主专属原语仍只在 `.cowork-flow/adapters/<host>/adapter.yaml` 和宿主资产中声明。
+Party Mode runtime 只输出 host-neutral next actions，宿主专属原语仍只在 `.cowork-flow/adapters/<host>/adapter.yaml` 和宿主资产中声明。正式子代理协议仍以 `.cowork-flow/spec/contracts/subagent-dispatch.md` 为准。
 
 ## 3.3 并行会话
 
@@ -195,7 +200,7 @@ L2 任务在 `task start` 前必须通过 readiness gate；同一 blocker 列表
 1. 先运行 `task next` 确认任务处于 `review` 检查阶段。
 2. 默认通过宿主适配器派发 `cowork-check`。派发必须使用新鲜子上下文，并遵守 `.cowork-flow/spec/contracts/subagent-dispatch.md`。
 3. 检查内容：
-    - PRD 验收标准是否满足。
+    - decision-anchor 验收标准是否满足。
     - `git diff` 是否只包含预期范围。
     - 测试是否覆盖关键行为。
     - `.cowork-flow/spec/` 是否需要更新。
@@ -233,7 +238,7 @@ L2 任务在 `task start` 前必须通过 readiness gate；同一 blocker 列表
 
 恢复时只读取最小上下文：
 1. 运行 `./.cowork-flow/run resume`。
-2. 按 `RESUME CHECKLIST` 读取当前任务 PRD、计划状态和 JSONL 指向文件。
+2. 按 `RESUME CHECKLIST` 读取当前任务 decision-anchor、计划状态和 JSONL 指向文件。
 3. 不批量读取所有规格、计划、任务或工作区日志。
 4. 不存在当前会话任务时，先创建或启动任务。
 

package/template/.zcode/scaffold/AGENTS.md

@@ -16,24 +16,34 @@
 
 ## 0.1 编码前强制门禁
 
-**编辑文件、变更代码、派发子代理之前，MUST 调用 `before-dev` skill。**
+**编辑文件、变更代码、派发子代理之前，先确定当前工作流状态，再决定放行、阻断还是路由。**
 
-该 skill 读取 `<workflow-state>` 决定放行或阻断：
+按以下顺序判定当前状态：
+
+1. **系统提示已包含 `<workflow-state>` 块（hook 注入）**: 直接按该块
+   `Status:` 行路由。
+2. **否则运行一次导航器**：
+   ```bash
+   ./.cowork-flow/run task next [task-dir-or-name]
+   ```
+   按返回的 `task.json.status` 路由，缺失活动任务时先创建再启动。
+
+状态路由：
 
 - `no_task` → **阻断**。拒绝写代码；引导 brainstorming → plan → task create → task start
-- `delegated_subtask` → 按子代理规则执行
-- `planning` → **阻断**。PRD 和 implement.jsonl 就绪前不允许实现
-- `in_progress` / `review` → 放行
-- `completed` → **阻断**。创建新任务
+- `delegated_subtask` → 按子代理规则执行，派发方核验绑定
+- `planning` → **阻断**。decision-anchor.md 和 implement.jsonl 就绪前不允许实现或派发 cowork-implement
+- `in_progress` / `review` → 放行；按当前阶段推进
+- `completed` → **阻断**。创建新任务或归档会话
 
 豁免：
 
 - 只读问答
 - 纯查询命令（`git status`、`task next`、`task current`）
 - 用户明确说"跳过流程"
-- `before-dev` 本身
+- `task next` / `task validate` 本身
 
-不确定是否需要写代码时，先调用 `before-dev`。
+不确定是否需要写代码时，先运行 `task next`。
 
 ## 1. 先思考
 

package/template/AGENTS.md

@@ -32,7 +32,7 @@
 
 - `no_task` → **阻断**。拒绝写代码；引导 brainstorming → plan → task create → task start。
 - `delegated_subtask` → 按子代理规则执行，派发方核验绑定。
-- `planning` → **阻断**。PRD 和 implement.jsonl 就绪前不允许实现或派发 cowork-implement。
+- `planning` → **阻断**。decision-anchor.md 和 implement.jsonl 就绪前不允许实现或派发 cowork-implement。
 - `in_progress` / `review` → 放行；按当前阶段推进。
 - `completed` → **阻断**。创建新任务或归档会话。
 

package/template/skills/batch-mode/SKILL.md

@@ -1,117 +1,181 @@
 ---
 name: batch-mode
-description: Use when user approves a full plan and wants autonomous execution through all tasks without manual stepping. Each task still passes all gates independently.
+description: 用户批准完整计划并要求按任务图连续执行时使用；每个任务仍独立经过 Gate、实现、检查、完成和提交。
 ---
 
 # Batch Mode
 
-## Overview
+## 核心契约
 
-User approves the plan once (`implement.jsonl`), then the agent autonomously completes all tasks. **This does not bypass verification gates** -- each task still:
-- Passes the TDD evidence gate
-- Passes the check phase gates
-- Gets an independent commit
-- Pauses back to the user on failure or high-risk steps
+Batch Scheduler 是持久化状态机，不在 CLI 内模拟实现或检查完成。
 
-Only the **manual progression between tasks** is removed.
+- 任务顺序只来自 change/task graph 的叶子任务拓扑序。
+- `implement.jsonl`、`check.jsonl` 和 `tdd.jsonl` 只作为当前任务上下文与 Gate 证据，
+  不能作为 Batch 任务列表。
+- 每次只发布一个 host-neutral `next_action`。
+- Host 执行真实动作后，必须回写结果；状态机验证仓库状态后才推进。
+- 任何 Gate、绑定、实现、检查、测试、完成或提交失败都会暂停。
+- 已完成的任务、阶段和提交不会在恢复时重复执行。
 
-## When to Use
+## 启动条件
 
-- Plan is approved (`implement.jsonl` is complete and the user said "approved" + "auto" at the end of writing-plans)
-- Current before-dev status is in_progress or review
-- Tasks are low-coupling (different files/modules, no write conflicts)
-- L0/L1 tasks dominate (L2 tasks recommended for step-by-step confirmation)
+仅在以下条件全部满足时启动：
 
-**Not applicable when**:
-- Tasks are L2 (step-by-task review recommended)
-- Tasks have dependencies or write conflicts
-- This is a first-time exploratory implementation (implementation path is uncertain)
-- The user has not explicitly requested batch mode
+1. 用户明确批准计划并要求自动连续执行。
+2. parent task 与所有叶子任务已建立有效 task graph。
+3. 当前会话是 main/coordinator，不是 worker 或 delegated subagent。
+4. Host 能执行 task、subagent 和 Git 动作。
 
-## Startup Conditions
+启动命令：
 
+```bash
+./.cowork-flow/run task start <parent-task> --auto --approved
 ```
-User: "approved" + "auto"
-  -> agent checks:
-     1. before-dev status = in_progress / review
-     2. implement.jsonl exists, non-empty, every line is valid JSON
-     3. user explicitly approved
+
+命令返回完整 Batch 状态，其中 `next_action` 是唯一允许执行的下一步。
+
+## Host Action 循环
+
+每次按以下顺序处理：
+
+1. 读取 `next_action`，核对 `action_id`、`type`、`task` 和 `task_dir`。
+2. 只执行该动作，不提前执行后续阶段。
+3. 将结果写入 UTF-8 JSON 文件。
+4. 回写结果：
+
+```bash
+./.cowork-flow/run task batch-record-result <batch-id> --file <result.json>
+```
+
+5. 读取新状态；若为 `awaiting_host`，继续新的 `next_action`；若为 `paused`，
+   停止后续任务。
+
+## Action 类型
+
+### `start_task`
+
+运行真实任务启动命令并通过 readiness/spec/TDD Gate：
+
+```bash
+./.cowork-flow/run task start <task_dir>
+```
+
+成功结果必须包含：
+
+```json
+{
+  "action_id": "<action-id>",
+  "type": "start_task",
+  "outcome": "success",
+  "task_status": "in_progress"
+}
 ```
 
-## Batch Loop
+状态机同时读取 `task.json`，仅相信真实的 `in_progress` 状态。
 
+### `init_implement_context` / `init_check_context`
+
+按 action 中的 `role`、`agent_type`、`task_dir` 和 `title` 运行：
+
+```bash
+./.cowork-flow/run subagent init \
+  --role <role> \
+  --agent-type <agent_type> \
+  --execution-task-dir <task_dir> \
+  --title "<title>"
 ```
-for task in implement.jsonl:
-  1. task start <task>  (full readiness gate, includes L2 doubt-review)
-  2. dispatch cowork-implement
-  3. dispatch cowork-check
-  4. if check passes: git commit + task review + task complete
-  5. if check fails: cowork-implement fix (up to 3 retries)
-  6. on triggering any of 5 safety valves -> pause and report
+
+Host 必须使用返回的 `cowork_runtime_context_id` 与
+`cowork_host_context_key` 派发对应 worker，并让 worker 首步执行
+`subagent bind`。
+
+初始化结果必须回写：
+
+```json
+{
+  "action_id": "<action-id>",
+  "type": "init_implement_context",
+  "outcome": "success",
+  "runtime_context_id": "<runtime-context-id>",
+  "host_context_key": "<host-context-key>"
+}
 ```
 
-## 5 Safety Valves (Pause Conditions)
+检查阶段将 `type` 改为 `init_check_context`。
+
+### `await_implement_result` / `await_check_result`
+
+等待对应 worker 完成，验证输出属于当前任务且 runtime context 已绑定到预期 Host。
 
-Any single condition below triggers a **pause**; do not proceed to the next task:
+成功结果必须包含 action 中相同的 `runtime_context_id` 和
+`host_context_key`。状态机验证 `status=bound` 后关闭 runtime context；
+如果关闭成功但 Batch checkpoint 尚未落盘，重复回写仍可恢复。
 
-1. **TDD gate failure**: any task's tdd.jsonl evidence is invalid or missing
-2. **Check gate failure**: any task's check.jsonl has an unresolved blocker (after 3 retries)
-3. **Test/build breakage**: `git diff` introduces conflicts inconsistent with R-AG-005
-4. **3 retries still failing**: the same task's implement + check loop has not passed after 3 rounds
-5. **L2 doubt-review blocker**: an L2 decision has substantive unresolved doubt findings not reconciled
+### `review_task`
 
-When paused, output:
+运行：
 
+```bash
+./.cowork-flow/run task review <task_dir>
 ```
-## Batch Mode Paused
 
-Task: <task-name>
-Reason: <specific cause>
-Current state: <task status + last command output>
+成功结果的 `task_status` 必须为 `review`，状态机还会读取真实 `task.json`。
+
+### `complete_task`
+
+运行：
+
+```bash
+./.cowork-flow/run task complete <task_dir>
+```
+
+成功结果的 `task_status` 必须为 `completed`，状态机还会读取真实 `task.json`。
+
+### `commit_task`
+
+只提交当前任务已验证的改动，并回写真实 commit id：
 
-Options:
-1. Skip this task -> mark as skipped, proceed to next
-2. Manual takeover -> exit batch, user resumes manually
-3. Abort -> exit batch, all already-committed tasks remain intact
+```json
+{
+  "action_id": "<action-id>",
+  "type": "commit_task",
+  "outcome": "success",
+  "commit_id": "<git-commit-id>"
+}
 ```
 
-## Post-Batch Verification
+状态机使用 Git 验证该对象确实是 commit；空值、占位字符串或不存在的 commit
+都会暂停。
 
-After all tasks complete (or after skips/aborts), run once:
+## 失败与恢复
 
-1. **Full test suite**: `python -m pytest` / `npm test` / project-defined verification command
-2. **git log audit**: confirm each task has an independent commit with a message reflecting the task
-3. **Spec sync check**: confirm no remaining spec synchronization needs
-4. **Final report**:
+Host 不可用或任一动作失败时，回写非 success 结果：
 
+```json
+{
+  "action_id": "<action-id>",
+  "type": "<action-type>",
+  "outcome": "failure",
+  "detail": "<specific cause>"
+}
 ```
-## Batch Mode Report
 
-- Tasks completed: N
-- Tasks skipped: M (reasons: ...)
-- Total commits: K
-- Issues found: ...
+状态会变为 `paused`，失败任务与所有后续任务不会被标记 completed。
 
-### Per-Task Summary
+修复原因后运行：
 
-| task | commits | duration | issues |
-|------|---------|----------|--------|
-| ...  | ...     | ...      | ...    |
+```bash
+./.cowork-flow/run task batch-resume <batch-id>
 ```
 
-## Relationship With Existing Systems
+恢复会生成新的 `action_id`，但保留已完成任务、阶段、runtime 证据和 commit。
+不要跳过失败任务，不要手工修改 Batch 状态文件。
 
-- writing-plans -> generates implement.jsonl (input)
-- task start -> unchanged (each task has its own readiness gate)
-- cowork-implement -> unchanged (dispatch one task per call)
-- cowork-check -> unchanged (check one task per call)
-- doubt-review -> auto-triggered for L2 tasks
-- Party Mode -> does not participate in batch mode (advisory in nature)
+## 完成验证
 
-## Relationship With Before-Dev Gate
+Batch 状态变为 `completed` 后：
 
-Batch mode can only start when before-dev status is in_progress.
-Before entering batch mode, the main session confirms:
-- before-dev status = in_progress / review
-- implement.jsonl exists and is non-empty
-- the user explicitly said "approved" at the end of writing-plans
+1. 运行项目完整测试与构建命令。
+2. 核对 `completed_tasks`、`task_phases` 与 `commits` 一一对应。
+3. 核对每个叶子任务都有独立 commit。
+4. 运行 spec sync、doctor 和发布前检查。

package/template/skills/brainstorming/SKILL.md

@@ -5,7 +5,7 @@ description: Use when requirements are unclear, a requested change has multiple
 
 # Brainstorming
 
-Use this skill as the active clarification gate for new requirements. Turn an idea into a clear change request before PRD, planning, fixed-agent dispatch, or code changes begin.
+Use this skill as the active clarification gate for new requirements. Turn an idea into a clear change request before decision-anchor, planning, fixed-agent dispatch, or code changes begin.
 
 ## Flow
 
@@ -13,7 +13,7 @@ Use this skill as the active clarification gate for new requirements. Turn an id
 2. State the goal, non-goals, assumptions, scope boundary, success criteria, and the smallest useful scope.
 3. Ask one high-value question only when the answer cannot be inferred safely; otherwise proceed with explicit assumptions.
 4. Present 2-3 viable approaches when trade-offs matter, with a concrete recommended direction.
-5. Do not write PRD, planning, or fixed-agent dispatch input until the direction and acceptance criteria are clear.
+5. Do not write decision-anchor, planning, or fixed-agent dispatch input until the direction and acceptance criteria are clear.
 6. For L1/L2 work, create or update the change/task artifacts required by `.cowork-flow/workflow.md` after the clarification output is stable.
 7. Hand off to `writing-plans` when the requested behavior and acceptance criteria are clear.
 

package/template/skills/cowork-flow/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: cowork-flow
+description: Route cowork-flow work through one authoritative workflow entry. Use for starting, resuming, implementing, reviewing, debugging, discussing, or finishing repository work when workflow state and the next allowed operation must be resolved.
+---
+
+# Cowork Flow
+
+Use this Skill as the only public workflow router. Do not reproduce lifecycle
+rules from other Skills.
+
+## Resolve State
+
+1. Use the injected `<workflow-state>` when present.
+2. If state is absent, run `./.cowork-flow/run task next --json` exactly once.
+3. Treat `status`, `allowedOperations`, `requiredArtifacts`,
+   `recommendedSkill`, `internalProtocols`, and `blockers` as authoritative.
+4. Stop repository mutations when blockers exclude the requested operation.
+
+## Classify Intent
+
+Classify the request into exactly one intent:
+
+- `question`: answer or explain without changing repository state.
+- `clarify`: refine goals, boundaries, or acceptance criteria.
+- `plan`: create or revise an executable plan.
+- `implement`: change code or task artifacts.
+- `review`: verify implementation or complete review gates.
+- `debug`: diagnose a failure or repeated unsuccessful attempt.
+- `discuss`: compare options without advancing task state.
+- `batch`: request automated execution of a task graph.
+
+For `question`, answer directly when `answer_questions` is allowed. Do not load
+implementation or review protocols.
+
+## Route
+
+Use the active public Registry entry whose status and intent match the request.
+Select at most one public Skill. If there is no match, follow the allowed
+operation directly or report the blocker; never guess a second workflow entry.
+
+Load only the protocols listed in `internalProtocols`. These protocols refine
+execution but are not public alternatives and cannot override Runtime Gates.

package/template/skills/party-mode/SHARED-BOUNDARIES.md

@@ -1,6 +1,6 @@
 # Shared Boundaries
 
-These boundaries apply to both Party Mode and Party Mode V2.
+These boundaries apply to Party Mode runtime-board discussions.
 
 - This skill is advisory only.
 - It cannot mutate task status, start/review/complete/archive tasks, add sessions, commit, push, or satisfy formal workflow gates.