cowork-flow 0.0.3 → 0.0.5

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 fisklikewater
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -28,6 +28,7 @@ cowork-flow 是一个用于新项目初始化协作流程的模板仓库。它
     └── .cowork-flow/
         ├── config.yaml
         ├── workflow.md
+        ├── agent-team/
         ├── scripts/
         ├── spec/
         ├── changes/
@@ -56,6 +57,9 @@ cowork-flow 是一个用于新项目初始化协作流程的模板仓库。它
 `template/.cowork-flow/plans/`
 保存可执行步骤、验证方式和执行状态。
 
+`template/.cowork-flow/agent-team/`
+保存 agent team 的项目级 registry、适配器和策略。默认适配器是 `codex`，由主 agent 调度 Codex 子 agent；没有子 agent 能力时可退回 `manual` 提示词模式。
+
 ## 快速开始
 
 使用 CLI 把模板内容安装到目标项目根目录：
@@ -132,39 +136,64 @@ cowork-flow sync . --dry-run
 
 ## 常用入口
 
+模板内置统一入口来运行 Python 工作流脚本：
+
+- macOS / Linux / Git Bash / WSL：`./.cowork-flow/run`
+- Windows cmd / PowerShell：`.\.cowork-flow\run.cmd`
+
+入口会按 `COWORK_FLOW_PYTHON`、`PYTHON`、`python3`、`python`、`py -3`
+的顺序查找 Python 3.8+ 解释器，避免不同环境中 `python` / `python3`
+命令不一致的问题。
+
+下面示例使用 macOS / Linux 写法；Windows 原生命令行中把
+`./.cowork-flow/run` 替换为 `.\.cowork-flow\run.cmd`。
+
 初始化或查看开发者身份：
 
 ```bash
-python3 ./.cowork-flow/scripts/get_developer.py
-python3 ./.cowork-flow/scripts/init_developer.py <developer-name>
+./.cowork-flow/run get-developer
+./.cowork-flow/run init-developer <developer-name>
 ```
 
 查看当前上下文：
 
 ```bash
-python3 ./.cowork-flow/scripts/get_context.py
-python3 ./.cowork-flow/scripts/task.py list
+./.cowork-flow/run get-context
+./.cowork-flow/run task list
 ```
 
 创建并验证行为变更：
 
 ```bash
-python3 ./.cowork-flow/scripts/change.py create <slug>
-python3 ./.cowork-flow/scripts/change.py validate <slug>
+./.cowork-flow/run change create <slug>
+./.cowork-flow/run change validate <slug>
 ```
 
 创建并启动任务：
 
 ```bash
-python3 ./.cowork-flow/scripts/task.py create "<title>" --slug <task-name>
-python3 ./.cowork-flow/scripts/task.py start <task-dir>
+./.cowork-flow/run task create "<title>" --slug <task-name>
+./.cowork-flow/run task start <task-dir>
 ```
 
+执行 plan 时准备 agent team：
+
+默认 `agent_team.enabled: false`。运行 `agent-team prepare/status/next/record-result/record-review/retry/complete` 前，先在 `.cowork-flow/config.yaml` 中设置 `agent_team.enabled: true`。
+
+```bash
+./.cowork-flow/run agent-team init
+./.cowork-flow/run agent-team prepare <task-dir> --plan <plan-file>
+./.cowork-flow/run agent-team next <task-dir>
+./.cowork-flow/run agent-team complete <task-dir>
+```
+
+`agent-team` 命令会生成任务目录内的 dispatch plan、assignments、状态、审阅和 metrics 工件。默认 `codex` 适配器采用主 agent 调度型：脚本生成 Codex-ready 分派文件，主 agent 负责调用子 agent、协调并回写结果。
+
 记录 session：
 
 ```bash
-python3 ./.cowork-flow/scripts/get_context.py --mode record
-python3 ./.cowork-flow/scripts/add_session.py \
+./.cowork-flow/run get-context --mode record
+./.cowork-flow/run add-session \
   --title "<session-title>" \
   --commit "<commit-or-handoff-ref>" \
   --summary "<summary>"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cowork-flow",
-  "version": "0.0.3",
+  "version": "0.0.5",
   "description": "CLI for installing and maintaining cowork-flow collaboration templates.",
   "type": "module",
   "bin": {
@@ -10,12 +10,14 @@
     "bin",
     "src",
     "template",
-    "README.md"
+    "README.md",
+    "!template/**/__pycache__/**",
+    "!template/**/*.pyc"
   ],
   "scripts": {
     "test": "node --test",
-    "test:template": "python3 -m unittest discover tests -v",
-    "pack:check": "npm_config_cache=/tmp/cowork-flow-npm-cache npm pack --dry-run --json",
+    "test:template": "node scripts/run-template-tests.js",
+    "pack:check": "node scripts/pack-check.js",
     "test:all": "npm test && npm run test:template && npm run pack:check"
   },
   "engines": {

package/src/lib/copy-template.js

@@ -1,5 +1,5 @@
 import { constants } from 'node:fs';
-import { access, copyFile, mkdir, readFile, readdir, writeFile } from 'node:fs/promises';
+import { access, chmod, copyFile, mkdir, readFile, readdir, stat, writeFile } from 'node:fs/promises';
 import { dirname, join, relative } from 'node:path';
 
 import { templateRoot } from './paths.js';
@@ -90,9 +90,7 @@ export async function buildSuperpowersPlan(targetDir, options = {}) {
 }
 
 const PROTECTED_SYNC_FILES = new Set([
-  'AGENTS.md',
-  '.cowork-flow/config.yaml',
-  '.cowork-flow/workflow.md'
+  '.cowork-flow/config.yaml'
 ]);
 
 const PROTECTED_SYNC_PREFIXES = [
@@ -105,26 +103,30 @@ const PROTECTED_SYNC_PREFIXES = [
 
 const SAFE_SYNC_PREFIXES = [
   '.agent/skills/',
-  '.cowork-flow/scripts/'
+  '.cowork-flow/'
 ];
 
 const SAFE_SYNC_FILES = new Set([
   '.cowork-flow/.gitignore',
-  '.cowork-flow/.version'
+  '.cowork-flow/.version',
+  '.cowork-flow/run',
+  '.cowork-flow/run.cmd'
 ]);
 
 const COWORK_FLOW_START = '<!-- COWORK-FLOW:START -->';
 const COWORK_FLOW_END = '<!-- COWORK-FLOW:END -->';
 
 function isProtectedSyncFile(relativePath) {
-  return PROTECTED_SYNC_FILES.has(relativePath)
-    || PROTECTED_SYNC_PREFIXES.some((prefix) => relativePath.startsWith(prefix));
+  const templatePath = toTemplatePath(relativePath);
+  return PROTECTED_SYNC_FILES.has(templatePath)
+    || PROTECTED_SYNC_PREFIXES.some((prefix) => templatePath.startsWith(prefix));
 }
 
 function isSafeSyncFile(relativePath) {
-  return SAFE_SYNC_FILES.has(relativePath)
-    || SAFE_SYNC_PREFIXES.some((prefix) => relativePath.startsWith(prefix))
-    || relativePath.endsWith('/.gitkeep');
+  const templatePath = toTemplatePath(relativePath);
+  return SAFE_SYNC_FILES.has(templatePath)
+    || SAFE_SYNC_PREFIXES.some((prefix) => templatePath.startsWith(prefix))
+    || templatePath.endsWith('/.gitkeep');
 }
 
 function replaceManagedBlock(targetContent, templateContent) {
@@ -242,6 +244,8 @@ export async function applyPlan(actions, options = {}) {
       await writeFile(item.destination, item.content, 'utf8');
     } else {
       await copyFile(item.source, item.destination);
+      const sourceStats = await stat(item.source);
+      await chmod(item.destination, sourceStats.mode & 0o777);
     }
   }
 }

package/src/lib/package-info.js

@@ -31,9 +31,14 @@ export function compareVersions(left, right) {
   return 0;
 }
 
+export function npmCommandOptions(platform = process.platform) {
+  return platform === 'win32' ? { shell: true } : {};
+}
+
 export async function fetchLatestVersion(packageName = 'cowork-flow') {
   const result = await execFileAsync('npm', ['view', packageName, 'version'], {
-    encoding: 'utf8'
+    encoding: 'utf8',
+    ...npmCommandOptions()
   });
   return result.stdout.trim();
 }
@@ -41,7 +46,8 @@ export async function fetchLatestVersion(packageName = 'cowork-flow') {
 export async function runGlobalInstall(packageSpec = 'cowork-flow@latest') {
   return new Promise((resolvePromise, rejectPromise) => {
     const child = spawn('npm', ['install', '-g', packageSpec], {
-      stdio: 'inherit'
+      stdio: 'inherit',
+      ...npmCommandOptions()
     });
     child.on('error', rejectPromise);
     child.on('close', (code) => resolvePromise(code ?? 1));

package/template/.agent/skills/agent-team-execution/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: agent-team-execution
+description: Use when executing an approved implementation plan with independent tasks, multiple agents, or an explicit request to use agent team execution
+---
+
+# Agent Team Execution
+
+Use this skill after a task is active and an approved `.cowork-flow/plans/*.md` file is in task context.
+
+## Process
+
+1. Run `./.cowork-flow/run agent-team prepare <task-dir> --plan <plan-file>`.
+2. Review `agent-team/dispatch-plan.yaml` for unsafe parallelism, file conflicts, missing context, or weak agent matches.
+3. Run `./.cowork-flow/run agent-team next <task-dir>` to get ready assignments.
+4. In Codex, dispatch the ready assignments to the recommended agent types. Tell each worker it is not alone in the codebase, must respect the write boundary, must not revert others' edits, and must list changed files.
+5. While workers run, coordinate: answer questions, unblock context gaps, and integrate non-conflicting results.
+6. Record outputs with `record-result` and reviews with `record-review`.
+7. Use `retry` only after adding missing context, changing agent choice, or splitting an oversized assignment.
+8. Run `complete` before claiming the agent team work is done.
+
+## Rules
+
+- The script suggests; the main agent decides.
+- Do not parallelize assignments with overlapping write files.
+- Do not skip spec review or quality review.
+- Do not rely on chat history for state; write results through `agent-team` commands.

package/template/{.superpowers → .agent/skills}/brainstorming/SKILL.md

@@ -110,7 +110,7 @@ digraph brainstorming {
 
 - Write the validated change artifacts under `.cowork-flow/changes/<slug>/`
   - `proposal.md` explains why the behavior should change
-  - `specs/.../spec.md` defines external behavior and acceptance criteria
+  - `spec.md` defines external behavior and acceptance criteria
   - `design.md` records important design trade-offs for L2 work
   - (User preferences for spec location override this default)
 - Use elements-of-style:writing-clearly-and-concisely skill if available

package/template/.agent/skills/record-session/SKILL.md

@@ -24,7 +24,7 @@ Do not archive a task while the plan file still shows stale progress.
 ### Step 1: Get Context & Check Tasks
 
 ```bash
-python3 ./.cowork-flow/scripts/get_context.py --mode record
+./.cowork-flow/run get-context --mode record
 ```
 
 [!] Archive tasks whose work is **actually done** — judge by work status, not the `status` field in task.json:
@@ -33,20 +33,20 @@ python3 ./.cowork-flow/scripts/get_context.py --mode record
 - Don't skip archiving just because `status` still says `planning` or `in_progress`
 
 ```bash
-python3 ./.cowork-flow/scripts/task.py archive <task-name>
+./.cowork-flow/run task archive <task-name>
 ```
 
 ### Step 2: One-Click Add Session
 
 ```bash
 # Method 1: Simple parameters
-python3 ./.cowork-flow/scripts/add_session.py \
+./.cowork-flow/run add-session \
   --title "Session Title" \
   --commit "hash1,hash2" \
   --summary "Brief summary of what was done"
 
 # Method 2: Pass detailed content via stdin
-cat << 'EOF' | python3 ./.cowork-flow/scripts/add_session.py --title "Title" --commit "hash"
+cat << 'EOF' | ./.cowork-flow/run add-session --title "Title" --commit "hash"
 | Feature | Description |
 |---------|-------------|
 | Change | Description |
@@ -72,7 +72,7 @@ EOF
 
 | Command | Purpose |
 |---------|---------|
-| `python3 ./.cowork-flow/scripts/get_context.py --mode record` | Get context for record-session |
-| `python3 ./.cowork-flow/scripts/add_session.py --title "..." --commit "..."` | **One-click add session (recommended)** |
-| `python3 ./.cowork-flow/scripts/task.py archive <name>` | Archive completed task (auto-commits) |
-| `python3 ./.cowork-flow/scripts/task.py list` | List active tasks |
+| `./.cowork-flow/run get-context --mode record` | Get context for record-session |
+| `./.cowork-flow/run add-session --title "..." --commit "..."` | **One-click add session (recommended)** |
+| `./.cowork-flow/run task archive <name>` | Archive completed task (auto-commits) |
+| `./.cowork-flow/run task list` | List active tasks |

package/template/.agent/skills/start/SKILL.md

@@ -44,13 +44,17 @@ cat AGENTS.md
 - Best practices
 - Project-specific collaboration and documentation rules
 
+Command examples use macOS / Linux / Git Bash / WSL syntax. In native Windows
+cmd or PowerShell, replace `./.cowork-flow/run <command>` with
+`.\.cowork-flow\run.cmd <command>`.
+
 > **Important**:
 > Reusable skills are already part of the template. During project onboarding, put project-specific facts in `AGENTS.md`, `.cowork-flow/workflow.md`, `.cowork-flow/config.yaml`, and `.cowork-flow/spec/` rather than editing `SKILL.md`.
 
 ### Step 2: Get Current Context
 
 ```bash
-python3 ./.cowork-flow/scripts/resume.py
+./.cowork-flow/run resume
 ```
 
 This shows: developer identity, git status, current task (if any), active tasks, and
@@ -108,9 +112,9 @@ Before entering Task Workflow, classify the change as `L0` / `L1` / `L2` using `
 
 - `L0`: No external behavior change. Continue with the existing Task Workflow.
 - `L1`: Behavior change in a bounded module. Do **not** go straight to PRD/Research. First run:
-  1. `python3 ./.cowork-flow/scripts/change.py create <slug>`
+  1. `./.cowork-flow/run change create <slug>`
   2. `superpowers:brainstorming` to create or complete `proposal/spec`
-  3. `python3 ./.cowork-flow/scripts/change.py validate <slug>`
+  3. `./.cowork-flow/run change validate <slug>`
   4. `superpowers:writing-plans` to produce the implementation plan
 - `L2`: Same as `L1`, plus required `design.md`. Multi-perspective review happens after implementation in the review gate.
 
@@ -217,7 +221,7 @@ If unclear, ask clarifying questions.
 **Step 2: Create Task Directory** `[AI]`
 
 ```bash
-TASK_DIR=$(python3 ./.cowork-flow/scripts/task.py create "<title>" --slug <name>)
+TASK_DIR=$(./.cowork-flow/run task create "<title>" --slug <name>)
 ```
 
 **Step 3: Write PRD** `[AI]`
@@ -290,7 +294,7 @@ Use this output format:
 Initialize default context:
 
 ```bash
-python3 ./.cowork-flow/scripts/task.py init-context "$TASK_DIR" <type>
+./.cowork-flow/run task init-context "$TASK_DIR" <type>
 # type: backend | frontend | fullstack
 ```
 
@@ -298,25 +302,25 @@ Add specs found in your research pass:
 
 ```bash
 # For each relevant spec and code pattern:
-python3 ./.cowork-flow/scripts/task.py add-context "$TASK_DIR" implement "<path>" "<reason>"
-python3 ./.cowork-flow/scripts/task.py add-context "$TASK_DIR" check "<path>" "<reason>"
+./.cowork-flow/run task add-context "$TASK_DIR" implement "<path>" "<reason>"
+./.cowork-flow/run task add-context "$TASK_DIR" check "<path>" "<reason>"
 ```
 
 If this task came through the Behavior Change Gate, add the approved artifacts before coding:
 
 ```bash
-python3 ./.cowork-flow/scripts/task.py add-context "$TASK_DIR" implement ".cowork-flow/changes/<slug>/proposal.md" "Approved change proposal"
-python3 ./.cowork-flow/scripts/task.py add-context "$TASK_DIR" implement ".cowork-flow/changes/<slug>/specs/.../spec.md" "Approved behavior spec"
-python3 ./.cowork-flow/scripts/task.py add-context "$TASK_DIR" implement ".cowork-flow/changes/<slug>/design.md" "Approved design for L2 changes"
-python3 ./.cowork-flow/scripts/task.py add-context "$TASK_DIR" implement ".cowork-flow/plans/YYYY-MM-DD-<slug>.md" "Approved implementation plan"
-python3 ./.cowork-flow/scripts/task.py add-context "$TASK_DIR" check ".cowork-flow/changes/<slug>/specs/.../spec.md" "Check implementation against approved spec"
-python3 ./.cowork-flow/scripts/task.py add-context "$TASK_DIR" check ".cowork-flow/plans/YYYY-MM-DD-<slug>.md" "Check implementation against approved plan"
+./.cowork-flow/run task add-context "$TASK_DIR" implement ".cowork-flow/changes/<slug>/proposal.md" "Approved change proposal"
+./.cowork-flow/run task add-context "$TASK_DIR" implement ".cowork-flow/changes/<slug>/spec.md" "Approved behavior spec"
+./.cowork-flow/run task add-context "$TASK_DIR" implement ".cowork-flow/changes/<slug>/design.md" "Approved design for L2 changes"
+./.cowork-flow/run task add-context "$TASK_DIR" implement ".cowork-flow/plans/YYYY-MM-DD-<slug>.md" "Approved implementation plan"
+./.cowork-flow/run task add-context "$TASK_DIR" check ".cowork-flow/changes/<slug>/spec.md" "Check implementation against approved spec"
+./.cowork-flow/run task add-context "$TASK_DIR" check ".cowork-flow/plans/YYYY-MM-DD-<slug>.md" "Check implementation against approved plan"
 ```
 
 **Step 7: Activate Task** `[AI]`
 
 ```bash
-python3 ./.cowork-flow/scripts/task.py start "$TASK_DIR"
+./.cowork-flow/run task start "$TASK_DIR"
 ```
 
 This sets `.current-task` so hooks can inject context.
@@ -332,6 +336,7 @@ Implement the task described in `prd.md`.
 - Follow all specs injected into implement context
 - Keep changes scoped to requirements
 - Run the project verification commands from `AGENTS.md` or `.cowork-flow/config.yaml` before finishing
+- If executing an approved plan with independent work, use `agent-team-execution`: run `agent-team prepare`, review the dispatch plan, use `agent-team next` for ready assignments, and finish with `agent-team complete`.
 
 **Step 9: Check Quality** `[AI]`
 
@@ -369,10 +374,10 @@ If yes, resume from the appropriate step (usually Step 7 or 8).
 When a conversation has many rounds, a task runs for a long time, or context was
 compressed, resume with the smallest useful context:
 
-1. Run `python3 ./.cowork-flow/scripts/resume.py`.
+1. Run `./.cowork-flow/run resume`.
 2. Follow the `RESUME CHECKLIST` section.
 3. Read the current task `prd.md`.
-4. Run `python3 ./.cowork-flow/scripts/task.py list-context <task-dir>` and read only the jsonl references needed for the current phase.
+4. Run `./.cowork-flow/run task list-context <task-dir>` and read only the jsonl references needed for the current phase.
 5. If a plan is listed, read its current execution status before continuing implementation.
 
 Do not bulk-read `.cowork-flow/spec/`, all plans, all tasks, or workspace journals
@@ -395,14 +400,14 @@ anchor, then load details on demand.
 
 | Script | Purpose |
 |--------|---------|
-| `python3 ./.cowork-flow/scripts/resume.py` | Resume session with minimal context checklist |
-| `python3 ./.cowork-flow/scripts/get_context.py` | Get session context |
-| `python3 ./.cowork-flow/scripts/task.py create` | Create task directory |
-| `python3 ./.cowork-flow/scripts/task.py init-context` | Initialize jsonl files |
-| `python3 ./.cowork-flow/scripts/task.py add-context` | Add spec to jsonl |
-| `python3 ./.cowork-flow/scripts/task.py start` | Set current task |
-| `python3 ./.cowork-flow/scripts/task.py finish` | Clear current task |
-| `python3 ./.cowork-flow/scripts/task.py archive` | Archive completed task |
+| `./.cowork-flow/run resume` | Resume session with minimal context checklist |
+| `./.cowork-flow/run get-context` | Get session context |
+| `./.cowork-flow/run task create` | Create task directory |
+| `./.cowork-flow/run task init-context` | Initialize jsonl files |
+| `./.cowork-flow/run task add-context` | Add spec to jsonl |
+| `./.cowork-flow/run task start` | Set current task |
+| `./.cowork-flow/run task finish` | Clear current task |
+| `./.cowork-flow/run task archive` | Archive completed task |
 
 ### Workflow Phases `[AI]`
 

package/template/.cowork-flow/.version

@@ -1 +1 @@
-0.0.3
+0.0.5

package/template/.cowork-flow/agent-team/adapters.yaml

@@ -0,0 +1,15 @@
+# Agent Team Adapters
+
+default: codex
+fallback: manual
+
+adapters:
+  codex:
+    mode: coordinator-dispatched
+    description: 主 agent 使用 Codex 子 agent 工具执行脚本生成的 assignments。
+    output_file: adapters/codex.json
+
+  manual:
+    mode: prompt-only
+    description: 生成可复制的 assignment prompt，由人或其他宿主执行并回写结果。
+    output_file: adapters/manual.json

package/template/.cowork-flow/agent-team/agents.yaml

@@ -0,0 +1,68 @@
+# Agent Team Registry
+# Project teams may customize this file after initialization.
+
+default_adapter: codex
+
+agents:
+  implementer:
+    codex_type: worker
+    capabilities:
+      - implementation
+      - test-writing
+    preferred_task_types:
+      - code
+      - test
+    file_patterns:
+      - "src/**"
+      - "template/**"
+      - "tests/**"
+      - "test/**"
+    risk_limits:
+      max_parallel_write_conflicts: 0
+
+  spec-reviewer:
+    codex_type: default
+    capabilities:
+      - spec-review
+      - acceptance-check
+    preferred_task_types:
+      - review
+      - documentation
+    file_patterns:
+      - ".cowork-flow/changes/**"
+      - ".cowork-flow/plans/**"
+      - "README.md"
+      - "template/**"
+    risk_limits:
+      max_parallel_write_conflicts: 0
+
+  quality-reviewer:
+    codex_type: default
+    capabilities:
+      - code-quality-review
+      - test-review
+    preferred_task_types:
+      - review
+      - verification
+    file_patterns:
+      - "src/**"
+      - "template/**"
+      - "tests/**"
+      - "test/**"
+    risk_limits:
+      max_parallel_write_conflicts: 0
+
+  docs-agent:
+    codex_type: worker
+    capabilities:
+      - documentation
+      - workflow-writing
+    preferred_task_types:
+      - docs
+    file_patterns:
+      - "README.md"
+      - "AGENTS.md"
+      - ".cowork-flow/**/*.md"
+      - ".agent/skills/**"
+    risk_limits:
+      max_parallel_write_conflicts: 0

package/template/.cowork-flow/agent-team/policy.yaml

@@ -0,0 +1,23 @@
+# Agent Team Policy
+
+parallel:
+  allow_parallel_batches: true
+  disallow_file_write_conflicts: true
+  require_coordinator_review: true
+
+reviews:
+  require_spec_review: true
+  require_quality_review: true
+  chain:
+    - implementer
+    - spec-reviewer
+    - quality-reviewer
+
+retry:
+  max_attempts: 3
+  retry_on:
+    - needs_context
+    - failed_verification
+    - review_rejected
+    - adapter_failed
+  escalation: needs-coordinator-decision

package/template/.cowork-flow/config.yaml

@@ -14,6 +14,15 @@ session_commit_message: "chore: record journal"
 # Maximum lines per journal file before rotating to a new one
 max_journal_lines: 2000
 
+#-------------------------------------------------------------------------------
+# Agent Team Runtime
+#-------------------------------------------------------------------------------
+
+# Disabled by default. Set to true before using agent-team runtime commands such
+# as prepare/status/next/record-result/record-review/retry/complete.
+agent_team:
+  enabled: false
+
 #-------------------------------------------------------------------------------
 # Task Lifecycle Hooks
 #-------------------------------------------------------------------------------