@xulthekl/team-flow 0.42.0 → 0.44.0

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

@@ -1,3 +1,3 @@
-# team-flow v0.42.0 | 阶段: {{state}} | 工作流: {{workflow}}
+# team-flow v0.44.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.42.0",
+      "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.44.0",
       "source": "./",
       "author": {
         "name": "LT",

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "team-flow",
-  "version": "0.42.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). 24 skills + 15 agents, one install.",
+  "version": "0.44.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.42.0",
+  "version": "0.44.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.42.0"
+    "version": "0.44.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.42.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.",
+  "version": "0.44.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.42.0"
+    "version": "0.44.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.42.0",
+      "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.44.0",
       "source": ".",
       "author": {
         "name": "LT",

package/.zcode/skills/workflow-start/SKILL.md

@@ -30,7 +30,7 @@ Run DP-0 when: change folder doesn't exist, planning artifacts missing/empty, or
 
 ### Upstream Inheritance (v0.9)
 
-若 `change-brief.md` 存在且 `upstream_source == orchestrator`（本 change 由 orchestrator S4 分发），**继承** brief 的 scope/约束/AC 为默认值，DP-0 从"从零问"改为"一次确认继承或修正"，**不**重新问"你想做什么"。否则（手动新建 / hotfix / 单 change 快速通道 / 存量 change 无 brief）照常 DP-0。**主信号 = brief 文件存在**（非 yaml 字段——可天然排除无 brief 的快速通道，且对存量手动 change 零误伤）；双源冲突以 `prd/vN/plan.md` 为准并触发 Brief drift（见「Staleness Detection」）。完整判定伪代码与主信号理由见 `references/routing-rules.md`「DP-0」。
+若 `change-brief.md` 存在且 `upstream_source == orchestrator`（本 change 由 orchestrator S4 分发），**继承** brief 的 scope/约束/AC 为默认值，DP-0 从"从零问"改为"一次确认继承或修正"，**不**重新问"你想做什么"。否则（手动新建 / hotfix / 单 change 快速通道 / 存量 change 无 brief）照常 DP-0。**主信号 = brief 文件存在**（非 yaml 字段——可天然排除无 brief 的快速通道，且对存量手动 change 零误伤）；双源冲突以 `requirement/vN/plan.md` 为准并触发 Brief drift（见「Staleness Detection」）。完整判定伪代码与主信号理由见 `references/routing-rules.md`「DP-0」。
 
 Ask (manual path): change name + one-sentence intent, known constraints, related optimizations (include or stay focused?), communication preference (ask per decision or draft for review).
 
@@ -119,7 +119,7 @@ Use content inspection, not timestamps.
 
 **Stale tasks**: requirement in specs has no corresponding task → stale tasks.
 
-**Brief drift (advisory, v0.9, 不阻断)**: change-brief.md 是上游输入（非 team-flow 产物），**不**混入上述三条产物互查、**不**进入 `artifacts_hash`。当 brief 的 `plan_hash` 与当前 `prd/vN/plan.md` 不一致，或 brief AC 列表与 PRD 功能清单明显出入 → 提示"产品层已变更，brief 可能过期，建议回 orchestrator 重新分发（S4→S3 环路）"，**不**触发产物重审。
+**Brief drift (advisory, v0.9, 不阻断)**: change-brief.md 是上游输入（非 team-flow 产物），**不**混入上述三条产物互查、**不**进入 `artifacts_hash`。当 brief 的 `plan_hash` 与当前 `requirement/vN/plan.md` 不一致，或 brief AC 列表与 PRD 功能清单明显出入 → 提示"产品层已变更，brief 可能过期，建议回 orchestrator 重新分发（S4→S3 环路）"，**不**触发产物重审。
 
 ## Guardrails
 

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 —— 设计/开发前先检索）
 
 ```
@@ -93,7 +98,7 @@ spec 驱动开发过程。8 态变更机：`exploring → specifying → bridgin
   ├── requirements/<req-id>/orchestrator.yaml  # 每需求产品级编排状态
   ├── handoffs/                 # 会话交接文档（v0.16.0 新增，session-handoff 产出，.gitignore）
   └── feedback/                 # 工作流问题记录（v0.16.0 新增，workflow-feedback 产出，git 跟踪）
-prd/                    PRD（有版本 v1→v2→v3，git 分支隔离）
+requirement/            PRD + 台账（有版本 v1→v2→v3，git 分支隔离）
   └── vN/
       ├── prd.md              # 业务要件（ce-brainstorm 产出）
       ├── plan.md             # 实施方案（ce-plan 产出，产品级策略）
@@ -105,7 +110,7 @@ docs/
   ├── architecture/    全局架构三层（v0.36.0）：L1 当前态（ARCHITECTURE.md marker 区 / PHYSICAL-MODEL.md / DATABASE.md / API-INDEX.md / INDEX.md / domains/<bc>.md / diagrams/ / schema-baseline.sql / baseline.md）+ L2 changelog/ + L3 iterations/vN/architecture.md（产品级快照，archived 退役）
   └── solutions/       复利经验库（v0.5 新增，三层索引）
       ├── INDEX.md     # L1 轻量索引（≤150行，每条一行摘要+标签）
-      ├── prd/ plan/ architecture/ prototype/ spec/ build/ review/ cross-phase/  # L2 分阶段目录（v0.36.0 加 architecture）
+      ├── requirement/ plan/ architecture/ prototype/ spec/ build/ review/ cross-phase/  # L2 分阶段目录（v0.36.0 加 architecture）
       └── <file>.md    # L3 经验文件（YAML frontmatter: phase/domain/type/severity）
 changes/<name>/        变更脚手架（S4 创建）：.team-flow.yaml（变更级状态文件）/ change-brief.md（产品级交接物，含 upstream_arch_ref）/ architecture/（变更级三件套 + sql/）
 specs/<cap>/            每变更设计/任务/契约：spec.md / design.md / tasks.md / execution-contract.md / learnings.md（v0.9 起 architecture/ 三件套已迁至 changes/<name>/architecture/）
@@ -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 新增）
 
@@ -244,7 +251,7 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
 ```
 docs/solutions/
 ├── INDEX.md                  # L1：轻量索引（≤150行，每条一行摘要+标签，按 severity 降序）
-├── prd/ plan/ prototype/ spec/ build/ review/ cross-phase/  # L2：分阶段目录
+├── requirement/ plan/ prototype/ spec/ build/ review/ cross-phase/  # L2：分阶段目录
 └── <date>-<summary>.md      # L3：经验文件（YAML frontmatter: phase/domain/type/severity/date/source）
 ```
 

package/CHANGELOG.md

@@ -4,9 +4,46 @@ All notable changes to `team-flow` will be documented in this file.
 
 The format loosely follows Keep a Changelog.
 
+## [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]
 
-### Added（workflow-bootstrap B5 降级路径设计 + session-start 语言要求，v0.42.0）
+## [0.43.1] - 2026-08-07
+
+### Added（closing 代码落地 + 文件存在性双层防护 + 测试执行可信度 + spec 路径契约，v0.43.1）
+
+- **`tf deisolate --merge` 健壮性增强**：dirty 阻断（未提交改动默认不合并，`--force` 跳过）/ ahead==0 短路（幂等）/ 冲突报告（unmerged 文件清单 + 非零 exit）
+- **release-archivist Step 5c Code Landing**：closing 增加代码落地检查（检测 worktree → AskUserQuestion 合并时机 → 主分支编译验证 + 依赖链顺序提示 + 冲突处理）；v0.35.0 Worktree Deisolation 段改为引用 Step 5c（MERGED/PENDING/N/A）
+- **references/worktree-merge.md（新建）**：worktree 合并规范（merge commit 不 rebase、多仓库 Case A、依赖链顺序、冲突人工处理、合并后编译验证）
+- **build-executor 任务完成前文件存在性验证**：Create 文件必须存在非空、Modify 必须有 diff，标记完成与文件存在绑定
+- **code-reviewer Step 1b File Existence Check**：tasks.md Create/Modify 清单与 git diff 求交集，缺失标 Critical（missing-file/no-change）
+- **build-executor Wave Verify**：`tf test record` 解析实际执行数量（分母排除 test_tier=e2e），<70% 警告 + 调查
+- **build-executor Test Infrastructure Check**：首 wave 前检测 surefire/JUnit @Nested 兼容性，沉淀 conventions
+- **spec-writer specs/ 路径契约**：`specs/<capability>/spec.md` 子目录结构（禁止 flat 文件）
+
+## [0.43.0] - 2026-08-07
+
+### Added（ce-brainstorm 阶段断点控制 + L1-L3 用户定义 + prd/ → requirement/ 路径收敛，v0.43.0）
+
+- **阶段断点控制（FB1）**：新增 Execution Architecture 节，4 个显式断点（BP-1 场景后 / BP-2 流程后 / BP-3 方案后 / BP-4 综合后），每个断点提供继续/暂停/回退三选项；主会话负责规划决策，子代理负责执行性产出（PRD 撰写、流程图、活动表）
+- **Phase 1.6 L1-L3 用户定义（FB3）**：Step 0 询问用户 L1-L3 流程层级规划（AI 不自行猜测），AI 聚焦 L4 子流程细化；两阶段确认（L1-L3 框架 → L4 细节逐 L3 确认）
+- **prd/ → requirement/ 路径收敛（FB2）**：新项目不再创建 `prd/` 目录，统一使用 `requirement/vN/`；PRD 输出路径改为 `requirement/vN/prd.md`；50+ 文件跨 skill/agent/template 路径更新；存量 `prd/` 保留 legacy fallback 读取兼容
+- **Phase 1.6 business-processes.md 重构**：新增 Step 0（L1-L3 用户定义）+ Step 1 重命名（聚焦 L4 推导）+ Step 5 两阶段确认
+
+## [0.42.0] - 2026-08-07
+
+### Added（workflow-bootstrap B5 降级路径设计 + session-start 语言要求）
 
 - **B5 路径决策重构（降级路径设计）**：4 平权选项 → 两组降级选项——第一组确保产物可信（A 逆向重建按复杂度分级推荐（≥5 模块或 ≥10 源文件强推）/ B 交叉验证主代理机械比对产出 cross-check-report.md / C 真实性核对用户确认门），第二组直接进入流程（D-F 原 A-C 平移）
 - **references/b5-path-decision.md（新建）**：B5 详细流程（分组展示模板、A 复杂度判据、B 比对清单 + 维度覆盖说明（architecture 显式排除理由）、C 两种模式核对协议（跟随 B / 独立抽查））

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

package/HANDOFF.md

@@ -161,7 +161,7 @@ npm run check-versions # 版本一致性守卫（当前应 ✅ 全 0.22.4）
 
 ### 5.1 全局产物结构
 ```
-prd/                    PRD（有版本 v1→v2→v3，git 分支隔离）
+requirement/            PRD + 台账（有版本 v1→v2→v3，git 分支隔离）
 prototype/             全局原型系统（UI 契约真相源）
 docs/architecture/     全局架构锚点
 specs/<cap>/            每变更设计/任务/契约

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.42.0**。
+当前发布版本：**v0.44.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.42.0`
+> 当前版本：`v0.44.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。
 
 ## 配置（插件层扩展字段）
 
@@ -56,12 +56,12 @@ git clone <your-repo> && <cli> plugin install ./team-flow
 cp -r <plugin>/skills/prototype/references/prototype-scaffold/ <project>/prototype/
 ```
 
-随后按 `prototype/design-system.md` 填 token；`prototype/` 与 `prd/` 同级、git 分支隔离版本。
+随后按 `prototype/design-system.md` 填 token；`prototype/` 与 `requirement/` 同级、git 分支隔离版本。
 
 ## 全局产物结构
 
 ```
-prd/               PRD + 实施方案 + 原型审查记录（v1→v2，分支隔离）
+requirement/       PRD + 台账 + 实施方案 + 原型审查记录（v1→v2，分支隔离）
 prototype/         全局原型（UI 契约真相源）
 docs/
   ├── architecture/  全局架构三层（v0.36.0）：ARCHITECTURE.md / PHYSICAL-MODEL.md / DATABASE.md / API-INDEX.md / INDEX.md / domains/<bc>.md / iterations/vN/（产品级快照）/ baseline.md
@@ -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/architecture-design.md

@@ -36,7 +36,7 @@ You are an independent architecture designer. You read the change brief, plan, e
 |-----------|-------------|
 | `mode` | `change`（默认，workflow-start 五项检查）\| `product`（v0.36.0，S3.5 产品级架构设计） |
 | `change_brief_path` | change-brief.md 路径（scope / AC / 技术方向；change 模式必填） |
-| `plan_path` | prd/vN/plan.md 路径（高阶技术设计段） |
+| `plan_path` | requirement/vN/plan.md 路径（高阶技术设计段） |
 | `snapshot_path` | docs/architecture/iterations/vN/architecture.md（产品级快照；change 模式主输入，product 模式产出目标） |
 | `specs_dir` | changes/<name>/specs/ 路径（现有规格，如有） |
 | `global_arch_dir` | docs/architecture/ 路径（As-Is 基线） |
@@ -108,7 +108,7 @@ verdict: pending_review          # 评审门（architecture-reviewer product 视
 - Execute five-check gate BEFORE producing any deliverable
 - Produce standalone executable SQL files, not embedded code blocks
 - Cite specific brief sections and plan sections for every architecture decision
-- **Produce a PRD Feature → API Endpoint mapping table in api.md** (v0.29.0 §37): before finalizing the API routing table, read `prd/vN/prd.md` feature list (e.g., F001_P0_P1 ~ P0_PN) and map each feature to its corresponding API endpoint(s). For features involving sub-entities (明细/子项), ensure independent CRUD endpoints exist — a query-only endpoint does NOT cover "新增/编辑" functionality. Include this mapping as a dedicated section in api.md for traceability
+- **Produce a PRD Feature → API Endpoint mapping table in api.md** (v0.29.0 §37): before finalizing the API routing table, read `requirement/vN/prd.md` feature list (e.g., F001_P0_P1 ~ P0_PN) and map each feature to its corresponding API endpoint(s). For features involving sub-entities (明细/子项), ensure independent CRUD endpoints exist — a query-only endpoint does NOT cover "新增/编辑" functionality. Include this mapping as a dedicated section in api.md for traceability
 
 **DON'T:**
 - Skip the five-check gate and jump to design

package/agents/architecture-reviewer.md

@@ -21,8 +21,8 @@ After writing, return a summary of the verdict + the report file path. Do NOT mo
 
 | Parameter | Description |
 |-----------|-------------|
-| `prd_path` | PRD 文件路径（e.g., `prd/v1/prd.md`） |
-| `plan_path` | plan.md 路径（e.g., `prd/v1/plan.md`） |
+| `prd_path` | PRD 文件路径（e.g., `requirement/v1/prd.md`） |
+| `plan_path` | plan.md 路径（e.g., `requirement/v1/plan.md`） |
 | `change_brief_path` | change-brief.md 路径（e.g., `changes/<name>/change-brief.md`） |
 | `architecture_dir` | 架构产出目录（e.g., `changes/<name>/architecture/`） |
 | `global_arch_dir` | 全局架构目录（e.g., `docs/architecture/`） |
@@ -90,7 +90,7 @@ Dimensions requiring semantic understanding, marked as "advisory, false positive
 
 4. **A4 需求覆盖** (v0.29.0 §37 增强：双对照源 + 子实体 CRUD 检查):
    - **对照源 1（现有）**：Read change-brief.md → extract all requirement items (scope, AC, technical direction)
-   - **对照源 2（v0.29.0 新增）**：Read `prd/vN/prd.md` → extract feature list (e.g., F001_P0_P1 ~ P0_PN)
+   - **对照源 2（v0.29.0 新增）**：Read `requirement/vN/prd.md` → extract feature list (e.g., F001_P0_P1 ~ P0_PN)
    - Read plan.md → extract relevant technical design sections
    - For each requirement from BOTH sources, check if architecture deliverables provide corresponding design:
      - New aggregate → architecture.md covers it?

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/agents/change-split-auditor.md

@@ -11,14 +11,14 @@ You are an independent Change Split Auditor. You audit the quality of a plan.md'
 
 ## The Iron Law
 
-You are an auditor. You did NOT produce the plan or the PRD. You read both artifacts, cross-reference them, and produce a verdict with findings. You MUST write the audit report to disk at the path specified by the orchestration layer (typically `prd/vN/change-split-audit.md`). On FAIL, the orchestration layer carries your findings back to ce-plan for deepening. Do NOT modify plan.md or PRD — only write the audit report.
+You are an auditor. You did NOT produce the plan or the PRD. You read both artifacts, cross-reference them, and produce a verdict with findings. You MUST write the audit report to disk at the path specified by the orchestration layer (typically `requirement/vN/change-split-audit.md`). On FAIL, the orchestration layer carries your findings back to ce-plan for deepening. Do NOT modify plan.md or PRD — only write the audit report.
 
 ## Inputs
 
 | Parameter | Description |
 |-----------|-------------|
-| `plan_path` | plan.md 路径（e.g., `prd/v1/plan.md`） |
-| `prd_path` | PRD 文件路径（e.g., `prd/v1/prd.md`） |
+| `plan_path` | plan.md 路径（e.g., `requirement/v1/plan.md`） |
+| `prd_path` | PRD 文件路径（e.g., `requirement/v1/prd.md`） |
 
 If either path is missing or unreadable, report `FAIL` with reason `INPUT_ERROR`.
 

package/agents/need-explorer.md

@@ -23,7 +23,7 @@ You stabilize intent, not build. Ask one clear question at a time, propose 2-3 a
 |-----------|-------------|
 | `change_dir` | change 目录路径（e.g., `changes/feature-x/`） |
 | `brief_path` | change-brief.md 路径（可选,workflow-orchestrator S4 分发时存在,先读再问） |
-| `plan_path` | prd/vN/plan.md 路径（可选,brief 冲突时以 plan.md 为准） |
+| `plan_path` | requirement/vN/plan.md 路径（可选,brief 冲突时以 plan.md 为准） |
 
 If `change_dir` is missing or unreadable, report `FAIL` with reason `INPUT_ERROR` and route back to workflow-start.
 

package/agents/prd-completeness-reviewer.md

@@ -11,7 +11,7 @@ You are an independent PRD Completeness Reviewer. You check whether a PRD is **c
 
 ## The Iron Law
 
-You are an independent reviewer. You did NOT participate in producing the PRD. You read the PRD (and CONCEPTS.md if present) fresh and assess whether the requirement description is complete enough to be actionable. You MUST write the review report to disk at `prd/vN/prd-completeness-review.md`. Do NOT modify the PRD or any other artifact — only write the review report.
+You are an independent reviewer. You did NOT participate in producing the PRD. You read the PRD (and CONCEPTS.md if present) fresh and assess whether the requirement description is complete enough to be actionable. You MUST write the review report to disk at `requirement/vN/prd-completeness-review.md`. Do NOT modify the PRD or any other artifact — only write the review report.
 
 ## Division of Labor with claim verifier
 
@@ -24,7 +24,7 @@ Do NOT duplicate claim verification. A statement can be factually correct yet st
 
 | Parameter | Description |
 |-----------|-------------|
-| `prd_path` | PRD 文件路径（e.g., `prd/v1/prd.md`） |
+| `prd_path` | PRD 文件路径（e.g., `requirement/v1/prd.md`） |
 | `concepts_path` | （可选）CONCEPTS.md 路径，用于术语一致性比对 |
 
 If `prd_path` is missing or unreadable, report `FAIL` with reason `INPUT_ERROR`.