@xulthekl/team-flow 0.43.1 → 0.45.0

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

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

package/.claude-plugin/marketplace.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "description": "Unified workflow plugin: team-flow + compound-engineering core subset + architecture-design + prototype + workflow-orchestrator + workflow-bootstrap + e2e + session-handoff + workflow-feedback. 24 skills + 15 agents, one install.",
+  "description": "Unified workflow plugin: team-flow + compound-engineering core subset + architecture-design + prototype + workflow-orchestrator + workflow-bootstrap + e2e + session-handoff + workflow-feedback + business-analysis. 25 skills + 16 agents, one install.",
   "owner": {
     "name": "LT",
     "url": "https://github.com/LT"
@@ -8,8 +8,8 @@
   "plugins": [
     {
       "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. 24 skills + 15 agents with embedded TDD, SDD, code review, debugging, delta spec sync, and design-system-driven prototyping.",
-      "version": "0.43.1",
+      "description": "8-state spec workflow + compound global compounding + architecture-design (4A/DDD) + local HTML prototype + product-level orchestration + bootstrap + e2e + session handoff + workflow feedback + independent business analysis. 25 skills + 16 agents with embedded TDD, SDD, code review, debugging, delta spec sync, and design-system-driven prototyping.",
+      "version": "0.45.0",
       "source": "./",
       "author": {
         "name": "LT",

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "team-flow",
-  "version": "0.43.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). 24 skills + 15 agents, one install.",
+  "version": "0.45.0",
+  "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) + business-analysis (independent requirement/scenario artifact). 25 skills + 16 agents, one install.",
   "source": "./",
   "author": {
     "name": "LT",

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.43.1",
+  "version": "0.45.0",
   "description": "Spec-first workflow that bridges OpenSpec-style planning and Superpowers-style execution discipline.",
   "author": {
     "name": "MageByte",
@@ -26,7 +26,7 @@
   "interface": {
     "displayName": "team-flow",
     "shortDescription": "Spec-first workflow with guarded execution.",
-    "longDescription": "A self-contained Codex workflow plugin with 24 skills for intent exploration, planning artifacts, execution contracts, TDD execution, review gates, systematic debugging, closure, and delta spec sync.",
+    "longDescription": "A self-contained Codex workflow plugin with 25 skills for intent exploration, planning artifacts, execution contracts, TDD execution, review gates, systematic debugging, closure, delta spec sync, and independent business analysis.",
     "developerName": "MageByte",
     "category": "Developer Tools",
     "composerIcon": "./assets/icon.svg",

package/.cursor-plugin/marketplace.json

@@ -5,13 +5,13 @@
   },
   "metadata": {
     "description": "Unified workflow plugin marketplace for Cursor (team-flow: team-flow + compound + architecture-design + prototype).",
-    "version": "0.43.1"
+    "version": "0.45.0"
   },
   "plugins": [
     {
       "name": "team-flow",
       "source": ".",
-      "description": "Unified workflow plugin: team-flow + compound-engineering core subset + architecture-design + prototype. 24 skills + 15 agents."
+      "description": "Unified workflow plugin: team-flow + compound-engineering core subset + architecture-design + prototype + business-analysis. 25 skills + 16 agents."
     }
   ]
 }

package/.cursor-plugin/plugin.json

@@ -1,8 +1,8 @@
 {
   "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). 24 skills + 15 agents, one install.",
-  "version": "0.43.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) + business-analysis (independent requirement/scenario artifact). 25 skills + 16 agents, one install.",
+  "version": "0.45.0",
   "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.43.1"
+    "version": "0.45.0"
   },
   "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.43.1",
+      "description": "Unified workflow with planning artifacts, execution contracts, TDD, review gates, systematic debugging, delta spec sync, architecture-design, independent business analysis, and local HTML prototyping.",
+      "version": "0.45.0",
       "source": ".",
       "author": {
         "name": "LT",

package/AGENTS.md

@@ -1,6 +1,6 @@
 # AGENTS.md · team-flow
 
-> team-flow 统一插件 = **team-flow**（spec 驱动开发）+ **compound-engineering 核心子集**（全局复利）+ **architecture-design**（4A+DDD 增量设计）+ **prototype**（本地 HTML 原型）+ **e2e**（AC 驱动 Playwright E2E）+ **workflow-orchestrator**（产品级编排）+ **workflow-bootstrap**（既有项目接入）。一次安装，七套能力协同（24 skills + 15 agents），支持 9 安装面（Claude Code, Cursor, OpenAI Codex CLI/App, GitHub Copilot CLI, Gemini CLI, OpenCode, WorkBuddy, Trae, ima-copilot）。
+> team-flow 统一插件 = **team-flow**（spec 驱动开发）+ **compound-engineering 核心子集**（全局复利）+ **architecture-design**（4A+DDD 增量设计）+ **prototype**（本地 HTML 原型）+ **e2e**（AC 驱动 Playwright E2E）+ **workflow-orchestrator**（产品级编排）+ **workflow-bootstrap**（既有项目接入）。一次安装，七套能力协同（25 skills + 16 agents），支持 9 安装面（Claude Code, Cursor, OpenAI Codex CLI/App, GitHub Copilot CLI, Gemini CLI, OpenCode, WorkBuddy, Trae, ima-copilot）。
 
 ## What This Is
 
@@ -12,7 +12,7 @@
 
 ### 身份与依赖关系
 
-- **team-flow**（本插件）：Claude Code / Cursor 等宿主的插件实体（`plugin.json` name = `team-flow`），包含 24 个 skills + 15 个 agents + hooks + templates
+- **team-flow**（本插件）：Claude Code / Cursor 等宿主的插件实体（`plugin.json` name = `team-flow`），包含 25 个 skills + 16 个 agents + hooks + templates
 - **@xulthekl/team-flow**（npm 底座包）：team-flow 的 CLI 工具层（`package.json` name = `@xulthekl/team-flow`，bin = `tf` / `team-flow`），提供状态机、校验、复利 CLI 等运行时能力
 - 关系：team-flow 插件 **包含** @xulthekl/team-flow npm 包作为底座（同一仓库、同一版本）。skills 中的 `tf ...` 调用的是已全局安装的 @xulthekl/team-flow CLI，版本由 session-start hook 自动同步
 - 历史身份（已废弃）：`spec-superflow`（npm 包名，0.11.0 后停止发布）/ `ssf`（CLI 前缀）/ `.spec-superflow.yaml`（状态文件）—— 详见设计增强方案 v0.9 §27
@@ -33,7 +33,7 @@ node --test tests/e2e.test.mjs --test-name-pattern="parseDeltaSpec"
 npm run validate
 ```
 
-## 能力概览（九套合一，24 skills）
+## 能力概览（十套合一，25 skills）
 
 ### 1. team-flow（底座，9 skills）
 spec 驱动开发过程。8 态变更机：`exploring → specifying → bridging → approved-for-build → executing → closing`（另有 `debugging` 侧路径 + `abandoned` 终态）。
@@ -85,6 +85,11 @@ spec 驱动开发过程。8 态变更机：`exploring → specifying → bridgin
 - 输出到 `.team-flow/feedback/`（git 跟踪，改进输入持久化）
 - release-archivist 收尾时联动建议触发
 
+### 10. business-analysis（1 skill，独立业务分析工具）
+- 将任意用户输入整理为 `requirement/vN/business-analysis.md`，产出 Requirements List 与 Scenario List
+- 支持多轮单问澄清、待办记录、新增/更新模式，写入前必须阻塞用户确认
+- 不进入核心工作流，作为独立外挂工具运行
+
 ## 全局产物结构（Discoverability —— 设计/开发前先检索）
 
 ```
@@ -169,7 +174,7 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
   全局作为下一 change / 下一 PRD 版本的 grounding → 闭环
 ```
 
-## Skills 索引（24 个）
+## Skills 索引（25 个）
 
 | Skill | 归属 | 用途 |
 |---|---|---|
@@ -197,6 +202,7 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
 | workflow-bootstrap | 既有项目接入 | 既有项目侦察+基线建立（v0.6） |
 | session-handoff | 会话交接 | 上下文腐化时压缩会话为交接文档（v0.16.0） |
 | workflow-feedback | 工作流反馈 | 工作流问题结构化记录（v0.16.0） |
+| business-analysis | 独立业务分析 | 将任意输入整理为 requirement/vN/business-analysis.md（独立外挂，v0.44.0） |
 
 ### 触发域分层（v0.12.0 新增）
 
@@ -207,13 +213,13 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
 | 接入层 | workflow-bootstrap | "初始化/接入/分析代码库" | 一次性，触发词独特，无冲突 |
 | 产品级（唯一入口） | **workflow-orchestrator** | 新的产品级需求（"新需求/从头开始/我有个想法/做一个XX"） | 拥有所有"产品级新需求"触发词，内部路由到 ce-brainstorm/ce-plan |
 | 变更级（唯一入口） | workflow-start | change 上下文内的操作（.team-flow.yaml） | 有强上下文约束，与产品级天然隔离 |
-| 步骤级 - 独立工具 | ce-ideate, ce-strategy, ce-compound, ce-proof, architecture-design, prototype, e2e, session-handoff, workflow-feedback | 各自独特触发词 | 无冲突，可独立触发 |
+| 步骤级 - 独立工具 | ce-ideate, ce-strategy, ce-compound, ce-proof, architecture-design, prototype, e2e, session-handoff, workflow-feedback, **business-analysis** | 各自独特触发词 | 无冲突，可独立触发；business-analysis 不进入核心工作流 |
 | 步骤级 - 受限独立 | ce-brainstorm, ce-plan | 可独立触发，但产品级新需求应走 orchestrator | description 中标注路由指导 |
 | 步骤级 - 仅路由 | need-explorer, spec-writer, contract-builder, build-executor, code-reviewer, spec-merger, release-archivist, bug-investigator | 仅由 workflow-start 路由 | 不独立触发 |
 
 > **规则**：新增 skill 时必须在此表登记所属层级。产品级新需求触发词归 workflow-orchestrator 独占。
 
-### Agents 索引（v0.7 新增，v0.30.0 增至 15 个）
+### Agents 索引（v0.7 新增，v0.30.0 增至 16 个）
 
 > **agent 文件设计规范见 CONTRIBUTING.md §6 + `templates/agent-template.md`**（v0.33.0）：frontmatter 必须合法 YAML（非法时 Claude Code 静默降级，skills: 预加载与 tools: 限制全部失效）；description 单句、禁 `<example>` 块；新增/修改 agent 必过 frontmatter-lint + 实证探针。
 
@@ -234,6 +240,7 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
 | contract-builder | 执行契约 agent——将规划制品压缩为单一执行握手 execution-contract.md、守 DP-3 批准门（可写型，契约文件唯一所有者；spec-writer DP-2 后、build-executor 前） | Read/Bash/Grep/Glob/Write/Edit | workflow-start 路由时作为子代理 dispatch |
 | build-executor | 构建执行 agent——以契约为权威驱动 TDD 批次实施（SDD/Inline/Batch Inline）、守 TDD Iron Law（可写型，实施代码所有者；契约 DP-3 批准后、release-archivist 前） | Read/Bash/Grep/Glob/Write/Edit | workflow-start 路由时作为子代理 dispatch |
 | release-archivist | 发布归档 agent——执行验证、产出 closing 总结、完成归档就绪（arch-merge → prototype-sync → 复利晋升）（可写型，归档制品所有者；build-executor 后、change 关闭前） | Read/Bash/Grep/Glob/Write/Edit | workflow-start 路由时作为子代理 dispatch |
+| business-analysis | 独立业务分析 agent——将任意输入整理为 requirement/vN/business-analysis.md，多轮单问澄清、待办记录、新增/更新模式，写入前阻塞确认 | Read/Bash/Grep/Glob/Write/Edit | 独立触发，不进入 workflow-orchestrator 核心流程（v0.44.0） |
 
 ## 复利贯穿机制（v0.5 新增）
 

package/CHANGELOG.md

@@ -4,8 +4,39 @@ All notable changes to `team-flow` will be documented in this file.
 
 The format loosely follows Keep a Changelog.
 
+## [0.45.0] - 2026-08-18
+
+### Added（glaf4-dev 集成增强，v0.45.0）
+
+设计来源：`docs/plan/glaf4-dev-integration-design.md` v2.1（glaf4-dev 统一开发技能族 v0.3.0，生产+测试全委托）
+
+- **运行时探测**（接口①）：`tf glaf4-delegation detect <root>` 三态检测（is_glaf4_java / glaf4_dev_available / delegation_mode）+ 写 `.team-flow/team-flow.config.json` 的 `glaf4_dev` 段；git root ≠ target_root 时写 git root 冗余副本（多服务 OR 聚合 enabled + delegation_mode 保留）；config-loader 查找链补 git root `.team-flow/`
+- **test-matrix-export v2**（接口②）：支持 test-matrix-vnext（schema_version 2.0）——模块名从 case.target 推导、kind→work_mode 映射（REFACTOR→TDD 记 footer）、write_targets 数组多行拆分 + `#方法` 锚点、case_id 与 rewriteIndex 正则兼容 WARN、`validateSchemaVersion` 版本门（未知版本显式 BLOCK）
+- **S1 guard 改造**（接口③）：`EXECUTION_MODES` 扩入 `glaf4-delegation`；execution-recommendation 补 recommend 链（glaf4DelegationAvailable 注入 available_modes + 白名单改引用单一真相源）；cmd-execution 支持 `--mode glaf4-delegation --wave w1:serial:delegate` 单 wave 计划
+- **证据回灌**（接口④）：`tf glaf4-evidence-export` 聚合 glaf4-dev run 终局 PASS 证据（模式→证据阶段映射、每 batch 最终 GREEN、executed_classes 去重、surefire 兼容行、total=0 边界、environment_error 分流）→ `tf test record --from` 落盘
+- **委托协议 CLI**：`tf glaf4-delegation`（confirm DP-4 委托确认 5 项 + write-set.json 落盘 + 契约段 diff WARN；verify-write-set 门禁级对账；verify-tasks 审计；record-partial 落 partial writes；reset 删 plan 重走 DP-4）
+- **delegation-status guard 维度**：executing:closing 校验 `delegation_status`（failed 阻断直到人工重置；retry_count≥3 提示上限）
+- **skip 禁令**：glaf4-delegation 模式禁 `test_matrix_skipped`（唯一例外 TEST_BOOTSTRAP），三个测试门禁统一接入
+- **GLAF4 Delegation 段**：contract-builder SKILL 重写 GLAF4 路由 + `references/glaf4-delegation.md`（骨架矩阵先行时序 + closing 时序协议）+ `templates/execution-contract.md` 段占位；workflow-start 路由从 glaf4-tests → glaf4-dev 实施委托
+- **四轮覆盖度评审闭环**：2 阻塞（C1 探测断链/C2 版本契约）+ 5 Important（模板表头盲区/嵌套工程根/多服务污染/detect 接线/mode last-write-wins）+ 12 Minor 全修，707/707 测试通过
+
+## [0.44.0] - 2026-08-17
+
+### Added（独立 business-analysis skill/agent，v0.44.0）
+
+- **新增 `skills/business-analysis/`**：独立业务分析 skill，将任意用户输入整理为 `requirement/vN/business-analysis.md`，产出 Requirements List 与 Scenario List
+- **新增 `agents/business-analysis.md`**：配套独立 agent，`tools` 含 Read/Bash/Grep/Glob/Write/Edit，写入前必须阻塞用户确认
+- **多轮单问澄清协议**：每次只问 1 个问题，用户无法回答时记录为 `TODO-xxx`，相关条目保持 🔵 pending
+- **版本解析规则**：支持显式参数 / `tf runtime config --get active.requirement` / `requirement/` 目录扫描 / 默认 `v1`
+- **输出格式契约**：只含需求列表 + 业务场景列表 + Open Questions/TODOs，禁止写入 `ledger.md`、PRD、流程、架构、`.team-flow.yaml`
+- **QA 检查清单**：5 项 Error 检查（角色覆盖、六维度齐全、REQ 引用存在、对话证据可追溯、Acceptance 可测试）
+- **技能/Agent 计数同步**：24 skills + 15 agents → 25 skills + 16 agents，plugin.json / marketplace.json / README.md / AGENTS.md / package.json / gemini-extension.json 等同步更新
+- **测试覆盖**：`tests/lib/cmd-install-workbuddy.test.mjs` 技能数断言更新为 25；保留 `docs/examples/*/specs/` 示例目录（`.gitignore` 例外规则）
+
 ## [Unreleased]
 
+## [0.43.1] - 2026-08-07
+
 ### Added（closing 代码落地 + 文件存在性双层防护 + 测试执行可信度 + spec 路径契约，v0.43.1）
 
 - **`tf deisolate --merge` 健壮性增强**：dirty 阻断（未提交改动默认不合并，`--force` 跳过）/ ahead==0 短路（幂等）/ 冲突报告（unmerged 文件清单 + 非零 exit）

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.43.1 | 阶段: {{state}} | 工作流: {{workflow}}
+# team-flow v0.45.0 | 阶段: {{state}} | 工作流: {{workflow}}
 当前阶段允许的操作由 workflow-start 路由规则定义。
 禁止跨越 DP gate 进入下一阶段。变更范围以 execution-contract.md 的 Intent Lock 为准。
 <!-- team-flow-phase-guard-end -->

package/INSTALL.md

@@ -7,32 +7,34 @@
 - [Fission-AI/OpenSpec](https://github.com/Fission-AI/OpenSpec) — 规划引擎（Schema 验证、Delta Spec、工件解析）
 - [obra/superpowers](https://github.com/obra/superpowers) — 执行纪律（TDD 铁律、SDD、系统化调试、代码审查）
 
-当前发布版本：**v0.43.1**。
+当前发布版本：**v0.45.0**。
 
 ---
 
 ## 平台总览
 
-| 平台 | 安装 | 升级 | 卸载 |
-|------|------|------|------|
-| Claude Code | marketplace | `/plugin update` | `/plugin uninstall` |
-| Cursor | skills 目录 / GitHub 导入 / 一键脚本 | 重新运行脚本 | 删除 `.cursor/skills/` |
-| OpenAI Codex CLI | Plugin Directory / marketplace | marketplace refresh + re-add | `codex plugin remove` |
-| OpenAI Codex App | Plugins 面板 / marketplace | CLI 更新后 App 面板启用 | App 面板禁用 |
-| GitHub Copilot CLI | marketplace | `copilot plugin update` | `copilot plugin uninstall` |
-| Gemini CLI | `gemini extensions install` | `gemini extensions update` | `gemini extensions uninstall` |
-| OpenCode | plugin entry / skills 目录 | `git pull` | 删除 plugin/skills |
-| WorkBuddy | `tf install-workbuddy` | 重新运行安装器 | 删除 marketplace 插件并禁用 |
-| Trae IDE / TRAE Work | `.trae/skills` / 上传 zip 或 .skill / marketplace | `git pull` + 重新导入 | UI 卸载或删除技能目录 |
-| Cline | `tf install-cline` | 重新运行脚本 | 删除 `.cline/skills/`、`.clinerules/` |
-| Kiro | `tf install-kiro` | 重新运行脚本 | 删除 `.kiro/skills/`、`.kiro/steering/` |
-| Windsurf | `tf install-windsurf` | 重新运行脚本 | 删除 `.windsurf/skills/`、`.windsurf/rules/` |
-| Qwen Code | `tf install-qwen` | 重新运行脚本 | 删除 `.qwen/skills/`、`.qwen/rules/` |
-| Amazon Q Developer | `tf install-amazon-q` | 重新运行脚本 | 删除 `.amazonq/skills/`、`.amazonq/rules/` |
-| Roo Code | `tf install-roocode` | 重新运行脚本 | 删除 `.roo/skills/`、`.roo/rules/` |
-| Continue | `tf install-continue` | 重新运行脚本 | 删除 `.continue/skills/`、`.continue/rules/` |
-| Pi | `tf install-pi` | 重新运行脚本 | 删除 `.pi/skills/` |
-| ZCODE | `tf install-zcode` | 重新运行脚本 | 删除 `.zcode/skills/`、`.zcode/rules/` |
+
+| 平台                   | 安装                                             | 升级                           | 卸载                                        |
+| -------------------- | ---------------------------------------------- | ---------------------------- | ----------------------------------------- |
+| Claude Code          | marketplace                                    | `/plugin update`             | `/plugin uninstall`                       |
+| Cursor               | skills 目录 / GitHub 导入 / 一键脚本                   | 重新运行脚本                       | 删除 `.cursor/skills/`                      |
+| OpenAI Codex CLI     | Plugin Directory / marketplace                 | marketplace refresh + re-add | `codex plugin remove`                     |
+| OpenAI Codex App     | Plugins 面板 / marketplace                       | CLI 更新后 App 面板启用             | App 面板禁用                                  |
+| GitHub Copilot CLI   | marketplace                                    | `copilot plugin update`      | `copilot plugin uninstall`                |
+| Gemini CLI           | `gemini extensions install`                    | `gemini extensions update`   | `gemini extensions uninstall`             |
+| OpenCode             | plugin entry / skills 目录                       | `git pull`                   | 删除 plugin/skills                          |
+| WorkBuddy            | `tf install-workbuddy`                         | 重新运行安装器                      | 删除 marketplace 插件并禁用                      |
+| Trae IDE / TRAE Work | `.trae/skills` / 上传 zip 或 .skill / marketplace | `git pull` + 重新导入            | UI 卸载或删除技能目录                              |
+| Cline                | `tf install-cline`                             | 重新运行脚本                       | 删除 `.cline/skills/`、`.clinerules/`        |
+| Kiro                 | `tf install-kiro`                              | 重新运行脚本                       | 删除 `.kiro/skills/`、`.kiro/steering/`      |
+| Windsurf             | `tf install-windsurf`                          | 重新运行脚本                       | 删除 `.windsurf/skills/`、`.windsurf/rules/` |
+| Qwen Code            | `tf install-qwen`                              | 重新运行脚本                       | 删除 `.qwen/skills/`、`.qwen/rules/`         |
+| Amazon Q Developer   | `tf install-amazon-q`                          | 重新运行脚本                       | 删除 `.amazonq/skills/`、`.amazonq/rules/`   |
+| Roo Code             | `tf install-roocode`                           | 重新运行脚本                       | 删除 `.roo/skills/`、`.roo/rules/`           |
+| Continue             | `tf install-continue`                          | 重新运行脚本                       | 删除 `.continue/skills/`、`.continue/rules/` |
+| Pi                   | `tf install-pi`                                | 重新运行脚本                       | 删除 `.pi/skills/`                          |
+| ZCODE                | `tf install-zcode`                             | 重新运行脚本                       | 删除 `.zcode/skills/`、`.zcode/rules/`       |
+
 
 ---
 
@@ -41,7 +43,7 @@
 ### 安装（推荐：Marketplace）
 
 ```bash
-/plugin marketplace add MageByte-Zero/team-flow
+/plugin marketplace add http://team:glpat-qyqtVEKeE3eu6EfrohoAEm86MQp1OjEyOQk.01.0z1ft22h9@172.25.254.5:10080/d40050-gtmc-ai/team-flow.git
 /plugin install team-flow@team-flow
 ```
 
@@ -64,7 +66,7 @@
 ### 本地安装（开发 / 离线）
 
 ```bash
-git clone https://github.com/MageByte-Zero/team-flow.git
+git clone http://team:glpat-qyqtVEKeE3eu6EfrohoAEm86MQp1OjEyOQk.01.0z1ft22h9@172.25.254.5:10080/d40050-gtmc-ai/team-flow.git
 
 # 在 Claude Code 中执行：
 /plugin install file:/absolute/path/to/team-flow
@@ -807,4 +809,4 @@ Checkpoint 是任务级恢复上下文。`result-ready` handoff 在继续受影
 
 推荐流程：`exploring -> specifying -> bridging -> approved-for-build -> execution plan -> executing -> closing`
 
-hotfix 快速路径：`exploring -> bridging -> approved-for-build -> executing`。hotfix 可以跳过完整的 `proposal.md`、`design.md`、`tasks.md`、`specs/`，但仍然必须先生成一份新的最小 `execution-contract.md`，并完成 DP-3 批准后才能开始实现。
+hotfix 快速路径：`exploring -> bridging -> approved-for-build -> executing`。hotfix 可以跳过完整的 `proposal.md`、`design.md`、`tasks.md`、`specs/`，但仍然必须先生成一份新的最小 `execution-contract.md`，并完成 DP-3 批准后才能开始实现。

package/README.md

@@ -1,6 +1,6 @@
 # team-flow
 
-> 当前版本：`v0.43.1`
+> 当前版本：`v0.45.0`
 
 > 统一插件：**team-flow**（spec 驱动开发）+ **compound-engineering 核心子集**（全局复利）+ **architecture-design**（4A+DDD 增量设计）+ **prototype**（本地 HTML 原型）+ **e2e**（AC 驱动 E2E）+ **workflow-orchestrator**（产品级编排）+ **workflow-bootstrap**（既有项目接入）。一次安装，七套能力协同。
 
@@ -34,7 +34,7 @@
 git clone <your-repo> && <cli> plugin install ./team-flow
 ```
 
-> 不同宿主 CLI 的安装子命令略有差异（如 Claude Code 为 `/plugin add`，Cursor 为 `plugin install`）。以宿主文档为准；本插件提供单一 `plugin.json`，一次安装即加载全部 24 个 skills。
+> 不同宿主 CLI 的安装子命令略有差异（如 Claude Code 为 `/plugin add`，Cursor 为 `plugin install`）。以宿主文档为准；本插件提供单一 `plugin.json`，一次安装即加载全部 25 个 skills。
 
 ## 配置（插件层扩展字段）
 
@@ -70,7 +70,7 @@ specs/<cap>/        每变更设计/任务/契约 + learnings.md
 STRATEGY.md CONCEPTS.md 策略 / 领域词汇
 ```
 
-## 九套能力（24 skills）
+## 十套能力（25 skills）
 
 - **team-flow**（9）：workflow-start / need-explorer / spec-writer / contract-builder / build-executor / code-reviewer / spec-merger / release-archivist / bug-investigator
 - **compound 核心子集**（6）：ce-brainstorm / ce-plan / ce-compound / ce-strategy / ce-ideate / ce-proof
@@ -82,10 +82,11 @@ STRATEGY.md CONCEPTS.md 策略 / 领域词汇
 - **会话交接**（1）：session-handoff（上下文腐化时压缩会话为交接文档，v0.16.0）
 - **工作流反馈**（1）：workflow-feedback（工作流问题结构化记录，与 ce-compound 互补，v0.16.0）
 - **设计系统**（1）：design-system（独立创建/迭代项目级设计系统，用户主导交互，v0.19.0）
+- **业务分析**（1）：business-analysis（将任意输入整理为 requirement/vN/business-analysis.md，多轮单问澄清，独立外挂，v0.44.0）
 
-### 配套 agents（15 个，v0.30.0 增至 15）
+### 配套 agents（16 个，v0.30.0 增至 16）
 
-全部由编排层 dispatch（主代理只编排，need-explorer 为主进程交互式澄清）：architecture-design（架构设计门控）/ architecture-reviewer（架构自动审查）/ bug-investigator（bug 根因调查）/ change-split-auditor（拆分质量审计）/ code-reviewer（代码审查）/ cross-change-consistency-checker（跨 change 一致性）/ prd-completeness-reviewer（PRD 完整性评审）/ prototype-builder（原型绘制）/ prototype-env-scout（原型环境探查）/ prototype-reviewer（原型评审）/ need-explorer（需求探索）/ spec-writer（规格编写）/ contract-builder（执行契约构建）/ build-executor（TDD 构建执行）/ release-archivist（发布归档）。
+全部由编排层 dispatch（主代理只编排，need-explorer 为主进程交互式澄清）：architecture-design（架构设计门控）/ architecture-reviewer（架构自动审查）/ bug-investigator（bug 根因调查）/ change-split-auditor（拆分质量审计）/ code-reviewer（代码审查）/ cross-change-consistency-checker（跨 change 一致性）/ prd-completeness-reviewer（PRD 完整性评审）/ prototype-builder（原型绘制）/ prototype-env-scout（原型环境探查）/ prototype-reviewer（原型评审）/ need-explorer（需求探索）/ spec-writer（规格编写）/ contract-builder（执行契约构建）/ build-executor（TDD 构建执行）/ release-archivist（发布归档）/ business-analysis（独立业务分析）。
 
 ### 命名约定
 

package/agents/business-analysis.md

@@ -0,0 +1,53 @@
+---
+name: business-analysis
+description: "独立业务分析 agent：交互式整理 requirement/vN/business-analysis.md，产出 Requirements List 与 Scenario List，支持多轮单问澄清与待办记录，写入前必须阻塞用户确认。"
+model: inherit
+color: blue
+tools: ["Read", "Bash", "Grep", "Glob", "Write", "Edit"]
+skills:
+  - business-analysis
+---
+
+You are an independent Business Analysis agent. Your sole responsibility is to maintain `requirement/vN/business-analysis.md` by turning user input into structured requirements and scenarios. You write only this artifact and never write `ledger.md`, PRD, process details, architecture, or `.team-flow.yaml`.
+
+**Your preloaded Skill contains the detailed methodology.** Follow it for HOW. This prompt defines WHO you are and WHAT you must deliver.
+
+## Artifact Ownership
+
+You are the sole owner of `requirement/vN/business-analysis.md`. No other agent or orchestrator should modify this file directly.
+
+## Inputs
+
+| Parameter | Description |
+|-----------|-------------|
+| `user_input` | Raw user input: a sentence, document, meeting notes, etc. |
+| `version` | Target version, e.g. `v1`; auto-resolved if omitted |
+
+## Structured Output Contract
+
+Return the following YAML to the caller after each interaction:
+
+```yaml
+status: drafting | waiting_for_user | confirmed | blocked
+version: vN
+artifact_path: requirement/vN/business-analysis.md
+open_todos: []
+summary: "..."
+```
+
+## Red Lines
+
+**DO:**
+- Ask one question at a time
+- Record unanswered questions as TODOs in `## Open Questions / TODOs`
+- Keep entries as 🔵 pending until the user explicitly confirms them
+- Write acceptance criteria that are concrete and testable
+
+**DON'T:**
+- DO NOT write `ledger.md`
+- DO NOT modify `.team-flow.yaml` state or workflow fields
+- DO NOT use generic roles like "user"
+- DO NOT produce untestable acceptance criteria
+- DO NOT write process flow details, Mermaid diagrams, or L1-L4 process tables
+
+End your final response with an explicit terminal marker line: `FINAL VERDICT: <DONE | BLOCKED | FAIL>`

package/docs/README_en.md

@@ -126,7 +126,7 @@ npm install -g team-flow
 
 ### Version
 
-- Current: `v0.43.1`
+- Current: `v0.45.0`
 - 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/examples/add-dark-mode/specs/ui-theme/spec.md

@@ -1,35 +1,33 @@
-# Capability Spec
-
 ## ADDED Requirements
 
 ### Requirement: User can use dark mode
 
-The system SHALL provide a dark theme variant for the primary user interface.
+The system SHALL provide a user-facing dark mode for the web UI that can be toggled between light and dark themes.
 
-#### Scenario: Initial load follows system preference
+#### Scenario: Manual toggle
 
-- **WHEN** a first-time visitor opens the application and has no saved theme preference
-- **THEN** the interface uses the operating system color-scheme preference
+- **WHEN** the user clicks the theme toggle in the UI
+- **THEN** the interface switches to the selected theme immediately
 
-#### Scenario: User manually switches theme
+#### Scenario: System preference on first load
 
-- **WHEN** the user activates the theme toggle
-- **THEN** the interface switches between light and dark mode immediately
+- **WHEN** the user opens the application for the first time
+- **THEN** the interface theme matches the system preference by default
 
 ### Requirement: User preference persists
 
-The system SHALL persist an explicit user theme choice across reloads.
+The system SHALL persist the user's explicit theme choice across browser sessions using localStorage or an equivalent mechanism.
 
-#### Scenario: Saved choice overrides system preference
+#### Scenario: Return visit
 
-- **WHEN** a returning user has a saved theme choice
-- **THEN** the application loads using the saved choice instead of the current system preference
+- **WHEN** the user revisits the application after explicitly choosing dark mode
+- **THEN** the interface renders in dark mode without requiring another toggle
 
 ### Requirement: Theme maintains readable contrast
 
-The system SHALL preserve readable text and UI contrast in both light and dark mode.
+The system SHALL ensure that all core page colors and text combinations remain readable in both light and dark themes.
 
-#### Scenario: Primary content remains readable
+#### Scenario: Dark mode readability
 
-- **WHEN** the user views text, surfaces, and interactive controls in dark mode
-- **THEN** foreground and background combinations remain readable and distinguishable
+- **WHEN** the interface is in dark mode
+- **THEN** text and interactive elements meet WCAG contrast requirements against dark backgrounds

package/docs/examples/refactor-auth-boundary/specs/auth-boundary/spec.md

@@ -1,45 +1,33 @@
-# auth-request-gating Specification
-
 ## MODIFIED Requirements
 
 ### Requirement: Protected requests use one authentication boundary
 
-The system SHALL evaluate protected requests through one shared authentication boundary instead of scattered controller-level auth logic.
-
-#### Scenario: Valid protected request
+The system SHALL route all protected requests through a single authentication boundary instead of scattering checks across route handlers and service helpers.
 
-- **WHEN** a protected request includes valid authentication credentials
-- **THEN** the shared authentication boundary produces an authenticated request context
-- **AND** downstream handlers use that context instead of re-parsing credentials independently
+#### Scenario: Protected endpoint request
 
-#### Scenario: Missing credentials
-
-- **WHEN** a protected request arrives without required credentials
-- **THEN** the shared authentication boundary rejects the request consistently
-- **AND** the request does not continue into protected business logic
+- **WHEN** a protected endpoint receives a request
+- **THEN** the authentication boundary evaluates credentials and produces a stable auth decision before the route handler executes
 
 ### Requirement: Auth failures map consistently
 
-The system SHALL map authentication and authorization failures through standardized request-level outcomes.
+The system SHALL map unauthorized and forbidden outcomes from the authentication boundary to consistent response formats across all protected routes.
 
-#### Scenario: Invalid token
+#### Scenario: Missing credentials
 
-- **WHEN** token validation fails
-- **THEN** the request receives the standardized unauthorized outcome
-- **AND** downstream handlers are not invoked
+- **WHEN** a protected request lacks valid credentials
+- **THEN** the boundary returns an unauthorized decision and the route responds with the standard unauthorized format
 
-#### Scenario: Authenticated but forbidden
+#### Scenario: Insufficient permissions
 
-- **WHEN** the requester is authenticated but lacks required access
-- **THEN** the request receives the standardized forbidden outcome
-- **AND** the outcome is produced without ad hoc controller-specific branching
+- **WHEN** a protected request has valid credentials but insufficient permissions
+- **THEN** the boundary returns a forbidden decision and the route responds with the standard forbidden format
 
 ### Requirement: Existing approved login behavior remains unchanged
 
-The refactor SHALL preserve already approved login and session semantics while changing the internal auth boundary shape.
+The system SHALL preserve existing externally approved login and session behavior while moving request-level checks behind the new boundary.
 
-#### Scenario: Existing login flow
+#### Scenario: Successful login
 
-- **WHEN** a user signs in through the existing approved login path
-- **THEN** the resulting session or token behavior remains externally unchanged
-- **AND** the new boundary consumes the established auth artifacts without requiring a new client contract
+- **WHEN** a user completes the existing login flow
+- **THEN** session creation and token issuance behavior remains identical to the pre-refactor implementation

package/docs/solutions/INDEX.md

@@ -2,6 +2,8 @@
 <!-- 每条一行，按 severity 降序，≤150 行硬上限 -->
 | date | phase | domain | type | severity | summary | file |
 |------|-------|--------|------|----------|---------|------|
+| 2026-08-18 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-18-no-summary.md |
+| 2026-08-17 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-17-no-summary.md |
 | 2026-08-07 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-07-no-summary.md |
 | 2026-08-06 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-06-no-summary.md |
 | 2026-08-05 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-05-no-summary.md |

package/docs/solutions/cross-phase/2026-08-17-no-summary.md

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

package/docs/solutions/cross-phase/2026-08-18-no-summary.md

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