@xulthekl/team-flow 0.24.0 → 0.25.1

package/.claude/always/phase-guard.md

@@ -1,3 +1,3 @@
-# team-flow v0.24.0 | 阶段: {{state}} | 工作流: {{workflow}}
+# team-flow v0.25.1 | 阶段: {{state}} | 工作流: {{workflow}}
 当前阶段允许的操作由 workflow-start 路由规则定义。
 禁止跨越 DP gate 进入下一阶段。变更范围以 execution-contract.md 的 Intent Lock 为准。

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
     {
       "name": "team-flow",
       "description": "8-state spec workflow + compound global compounding + architecture-design (4A/DDD) + local HTML prototype + product-level orchestration + bootstrap + e2e + session handoff + workflow feedback. 23 skills + 8 agents with embedded TDD, SDD, code review, debugging, delta spec sync, and design-system-driven prototyping.",
-      "version": "0.24.0",
+      "version": "0.25.1",
       "source": "./",
       "author": {
         "name": "LT",

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.24.0",
+  "version": "0.25.1",
   "description": "Unified workflow plugin: team-flow (spec-driven dev: TDD/SDD/code-review/debugging) + compound-engineering core subset (brainstorm/plan/compound/strategy/ideate/proof, global compounding) + architecture-design (4A+DDD incremental design & global compounding) + prototype (local HTML prototype, zero external deps) + e2e (Playwright E2E, AC-driven) + workflow-orchestrator (product-level workflow orchestration) + workflow-bootstrap (existing project onboarding) + session-handoff (context transfer) + workflow-feedback (issue tracking). 23 skills + 8 agents, one install.",
   "source": "./",
   "author": {

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.24.0",
+  "version": "0.25.1",
   "description": "Spec-first workflow that bridges OpenSpec-style planning and Superpowers-style execution discipline.",
   "author": {
     "name": "MageByte",

package/.cursor-plugin/marketplace.json

@@ -5,7 +5,7 @@
   },
   "metadata": {
     "description": "Unified workflow plugin marketplace for Cursor (team-flow: team-flow + compound + architecture-design + prototype).",
-    "version": "0.24.0"
+    "version": "0.25.1"
   },
   "plugins": [
     {

package/.cursor-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "team-flow",
   "displayName": "team-flow",
   "description": "Unified workflow plugin: team-flow (spec-driven dev: TDD/SDD/code-review/debugging) + compound-engineering core subset (brainstorm/plan/compound/strategy/ideate/proof, global compounding) + architecture-design (4A+DDD incremental design & global compounding) + prototype (local HTML prototype, zero external deps) + e2e (Playwright E2E, AC-driven) + workflow-orchestrator (product-level workflow orchestration) + workflow-bootstrap (existing project onboarding) + session-handoff (context transfer) + workflow-feedback (issue tracking). 23 skills + 8 agents, one install.",
-  "version": "0.24.0",
+  "version": "0.25.1",
   "author": {
     "name": "LT",
     "url": "https://github.com/LT"

package/.github/plugin/marketplace.json

@@ -6,13 +6,13 @@
   },
   "metadata": {
     "description": "Unified workflow plugins and skills for AI coding agents (team-flow: team-flow + compound + architecture-design + prototype).",
-    "version": "0.24.0"
+    "version": "0.25.1"
   },
   "plugins": [
     {
       "name": "team-flow",
       "description": "Unified workflow with planning artifacts, execution contracts, TDD, review gates, systematic debugging, delta spec sync, architecture-design, and local HTML prototyping.",
-      "version": "0.24.0",
+      "version": "0.25.1",
       "source": ".",
       "author": {
         "name": "LT",

package/AGENTS.md

@@ -8,7 +8,7 @@
 
 - 零运行时依赖（team-flow 底座）
 - prototype 额外 **零外部依赖、可离线**（自包含 HTML + 页面内 Tweaks 控件，无 CDN）
-- 插件保持通用，所有风格由项目 `design-system.md` / `prd.template` 注入，不固化任何公司/产品风格
+- 插件保持通用，所有风格由项目 `design-system.md` / `prd.template`（含配套 `prd-brainstorm-profile.md`）注入，不固化任何公司/产品风格
 
 ### 身份与依赖关系
 
@@ -253,11 +253,11 @@ docs/solutions/
 
 项目 `team-flow.config.json` 可注入（**插件层扩展字段，非 team-flow 原生 schema**；原生仅 `artifacts.order` / `artifacts.skip`）：
 
-- `prd.template`：PRD 模板路径
+- `prd.template`：PRD 模板路径（默认 `templates/prd.md`，GTMC D7 业务要件 11 章结构）。ce-brainstorm Phase 0.0 首次运行时若未配置，会交互式询问用户选择默认模板或自定义路径，并自动写入配置。自定义模板应配套 brainstorm profile（`<模板名>-brainstorm-profile.md`），否则回退使用内置默认的 GTMC D7 profile
 - `prototype.designSystem`：项目 `design-system.md` 路径
 - `prototype.entry`：原型入口（默认 `prototype/index.html`）
 
-读取方式：`tf runtime config --get <key>`（插件层自读，字段命名避开原生 key 冲突）。
+读取方式：`tf runtime config --get <key>`（插件层自读，字段命名避开原生 key 冲突）。`prd.template` 已纳入 DEFAULTS（`config-loader.mjs`），未配置时返回默认值而非报错。
 
 ## Architecture（team-flow 底座，TypeScript）
 

package/CHANGELOG.md

@@ -6,6 +6,77 @@ The format loosely follows Keep a Changelog.
 
 ## [Unreleased]
 
+## [0.25.1] - 2026-07-29
+
+### Changed（SKILL.md 渐进式披露拆分，P1-9，3 项）
+
+#### ce-proof (346→88 行)
+- **skills/ce-proof/SKILL.md**：保留核心决策逻辑（Identity/Credentials/Publish Mode/Edit Strategy/Safety），curl 示例和工作流移入 references
+- **skills/ce-proof/references/api-recipes.md**（新增）：Create/Read/Edit/Presence/Title/Delete 的完整 curl 示例 + 错误码表 + Marks & Privacy + When the loop breaks
+- **skills/ce-proof/references/workflows.md**（新增）：Review/Create/Pull 三个完整工作流
+
+#### ce-brainstorm (458→122 行)
+- **skills/ce-brainstorm/SKILL.md**：保留核心原则 + 每个 Phase 摘要 + reference 引用指针
+- **skills/ce-brainstorm/references/output-format.md**（新增）：OUTPUT_FORMAT 5 级优先级解析逻辑
+- **skills/ce-brainstorm/references/phase0-routing.md**（新增）：Phase 0 的 Resume/Classify/Verdict/Assess/Scope/Spine/Iteration 详细路由
+- **skills/ce-brainstorm/references/prototype-loop.md**（新增）：Phase 3.5 原型内循环完整流程
+- **skills/ce-brainstorm/references/grounding.md**（新增）：Phase 1.1 上下文扫描 + grounding scout 提示词 + Slack 路由
+
+#### ce-ideate (402→85 行)
+- **skills/ce-ideate/SKILL.md**：保留核心原则 + Phase 摘要 + reference 引用指针
+- **skills/ce-ideate/references/phase0-scope.md**（新增）：Phase 0 完整路由逻辑（输出模式/主题门/模式分类/上下文门/聚焦与容量/成本透明）
+- **skills/ce-ideate/references/grounding.md**（新增）：Phase 1 模式感知 Grounding（仓库/非仓库调度 + Web 研究 + 用户研究工件 + 综合摘要）
+- **skills/ce-ideate/references/topic-surface.md**（新增）：Phase 1.5 主题表面分解（轴标准 + 证据侦察）
+
+## [0.25.0] - 2026-07-29
+
+### Added（brainstorm profile 机制，3 项）
+
+#### Brainstorm Profile 机制
+- **templates/prd-brainstorm-profile.md**（新增）：GTMC D7 模板的 brainstorm profile，定义核心思考维度（7 项：业务流程/状态模型/权限模型/用户角色/数据关系/业务规则/系统功能）、扩展维度（6 项：画面设计/业务术语/报表需求/交互机制/非功能性需求/编码规则）、反例边界（7 项：禁止后端模块划分/前端页面结构/数据库表设计/API 接口定义/技术选型/部署架构/代码结构）和正向示例
+- **skills/ce-brainstorm/references/prd-mapping.md**：新增"Brainstorm Profile 机制"完整说明（文件命名规则、查找优先级、三段结构、自定义 Profile 指南）
+- **skills/ce-brainstorm/references/brainstorm-sections.md**：新增"Brainstorm profile coverage check"段落，确保核心维度在 PRD 中被覆盖
+
+### Changed（Phase 0 模板选择 + Phase 2 profile 驱动，4 项）
+
+#### PRD 模板交互式选择
+- **skills/ce-brainstorm/SKILL.md Phase 0.0**：PRD 模板解析改为 MANDATORY STEP——必须执行 bash 命令检查配置，未配置自定义模板时强制使用 AskUserQuestion 询问用户选择默认或自定义路径，并自动写入 `team-flow.config.json`
+- **skills/ce-brainstorm/SKILL.md Phase 2**：新增"Load brainstorm profile"步骤，按 profile 维度约束方案探索；"Approach granularity"从"mechanism/product shape"改为"profile-driven product thinking, not architecture"
+- **skills/ce-brainstorm/SKILL.md 调用模式**：明确声明 `orchestrated` 模式仅跳过 Phase 3.5，Phase 0-3 均正常执行不可跳过
+
+#### Config 默认值
+- **scripts/lib/config-loader.mjs**：DEFAULTS 增加 `prd.template: 'templates/prd.md'`，`tf runtime config --get prd.template` 未配置时返回默认值而非报错
+
+### Documentation（1 项）
+
+- **AGENTS.md**：`prd.template` 配置字段说明扩充（含 brainstorm profile 关联说明）；通用性描述补充 profile 注入机制
+
+## [0.24.1] - 2026-07-28
+
+### Fixed（prototype skill 体系补强，5 项）
+
+#### P0: design-system-architect.md 重复维护
+- **prototype/references/agents/design-system-architect.md**: 替换为迁移指针，指向 `design-system skill` 下的权威版本，消除两份文件内容漂移风险
+
+#### P0: Open Design 命名歧义
+- **prototype/SKILL.md**: description 中明确标注 "Open Design 桌面应用"（GUI 工具，互斥项）与 "nexu-io/open-design 开源设计方法论"（craft 规则借鉴源）同名不同义；新增「方法论参考与归因」段
+
+#### P1: prototype-sync 自动触发
+- **prototype/SKILL.md**: prototype-sync 段从 "SOP" 升级为 "release-archivist 自动触发"，明确标准路径是 closing 流程自动触发
+- **release-archivist/SKILL.md**: 新增 prototype-sync 执行校验段，要求检查 stdout 输出，禁止在未执行时标注为已完成
+- **release-archivist/references/closing-procedures.md**: 同步执行校验段和 write-back order 约束
+
+### Added（原型设计能力扩展，2 项）
+
+#### P2-1: 交互原型 + 线框图方法论
+- **prototype/references/interactive-prototype.md**: 新增交互原型方法论（零依赖状态管理、表单验证、多步导航、动态列表）
+- **prototype/references/wireframe.md**: 新增线框图方法论（低保真快速探索、3-5 差异化方案、并排对比）
+- **prototype/references/orchestration-flow.md**: prompt 组装顺序契约新增原型类型注入策略（wireframe / interactive / static）
+
+#### P2-2: C 端骨架扩展
+- **prototype/references/layouts.md**: 新增 §9-§14 C 端骨架（hero-xl / marketing-features / social-proof / pricing-c / faq / cta-c），新增 C 端页面节奏表
+- **prototype/references/template.html**: 新增 C 端扩展 CSS（hero-xl / pricing-card / faq-item / urgency 等）
+
 ## [0.24.0] - 2026-07-28
 
 ### Fixed（复利工程强制化补强，5 项）

package/GEMINI.md

@@ -8,7 +8,7 @@ The workflow is self-contained and does not require OpenSpec or Superpowers at r
 
 
 <!-- team-flow-phase-guard-start -->
-# team-flow v0.24.0 | 阶段: {{state}} | 工作流: {{workflow}}
+# team-flow v0.25.1 | 阶段: {{state}} | 工作流: {{workflow}}
 当前阶段允许的操作由 workflow-start 路由规则定义。
 禁止跨越 DP gate 进入下一阶段。变更范围以 execution-contract.md 的 Intent Lock 为准。
 <!-- team-flow-phase-guard-end -->

package/INSTALL.md

@@ -7,7 +7,7 @@
 - [Fission-AI/OpenSpec](https://github.com/Fission-AI/OpenSpec) — 规划引擎（Schema 验证、Delta Spec、工件解析）
 - [obra/superpowers](https://github.com/obra/superpowers) — 执行纪律（TDD 铁律、SDD、系统化调试、代码审查）
 
-当前发布版本：**v0.24.0**。
+当前发布版本：**v0.25.1**。
 
 ---
 

package/README.md

@@ -1,6 +1,6 @@
 # team-flow
 
-> 当前版本：`v0.24.0`
+> 当前版本：`v0.25.1`
 
 > 统一插件：**team-flow**（spec 驱动开发）+ **compound-engineering 核心子集**（全局复利）+ **architecture-design**（4A+DDD 增量设计）+ **prototype**（本地 HTML 原型）+ **e2e**（AC 驱动 E2E）+ **workflow-orchestrator**（产品级编排）+ **workflow-bootstrap**（既有项目接入）。一次安装，七套能力协同。
 

package/docs/README_en.md

@@ -126,7 +126,7 @@ npm install -g team-flow
 
 ### Version
 
-- Current: `v0.24.0`
+- Current: `v0.25.1`
 - v0.9.1 highlights: DP-4 execution-mode recommendations, a portable runtime across 17 platforms, and a raw-package smoke with no plugin-root variable.
 - Self-contained — no OpenSpec or Superpowers runtime required
 - Upstream: [Fission-AI/OpenSpec](https://github.com/Fission-AI/OpenSpec), [obra/superpowers](https://github.com/obra/superpowers)

package/docs/solutions/INDEX.md

@@ -2,4 +2,5 @@
 <!-- 每条一行，按 severity 降序，≤150 行硬上限 -->
 | date | phase | domain | type | severity | summary | file |
 |------|-------|--------|------|----------|---------|------|
+| 2026-07-29 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-07-29-no-summary.md |
 | 2026-07-28 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-07-28-no-summary.md |

package/docs/solutions/cross-phase/2026-07-29-no-summary.md

@@ -0,0 +1,17 @@
+---
+phase: cross-phase
+domain: general
+type: insight
+severity: medium
+date: 2026-07-29
+source: 
+---
+
+## 问题描述
+(no summary)
+
+## 根因/模式
+（待补充）
+
+## 预防措施/应用方式
+（待补充）

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
   "description": "Unified workflow plugin: team-flow (spec-driven dev) + compound-engineering core subset + architecture-design (4A/DDD) + prototype (local HTML). 17 skills, one install.",
-  "version": "0.24.0",
+  "version": "0.25.1",
   "contextFileName": "GEMINI.md"
 }

package/hooks/session-start

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# v0.24.0: conditional injection — detects artifacts, injects workflow-start pointer
+# v0.25.1: conditional injection — detects artifacts, injects workflow-start pointer
 msg="<EXTREMELY_IMPORTANT>\nYou have team-flow installed. Use /team-flow:workflow-start ONLY when you detect an active team-flow change in the workspace (look for \`.team-flow.yaml\`, \`proposal.md\`, \`execution-contract.md\`, or \`specs/\` directories), OR when the user explicitly invokes it by name. For ordinary coding tasks without team-flow artifacts, do NOT invoke workflow-start — just handle the request directly.\n</EXTREMELY_IMPORTANT>"
 
 # Three platforms share the same message, only output format differs.

package/llms.txt

@@ -3,7 +3,7 @@
 ## Overview
 spec-superflow is a self-contained workflow integration plugin for Claude Code, Cursor, OpenAI Codex CLI/App, GitHub Copilot CLI, Gemini CLI, OpenCode, WorkBuddy, and Trae. It merges spec-driven planning artifacts (proposal, specs, design, tasks) with disciplined execution guardrails (TDD, review gates, controlled handoff) into one unified workflow.
 
-Current version: v0.24.0.
+Current version: v0.25.1.
 
 ## Key Documents
 - README.md: Chinese homepage with full usage guide and FAQ

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xulthekl/team-flow",
-  "version": "0.24.0",
+  "version": "0.25.1",
   "description": "Unified plugin (23 skills + 8 agents) integrating team-flow, compound-engineering, architecture-design, prototype, design-system, workflow-orchestrator, workflow-bootstrap, e2e, session-handoff, workflow-feedback for multi-agent coding tools.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.24.0",
+  "version": "0.25.1",
   "description": "Unified workflow plugin: team-flow (spec-driven dev: TDD/SDD/code-review/debugging) + compound-engineering core subset (brainstorm/plan/compound/strategy/ideate/proof, global compounding) + architecture-design (4A+DDD incremental design & global compounding) + prototype (local HTML prototype, zero external deps) + e2e (Playwright E2E, AC-driven) + workflow-orchestrator (product-level workflow orchestration) + workflow-bootstrap (existing project onboarding) + session-handoff (context transfer) + workflow-feedback (issue tracking). 23 skills + 8 agents, one install.",
   "author": {
     "name": "LT"

package/scripts/lib/config-loader.mjs

@@ -19,6 +19,9 @@ const DEFAULTS = {
   verification: {
     language: 'auto',
   },
+  prd: {
+    template: 'templates/prd.md',
+  },
 };
 
 export const MODEL_PROFILES = Object.freeze([

package/skills/bug-investigator/SKILL.md

@@ -49,7 +49,7 @@ Scientific method: form a single hypothesis ("I think X is the root cause becaus
 
 ### DP-5: Debug Escalation (3+ Failures)
 
-3+ failed fixes = architectural problem. Each fix revealing new problems elsewhere = wrong architecture. Record: `npx --yes --package @xulthekl/team-flow@0.24.0 tf state set <change-dir> dp_5_result <decision>`. Discuss with user before attempting more fixes.
+3+ failed fixes = architectural problem. Each fix revealing new problems elsewhere = wrong architecture. Record: `npx --yes --package @xulthekl/team-flow@0.25.1 tf state set <change-dir> dp_5_result <decision>`. Discuss with user before attempting more fixes.
 
 ## Red Flags — Return to Phase 1
 

package/skills/build-executor/SKILL.md

@@ -15,18 +15,18 @@ When `architecture/sql/` exists, also read:
 - `architecture/sql/ddl/*.sql` — executable DDL scripts; reference directly for DB schema change tasks instead of hand-writing DDL
 - `architecture/sql/migration/*.sql` — data migration scripts; execute as-is for data transformation tasks
 
-Check workflow mode first: `npx --yes --package @xulthekl/team-flow@0.24.0 tf state get <change-dir> workflow`. If `tweak` → direct edit mode. If `hotfix` or `full` → standard contract-first discipline.
+Check workflow mode first: `npx --yes --package @xulthekl/team-flow@0.25.1 tf state get <change-dir> workflow`. If `tweak` → direct edit mode. If `hotfix` or `full` → standard contract-first discipline.
 
 Branch/worktree preflight before ANY implementation edit (mandatory — do not skip):
 1. Run the isolation check:
    ```bash
-   npx --yes --package @xulthekl/team-flow@0.24.0 tf isolate <change-dir>
+   npx --yes --package @xulthekl/team-flow@0.25.1 tf isolate <change-dir>
    ```
    This script enforces git isolation: if you are on `main`/`master` it creates a
    git worktree (preferred) or a new branch, and exits non-zero if it cannot and you
    have not approved `--force`.
-2. If `npx --yes --package @xulthekl/team-flow@0.24.0 tf isolate` exits non-zero: STOP. Do not edit `main`/`master` in place.
-   Ask the user for explicit approval (and re-run with `npx --yes --package @xulthekl/team-flow@0.24.0 tf isolate <change-dir> --force`
+2. If `npx --yes --package @xulthekl/team-flow@0.25.1 tf isolate` exits non-zero: STOP. Do not edit `main`/`master` in place.
+   Ask the user for explicit approval (and re-run with `npx --yes --package @xulthekl/team-flow@0.25.1 tf isolate <change-dir> --force`
    only after they approve).
 3. If it succeeds, report the chosen branch/worktree and make all implementation
    edits there.
@@ -52,15 +52,15 @@ Return to `specifying` or `bridging` if: new behavior appears, interfaces change
 For `full`/`hotfix`, generate proposed waves from the approved contract, then use the recommendation as a decision aid rather than silently defaulting a mode:
 
 ```bash
-npx --yes --package @xulthekl/team-flow@0.24.0 tf execution recommend <change-dir> \
+npx --yes --package @xulthekl/team-flow@0.25.1 tf execution recommend <change-dir> \
   --wave <wave-id>:<parallel|serial>:<task,...>[:<depends-on,...>] --json
 # Show every available mode, the observed facts, and the recommendation to the user.
 # The command writes a receipt tied to the artifacts, contract, and waves. After the user chooses, record that explicit confirmation:
-npx --yes --package @xulthekl/team-flow@0.24.0 tf execution plan <change-dir> \
+npx --yes --package @xulthekl/team-flow@0.25.1 tf execution plan <change-dir> \
   --mode <selected-mode> --confirm --reason "user-selected execution mode" \
   --wave <wave-id>:<parallel|serial>:<task,...>[:<depends-on,...>]
 # Add --acknowledge-recommendation when the selection differs from the recommendation.
-npx --yes --package @xulthekl/team-flow@0.24.0 tf execution show <change-dir> --json
+npx --yes --package @xulthekl/team-flow@0.25.1 tf execution show <change-dir> --json
 ```
 
 The optional fourth `--wave` segment names prerequisite wave IDs. `execution show --json` reports `current`, plus each wave's `depends_on`, `receipt`, `blockers`, `retryable`, and `eligible` status. A wave with `retryable: true` has a current `fail` receipt and is eligible only for its focused repair and re-review; its dependents remain blocked until its replacement `pass` receipt. Report the saved plan revision, selected mode, ordered waves, dependencies, and whether every `parallel` wave can actually be dispatched concurrently on the current platform. If concurrency is unavailable, state the capability and reason plainly; retain the planned `parallel` strategy and do not silently execute it as a serial or Batch Inline plan.
@@ -73,7 +73,7 @@ The recommendation uses task count, configured `execution.inlineThreshold`, and
 | **Inline** | Recommended for a single sequential task; always available for a user-confirmed choice |
 | **Batch Inline** | Recommended for a bounded sequential batch; it remains serial and is never presented as parallel |
 
-Do not transition to `executing` until `execution show` reports `current: true` and the phase guard passes. A revised plan must repeat `npx --yes --package @xulthekl/team-flow@0.24.0 tf execution recommend` and use `npx --yes --package @xulthekl/team-flow@0.24.0 tf execution revise --confirm`; it creates a new revision and invalidates receipts from the prior revision.
+Do not transition to `executing` until `execution show` reports `current: true` and the phase guard passes. A revised plan must repeat `npx --yes --package @xulthekl/team-flow@0.25.1 tf execution recommend` and use `npx --yes --package @xulthekl/team-flow@0.25.1 tf execution revise --confirm`; it creates a new revision and invalidates receipts from the prior revision.
 
 ## Batch Inline Execution
 
@@ -88,21 +88,21 @@ Boundaries: if any task touches >1 module, involves schema/API/config changes, o
 For full/hotfix by default. Dispatch according to the persisted plan, review each planned wave, and run a final broad review after all waves.
 
 ### Planned-Wave Loop
-1. Read the current plan with `npx --yes --package @xulthekl/team-flow@0.24.0 tf execution show <change-dir> --json`; only waves shown with `current: true` and `eligible: true` may start. A `retryable: true` wave may only be repaired and re-reviewed; do not dispatch its dependents until its replacement receipt is `pass`. The CLI encodes dependencies in `--wave <id>:<strategy>:<tasks>[:<depends-on,...>]` and rejects a review receipt for a wave whose prerequisites lack current `pass` receipts.
+1. Read the current plan with `npx --yes --package @xulthekl/team-flow@0.25.1 tf execution show <change-dir> --json`; only waves shown with `current: true` and `eligible: true` may start. A `retryable: true` wave may only be repaired and re-reviewed; do not dispatch its dependents until its replacement receipt is `pass`. The CLI encodes dependencies in `--wave <id>:<strategy>:<tasks>[:<depends-on,...>]` and rejects a review receipt for a wave whose prerequisites lack current `pass` receipts.
 2. A `parallel` wave may dispatch independent tasks simultaneously only when the platform supports concurrent dispatch. If it does not, disclose the unavailable capability and execute the same wave one task at a time without changing its stored strategy.
 3. A `serial` wave dispatches one task at a time in listed order.
 4. After every wave, write a non-empty persisted regular-file review report (separate from the implementer's report), then record exactly one receipt that names that review report:
    ```bash
-   npx --yes --package @xulthekl/team-flow@0.24.0 tf execution review <change-dir> \
+   npx --yes --package @xulthekl/team-flow@0.25.1 tf execution review <change-dir> \
      --wave <wave-id> --base <sha> --head <sha> --report <review-report-path> --verdict <pass|fail>
    ```
    Do not begin a dependent wave until its predecessor receipt is `pass`.
 5. Critical/Important findings require a `fail` receipt, a focused repair, re-review, then a replacement `pass` receipt. Never advance or close with a missing or failed receipt.
 
 ### Per-Task Loop
-1. **Dispatch implementer**: Load the template with `npx --yes --package @xulthekl/team-flow@0.24.0 tf runtime asset read skills/build-executor/implementer-prompt.md`. Extract task brief with `scripts/task-brief PLAN_FILE N`. Include: where task fits, brief path, interfaces from prior tasks, report file path.
+1. **Dispatch implementer**: Load the template with `npx --yes --package @xulthekl/team-flow@0.25.1 tf runtime asset read skills/build-executor/implementer-prompt.md`. Extract task brief with `scripts/task-brief PLAN_FILE N`. Include: where task fits, brief path, interfaces from prior tasks, report file path.
 2. **Handle response**: DONE → generate review package + dispatch reviewer. DONE_WITH_CONCERNS → assess. NEEDS_CONTEXT → provide context. BLOCKED → re-dispatch with better model or escalate.
-3. **Review**: Load `npx --yes --package @xulthekl/team-flow@0.24.0 tf runtime asset read skills/build-executor/task-reviewer-prompt.md`. Reviewer returns spec compliance + code quality verdicts with the wave ID, git range, report path, and `pass`/`fail` receipt command.
+3. **Review**: Load `npx --yes --package @xulthekl/team-flow@0.25.1 tf runtime asset read skills/build-executor/task-reviewer-prompt.md`. Reviewer returns spec compliance + code quality verdicts with the wave ID, git range, report path, and `pass`/`fail` receipt command.
 4. **Fix**: If Critical or Important issues, write the `fail` receipt, dispatch fix subagent, re-review, and write the replacement `pass` receipt.
 5. **Mark complete**: Append to `.superpowers/sdd/progress.md`: `Task N: complete (commits <base7>..<head7>, review clean)`
 
@@ -110,7 +110,7 @@ For full/hotfix by default. Dispatch according to the persisted plan, review eac
 Use the configured profile that matches the task role. Resolve it before dispatch:
 
 ```bash
-npx --yes --package @xulthekl/team-flow@0.24.0 tf runtime config --resolve-model <profile>
+npx --yes --package @xulthekl/team-flow@0.25.1 tf runtime config --resolve-model <profile>
 ```
 
 | Profile | Role |
@@ -123,11 +123,11 @@ npx --yes --package @xulthekl/team-flow@0.24.0 tf runtime config --resolve-model
 For platforms whose dispatch supports a `model` field, explicitly pass the resolved `model` value. If the result is `configured: false`, automatic selection is unavailable: do not invent a provider model and do not bypass the existing requirement to specify `model` explicitly. Resolution only reads configuration; it does not switch models.
 
 ### Progress Ledger
-Track in `.superpowers/sdd/progress.md`. Check for existing ledger — completed tasks are done. After each batch: `npx --yes --package @xulthekl/team-flow@0.24.0 tf state set <change-dir> batches_completed <N>`.
+Track in `.superpowers/sdd/progress.md`. Check for existing ledger — completed tasks are done. After each batch: `npx --yes --package @xulthekl/team-flow@0.25.1 tf state set <change-dir> batches_completed <N>`.
 
 ## Inline Execution Mode
 
-Only after a user-confirmed `inline` selection is recorded by `npx --yes --package @xulthekl/team-flow@0.24.0 tf execution plan --confirm`; a non-recommended selection also records `--acknowledge-recommendation`. Executes in the current session and still writes one review receipt per planned wave.
+Only after a user-confirmed `inline` selection is recorded by `npx --yes --package @xulthekl/team-flow@0.25.1 tf execution plan --confirm`; a non-recommended selection also records `--acknowledge-recommendation`. Executes in the current session and still writes one review receipt per planned wave.
 
 Per-task: extract brief → write failing test → confirm failure → implement → confirm green → checkpoint review (done-when criteria, SHALL/MUST verification) → commit → save a task-level recovery checkpoint when another task remains → append to progress ledger.
 
@@ -135,7 +135,7 @@ After a task is committed and reviewed, when another task remains, save the
 recovery context with real evidence:
 
 ```bash
-npx --yes --package @xulthekl/team-flow@0.24.0 tf checkpoint save <change-dir> \
+npx --yes --package @xulthekl/team-flow@0.25.1 tf checkpoint save <change-dir> \
   --task <completed-task-id> --next "<next task>" --completed "<completed work>" \
   --verification "<verification report path>" --review "<review report path>" \
   --risk "<open risk or None>" --commit-start <base-sha> --commit-end <head-sha>
@@ -143,7 +143,7 @@ npx --yes --package @xulthekl/team-flow@0.24.0 tf checkpoint save <change-dir> \
 
 This augments `.superpowers/sdd/progress.md`; it does not replace the progress
 ledger or add a new core workflow state. Do not claim a checkpoint is current
-when `npx --yes --package @xulthekl/team-flow@0.24.0 tf checkpoint list` reports it as stale.
+when `npx --yes --package @xulthekl/team-flow@0.25.1 tf checkpoint list` reports it as stale.
 
 If task hits BLOCKED (3+ fix failures or changes outside declared scope), escalate to SDD.
 
@@ -153,8 +153,8 @@ Skip TDD. Apply changes directly. Verify file integrity (exists, non-empty, vali
 
 ## DP Records
 
-DP-4 is written by `npx --yes --package @xulthekl/team-flow@0.24.0 tf execution plan`; do not write it with raw `state set`.
-DP-5 (debug escalation): `npx --yes --package @xulthekl/team-flow@0.24.0 tf state set <change-dir> dp_5_result "<resolution>"` + timestamp.
+DP-4 is written by `npx --yes --package @xulthekl/team-flow@0.25.1 tf execution plan`; do not write it with raw `state set`.
+DP-5 (debug escalation): `npx --yes --package @xulthekl/team-flow@0.25.1 tf state set <change-dir> dp_5_result "<resolution>"` + timestamp.
 
 ## Completion Standard
 

package/skills/build-executor/implementer-prompt.md

@@ -22,7 +22,7 @@ Subagent (general-purpose):
     ## Planned Wave
 
     You are assigned to planned wave [WAVE_ID] with strategy [WAVE_STRATEGY].
-    Read `npx --yes --package @xulthekl/team-flow@0.24.0 tf execution show <change-dir> --json` before editing. Do not start
+    Read `npx --yes --package @xulthekl/team-flow@0.25.1 tf execution show <change-dir> --json` before editing. Do not start
     unless all declared dependencies have `pass` review receipts. A `parallel`
     label permits concurrent dispatch only when the controller confirms the
     platform supports it; never change the saved wave strategy yourself.

package/skills/build-executor/references/execution-modes.md

@@ -7,14 +7,14 @@
 For `full`/`hotfix`, generate proposed waves from the approved contract, then use the recommendation as a decision aid:
 
 ```bash
-npx --yes --package @xulthekl/team-flow@0.24.0 tf execution recommend <change-dir> \
+npx --yes --package @xulthekl/team-flow@0.25.1 tf execution recommend <change-dir> \
   --wave <wave-id>:<parallel|serial>:<task,...>[:<depends-on,...>] --json
 # Show every available mode, the observed facts, and the recommendation to the user.
-npx --yes --package @xulthekl/team-flow@0.24.0 tf execution plan <change-dir> \
+npx --yes --package @xulthekl/team-flow@0.25.1 tf execution plan <change-dir> \
   --mode <selected-mode> --confirm --reason "user-selected execution mode" \
   --wave <wave-id>:<parallel|serial>:<task,...>[:<depends-on,...>]
 # Add --acknowledge-recommendation when the selection differs from the recommendation.
-npx --yes --package @xulthekl/team-flow@0.24.0 tf execution show <change-dir> --json
+npx --yes --package @xulthekl/team-flow@0.25.1 tf execution show <change-dir> --json
 ```
 
 The optional fourth `--wave` segment names prerequisite wave IDs. `execution show --json` reports `current`, plus each wave's `depends_on`, `receipt`, `blockers`, `retryable`, and `eligible` status.
@@ -37,7 +37,7 @@ Dispatch according to the persisted plan, review each planned wave, and run a fi
 3. A `serial` wave dispatches one task at a time in listed order.
 4. After every wave, write a review report, then record one receipt:
    ```bash
-   npx --yes --package @xulthekl/team-flow@0.24.0 tf execution review <change-dir> \
+   npx --yes --package @xulthekl/team-flow@0.25.1 tf execution review <change-dir> \
      --wave <wave-id> --base <sha> --head <sha> --report <review-report-path> --verdict <pass|fail>
    ```
 5. Critical/Important findings require a `fail` receipt, focused repair, re-review, then replacement `pass` receipt.
@@ -66,7 +66,7 @@ Per-task: extract brief → write failing test → confirm failure → implement
 ## Model Selection
 
 ```bash
-npx --yes --package @xulthekl/team-flow@0.24.0 tf runtime config --resolve-model <profile>
+npx --yes --package @xulthekl/team-flow@0.25.1 tf runtime config --resolve-model <profile>
 ```
 
 | Profile | Role |
@@ -79,7 +79,7 @@ npx --yes --package @xulthekl/team-flow@0.24.0 tf runtime config --resolve-model
 ## Recovery Checkpoint
 
 ```bash
-npx --yes --package @xulthekl/team-flow@0.24.0 tf checkpoint save <change-dir> \
+npx --yes --package @xulthekl/team-flow@0.25.1 tf checkpoint save <change-dir> \
   --task <completed-task-id> --next "<next task>" --completed "<completed work>" \
   --verification "<verification report path>" --review "<review report path>" \
   --risk "<open risk or None>" --commit-start <base-sha> --commit-end <head-sha>

package/skills/build-executor/task-reviewer-prompt.md

@@ -146,7 +146,7 @@ Subagent (general-purpose):
     command for the controller:
 
     ```bash
-    npx --yes --package @xulthekl/team-flow@0.24.0 tf execution review <change-dir> --wave [WAVE_ID] --base [BASE_SHA] --head [HEAD_SHA] --report [REVIEW_REPORT_FILE] --verdict <pass|fail>
+    npx --yes --package @xulthekl/team-flow@0.25.1 tf execution review <change-dir> --wave [WAVE_ID] --base [BASE_SHA] --head [HEAD_SHA] --report [REVIEW_REPORT_FILE] --verdict <pass|fail>
     ```
 
     Use `fail` for any Critical/Important finding. A repair must be re-reviewed