@xulthekl/team-flow 0.43.1 → 0.44.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (29) hide show
  1. package/.claude/always/phase-guard.md +1 -1
  2. package/.claude-plugin/marketplace.json +3 -3
  3. package/.claude-plugin/plugin.json +2 -2
  4. package/.codex-plugin/plugin.json +2 -2
  5. package/.cursor-plugin/marketplace.json +2 -2
  6. package/.cursor-plugin/plugin.json +2 -2
  7. package/.github/plugin/marketplace.json +3 -3
  8. package/AGENTS.md +13 -6
  9. package/CHANGELOG.md +15 -0
  10. package/GEMINI.md +1 -1
  11. package/INSTALL.md +26 -24
  12. package/README.md +6 -5
  13. package/agents/business-analysis.md +53 -0
  14. package/docs/README_en.md +1 -1
  15. package/docs/examples/add-dark-mode/specs/ui-theme/spec.md +15 -17
  16. package/docs/examples/refactor-auth-boundary/specs/auth-boundary/spec.md +15 -27
  17. package/docs/solutions/INDEX.md +1 -0
  18. package/docs/solutions/cross-phase/2026-08-17-no-summary.md +17 -0
  19. package/docs/usage-guide.md +619 -0
  20. package/gemini-extension.json +2 -2
  21. package/hooks/session-start +2 -2
  22. package/llms.txt +1 -1
  23. package/package.json +2 -2
  24. package/plugin.json +2 -2
  25. package/skills/business-analysis/SKILL.md +80 -0
  26. package/skills/business-analysis/references/interaction-rules.md +86 -0
  27. package/skills/business-analysis/references/output-schema.md +88 -0
  28. package/skills/business-analysis/references/qa-checklist.md +31 -0
  29. package/skills/business-analysis/references/version-resolution.md +41 -0
package/.claude/always/phase-guard.md CHANGED
@@ -1,3 +1,3 @@
1
- # team-flow v0.43.1 | 阶段: {{state}} | 工作流: {{workflow}}
1
+ # team-flow v0.44.0 | 阶段: {{state}} | 工作流: {{workflow}}
2
2
  当前阶段允许的操作由 workflow-start 路由规则定义。
3
3
  禁止跨越 DP gate 进入下一阶段。变更范围以 execution-contract.md 的 Intent Lock 为准。
package/.claude-plugin/marketplace.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "team-flow",
3
- "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.",
3
+ "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.",
4
4
  "owner": {
5
5
  "name": "LT",
6
6
  "url": "https://github.com/LT"
@@ -8,8 +8,8 @@
8
8
  "plugins": [
9
9
  {
10
10
  "name": "team-flow",
11
- "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.",
12
- "version": "0.43.1",
11
+ "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.",
12
+ "version": "0.44.0",
13
13
  "source": "./",
14
14
  "author": {
15
15
  "name": "LT",
package/.claude-plugin/plugin.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "team-flow",
3
- "version": "0.43.1",
4
- "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.",
3
+ "version": "0.44.0",
4
+ "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.",
5
5
  "source": "./",
6
6
  "author": {
7
7
  "name": "LT",
package/.codex-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "team-flow",
3
- "version": "0.43.1",
3
+ "version": "0.44.0",
4
4
  "description": "Spec-first workflow that bridges OpenSpec-style planning and Superpowers-style execution discipline.",
5
5
  "author": {
6
6
  "name": "MageByte",
@@ -26,7 +26,7 @@
26
26
  "interface": {
27
27
  "displayName": "team-flow",
28
28
  "shortDescription": "Spec-first workflow with guarded execution.",
29
- "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.",
29
+ "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.",
30
30
  "developerName": "MageByte",
31
31
  "category": "Developer Tools",
32
32
  "composerIcon": "./assets/icon.svg",
package/.cursor-plugin/marketplace.json CHANGED
@@ -5,13 +5,13 @@
5
5
  },
6
6
  "metadata": {
7
7
  "description": "Unified workflow plugin marketplace for Cursor (team-flow: team-flow + compound + architecture-design + prototype).",
8
- "version": "0.43.1"
8
+ "version": "0.44.0"
9
9
  },
10
10
  "plugins": [
11
11
  {
12
12
  "name": "team-flow",
13
13
  "source": ".",
14
- "description": "Unified workflow plugin: team-flow + compound-engineering core subset + architecture-design + prototype. 24 skills + 15 agents."
14
+ "description": "Unified workflow plugin: team-flow + compound-engineering core subset + architecture-design + prototype + business-analysis. 25 skills + 16 agents."
15
15
  }
16
16
  ]
17
17
  }
package/.cursor-plugin/plugin.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "team-flow",
3
3
  "displayName": "team-flow",
4
- "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.",
5
- "version": "0.43.1",
4
+ "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.",
5
+ "version": "0.44.0",
6
6
  "author": {
7
7
  "name": "LT",
8
8
  "url": "https://github.com/LT"
package/.github/plugin/marketplace.json CHANGED
@@ -6,13 +6,13 @@
6
6
  },
7
7
  "metadata": {
8
8
  "description": "Unified workflow plugins and skills for AI coding agents (team-flow: team-flow + compound + architecture-design + prototype).",
9
- "version": "0.43.1"
9
+ "version": "0.44.0"
10
10
  },
11
11
  "plugins": [
12
12
  {
13
13
  "name": "team-flow",
14
- "description": "Unified workflow with planning artifacts, execution contracts, TDD, review gates, systematic debugging, delta spec sync, architecture-design, and local HTML prototyping.",
15
- "version": "0.43.1",
14
+ "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.",
15
+ "version": "0.44.0",
16
16
  "source": ".",
17
17
  "author": {
18
18
  "name": "LT",
package/AGENTS.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # AGENTS.md · team-flow
2
2
 
3
- > 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）。
3
+ > 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）。
4
4
 
5
5
  ## What This Is
6
6
 
@@ -12,7 +12,7 @@
12
12
 
13
13
  ### 身份与依赖关系
14
14
 
15
- - **team-flow**（本插件）：Claude Code / Cursor 等宿主的插件实体（`plugin.json` name = `team-flow`），包含 24 个 skills + 15 个 agents + hooks + templates
15
+ - **team-flow**（本插件）：Claude Code / Cursor 等宿主的插件实体（`plugin.json` name = `team-flow`），包含 25 个 skills + 16 个 agents + hooks + templates
16
16
  - **@xulthekl/team-flow**（npm 底座包）：team-flow 的 CLI 工具层（`package.json` name = `@xulthekl/team-flow`，bin = `tf` / `team-flow`），提供状态机、校验、复利 CLI 等运行时能力
17
17
  - 关系：team-flow 插件 **包含** @xulthekl/team-flow npm 包作为底座（同一仓库、同一版本）。skills 中的 `tf ...` 调用的是已全局安装的 @xulthekl/team-flow CLI，版本由 session-start hook 自动同步
18
18
  - 历史身份（已废弃）：`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"
33
33
  npm run validate
34
34
  ```
35
35
 
36
- ## 能力概览（九套合一，24 skills）
36
+ ## 能力概览（十套合一，25 skills）
37
37
 
38
38
  ### 1. team-flow（底座，9 skills）
39
39
  spec 驱动开发过程。8 态变更机：`exploring → specifying → bridging → approved-for-build → executing → closing`（另有 `debugging` 侧路径 + `abandoned` 终态）。
@@ -85,6 +85,11 @@ spec 驱动开发过程。8 态变更机：`exploring → specifying → bridgin
85
85
  - 输出到 `.team-flow/feedback/`（git 跟踪，改进输入持久化）
86
86
  - release-archivist 收尾时联动建议触发
87
87
 
88
+ ### 10. business-analysis（1 skill，独立业务分析工具）
89
+ - 将任意用户输入整理为 `requirement/vN/business-analysis.md`，产出 Requirements List 与 Scenario List
90
+ - 支持多轮单问澄清、待办记录、新增/更新模式，写入前必须阻塞用户确认
91
+ - 不进入核心工作流，作为独立外挂工具运行
92
+
88
93
  ## 全局产物结构（Discoverability —— 设计/开发前先检索）
89
94
 
90
95
  ```
@@ -169,7 +174,7 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
169
174
  全局作为下一 change / 下一 PRD 版本的 grounding → 闭环
170
175
  ```
171
176
 
172
- ## Skills 索引（24 个）
177
+ ## Skills 索引（25 个）
173
178
 
174
179
  | Skill | 归属 | 用途 |
175
180
  |---|---|---|
@@ -197,6 +202,7 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
197
202
  | workflow-bootstrap | 既有项目接入 | 既有项目侦察+基线建立（v0.6） |
198
203
  | session-handoff | 会话交接 | 上下文腐化时压缩会话为交接文档（v0.16.0） |
199
204
  | workflow-feedback | 工作流反馈 | 工作流问题结构化记录（v0.16.0） |
205
+ | business-analysis | 独立业务分析 | 将任意输入整理为 requirement/vN/business-analysis.md（独立外挂，v0.44.0） |
200
206
 
201
207
  ### 触发域分层（v0.12.0 新增）
202
208
 
@@ -207,13 +213,13 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
207
213
  | 接入层 | workflow-bootstrap | "初始化/接入/分析代码库" | 一次性，触发词独特，无冲突 |
208
214
  | 产品级（唯一入口） | **workflow-orchestrator** | 新的产品级需求（"新需求/从头开始/我有个想法/做一个XX"） | 拥有所有"产品级新需求"触发词，内部路由到 ce-brainstorm/ce-plan |
209
215
  | 变更级（唯一入口） | workflow-start | change 上下文内的操作（.team-flow.yaml） | 有强上下文约束，与产品级天然隔离 |
210
- | 步骤级 - 独立工具 | ce-ideate, ce-strategy, ce-compound, ce-proof, architecture-design, prototype, e2e, session-handoff, workflow-feedback | 各自独特触发词 | 无冲突，可独立触发 |
216
+ | 步骤级 - 独立工具 | ce-ideate, ce-strategy, ce-compound, ce-proof, architecture-design, prototype, e2e, session-handoff, workflow-feedback, **business-analysis** | 各自独特触发词 | 无冲突，可独立触发；business-analysis 不进入核心工作流 |
211
217
  | 步骤级 - 受限独立 | ce-brainstorm, ce-plan | 可独立触发，但产品级新需求应走 orchestrator | description 中标注路由指导 |
212
218
  | 步骤级 - 仅路由 | need-explorer, spec-writer, contract-builder, build-executor, code-reviewer, spec-merger, release-archivist, bug-investigator | 仅由 workflow-start 路由 | 不独立触发 |
213
219
 
214
220
  > **规则**：新增 skill 时必须在此表登记所属层级。产品级新需求触发词归 workflow-orchestrator 独占。
215
221
 
216
- ### Agents 索引（v0.7 新增，v0.30.0 增至 15 个）
222
+ ### Agents 索引（v0.7 新增，v0.30.0 增至 16 个）
217
223
 
218
224
  > **agent 文件设计规范见 CONTRIBUTING.md §6 + `templates/agent-template.md`**（v0.33.0）：frontmatter 必须合法 YAML（非法时 Claude Code 静默降级，skills: 预加载与 tools: 限制全部失效）；description 单句、禁 `<example>` 块；新增/修改 agent 必过 frontmatter-lint + 实证探针。
219
225
 
@@ -234,6 +240,7 @@ STRATEGY.md CONCEPTS.md 产品策略(BA) / 领域词汇
234
240
  | contract-builder | 执行契约 agent——将规划制品压缩为单一执行握手 execution-contract.md、守 DP-3 批准门（可写型，契约文件唯一所有者；spec-writer DP-2 后、build-executor 前） | Read/Bash/Grep/Glob/Write/Edit | workflow-start 路由时作为子代理 dispatch |
235
241
  | build-executor | 构建执行 agent——以契约为权威驱动 TDD 批次实施（SDD/Inline/Batch Inline）、守 TDD Iron Law（可写型，实施代码所有者；契约 DP-3 批准后、release-archivist 前） | Read/Bash/Grep/Glob/Write/Edit | workflow-start 路由时作为子代理 dispatch |
236
242
  | release-archivist | 发布归档 agent——执行验证、产出 closing 总结、完成归档就绪（arch-merge → prototype-sync → 复利晋升）（可写型，归档制品所有者；build-executor 后、change 关闭前） | Read/Bash/Grep/Glob/Write/Edit | workflow-start 路由时作为子代理 dispatch |
243
+ | business-analysis | 独立业务分析 agent——将任意输入整理为 requirement/vN/business-analysis.md，多轮单问澄清、待办记录、新增/更新模式，写入前阻塞确认 | Read/Bash/Grep/Glob/Write/Edit | 独立触发，不进入 workflow-orchestrator 核心流程（v0.44.0） |
237
244
 
238
245
  ## 复利贯穿机制（v0.5 新增）
239
246
 
package/CHANGELOG.md CHANGED
@@ -4,8 +4,23 @@ All notable changes to `team-flow` will be documented in this file.
4
4
 
5
5
  The format loosely follows Keep a Changelog.
6
6
 
7
+ ## [0.44.0] - 2026-08-17
8
+
9
+ ### Added（独立 business-analysis skill/agent，v0.44.0）
10
+
11
+ - **新增 `skills/business-analysis/`**：独立业务分析 skill，将任意用户输入整理为 `requirement/vN/business-analysis.md`，产出 Requirements List 与 Scenario List
12
+ - **新增 `agents/business-analysis.md`**：配套独立 agent，`tools` 含 Read/Bash/Grep/Glob/Write/Edit，写入前必须阻塞用户确认
13
+ - **多轮单问澄清协议**：每次只问 1 个问题，用户无法回答时记录为 `TODO-xxx`，相关条目保持 🔵 pending
14
+ - **版本解析规则**：支持显式参数 / `tf runtime config --get active.requirement` / `requirement/` 目录扫描 / 默认 `v1`
15
+ - **输出格式契约**：只含需求列表 + 业务场景列表 + Open Questions/TODOs，禁止写入 `ledger.md`、PRD、流程、架构、`.team-flow.yaml`
16
+ - **QA 检查清单**：5 项 Error 检查（角色覆盖、六维度齐全、REQ 引用存在、对话证据可追溯、Acceptance 可测试）
17
+ - **技能/Agent 计数同步**：24 skills + 15 agents → 25 skills + 16 agents，plugin.json / marketplace.json / README.md / AGENTS.md / package.json / gemini-extension.json 等同步更新
18
+ - **测试覆盖**：`tests/lib/cmd-install-workbuddy.test.mjs` 技能数断言更新为 25；保留 `docs/examples/*/specs/` 示例目录（`.gitignore` 例外规则）
19
+
7
20
  ## [Unreleased]
8
21
 
22
+ ## [0.43.1] - 2026-08-07
23
+
9
24
  ### Added（closing 代码落地 + 文件存在性双层防护 + 测试执行可信度 + spec 路径契约，v0.43.1）
10
25
 
11
26
  - **`tf deisolate --merge` 健壮性增强**：dirty 阻断（未提交改动默认不合并，`--force` 跳过）/ ahead==0 短路（幂等）/ 冲突报告（unmerged 文件清单 + 非零 exit）
package/GEMINI.md CHANGED
@@ -8,7 +8,7 @@ The workflow is self-contained and does not require OpenSpec or Superpowers at r
8
8
 
9
9
 
10
10
  <!-- team-flow-phase-guard-start -->
11
- # team-flow v0.43.1 | 阶段: {{state}} | 工作流: {{workflow}}
11
+ # team-flow v0.44.0 | 阶段: {{state}} | 工作流: {{workflow}}
12
12
  当前阶段允许的操作由 workflow-start 路由规则定义。
13
13
  禁止跨越 DP gate 进入下一阶段。变更范围以 execution-contract.md 的 Intent Lock 为准。
14
14
  <!-- team-flow-phase-guard-end -->
package/INSTALL.md CHANGED
@@ -7,32 +7,34 @@
7
7
  - [Fission-AI/OpenSpec](https://github.com/Fission-AI/OpenSpec) — 规划引擎（Schema 验证、Delta Spec、工件解析）
8
8
  - [obra/superpowers](https://github.com/obra/superpowers) — 执行纪律（TDD 铁律、SDD、系统化调试、代码审查）
9
9
 
10
- 当前发布版本：**v0.43.1**。
10
+ 当前发布版本：**v0.44.0**。
11
11
 
12
12
  ---
13
13
 
14
14
  ## 平台总览
15
15
 
16
- | 平台 | 安装 | 升级 | 卸载 |
17
- |------|------|------|------|
18
- | Claude Code | marketplace | `/plugin update` | `/plugin uninstall` |
19
- | Cursor | skills 目录 / GitHub 导入 / 一键脚本 | 重新运行脚本 | 删除 `.cursor/skills/` |
20
- | OpenAI Codex CLI | Plugin Directory / marketplace | marketplace refresh + re-add | `codex plugin remove` |
21
- | OpenAI Codex App | Plugins 面板 / marketplace | CLI 更新后 App 面板启用 | App 面板禁用 |
22
- | GitHub Copilot CLI | marketplace | `copilot plugin update` | `copilot plugin uninstall` |
23
- | Gemini CLI | `gemini extensions install` | `gemini extensions update` | `gemini extensions uninstall` |
24
- | OpenCode | plugin entry / skills 目录 | `git pull` | 删除 plugin/skills |
25
- | WorkBuddy | `tf install-workbuddy` | 重新运行安装器 | 删除 marketplace 插件并禁用 |
26
- | Trae IDE / TRAE Work | `.trae/skills` / 上传 zip 或 .skill / marketplace | `git pull` + 重新导入 | UI 卸载或删除技能目录 |
27
- | Cline | `tf install-cline` | 重新运行脚本 | 删除 `.cline/skills/`、`.clinerules/` |
28
- | Kiro | `tf install-kiro` | 重新运行脚本 | 删除 `.kiro/skills/`、`.kiro/steering/` |
29
- | Windsurf | `tf install-windsurf` | 重新运行脚本 | 删除 `.windsurf/skills/`、`.windsurf/rules/` |
30
- | Qwen Code | `tf install-qwen` | 重新运行脚本 | 删除 `.qwen/skills/`、`.qwen/rules/` |
31
- | Amazon Q Developer | `tf install-amazon-q` | 重新运行脚本 | 删除 `.amazonq/skills/`、`.amazonq/rules/` |
32
- | Roo Code | `tf install-roocode` | 重新运行脚本 | 删除 `.roo/skills/`、`.roo/rules/` |
33
- | Continue | `tf install-continue` | 重新运行脚本 | 删除 `.continue/skills/`、`.continue/rules/` |
34
- | Pi | `tf install-pi` | 重新运行脚本 | 删除 `.pi/skills/` |
35
- | ZCODE | `tf install-zcode` | 重新运行脚本 | 删除 `.zcode/skills/`、`.zcode/rules/` |
16
+
17
+ | 平台 | 安装 | 升级 | 卸载 |
18
+ | -------------------- | ---------------------------------------------- | ---------------------------- | ----------------------------------------- |
19
+ | Claude Code | marketplace | `/plugin update` | `/plugin uninstall` |
20
+ | Cursor | skills 目录 / GitHub 导入 / 一键脚本 | 重新运行脚本 | 删除 `.cursor/skills/` |
21
+ | OpenAI Codex CLI | Plugin Directory / marketplace | marketplace refresh + re-add | `codex plugin remove` |
22
+ | OpenAI Codex App | Plugins 面板 / marketplace | CLI 更新后 App 面板启用 | App 面板禁用 |
23
+ | GitHub Copilot CLI | marketplace | `copilot plugin update` | `copilot plugin uninstall` |
24
+ | Gemini CLI | `gemini extensions install` | `gemini extensions update` | `gemini extensions uninstall` |
25
+ | OpenCode | plugin entry / skills 目录 | `git pull` | 删除 plugin/skills |
26
+ | WorkBuddy | `tf install-workbuddy` | 重新运行安装器 | 删除 marketplace 插件并禁用 |
27
+ | Trae IDE / TRAE Work | `.trae/skills` / 上传 zip 或 .skill / marketplace | `git pull` + 重新导入 | UI 卸载或删除技能目录 |
28
+ | Cline | `tf install-cline` | 重新运行脚本 | 删除 `.cline/skills/`、`.clinerules/` |
29
+ | Kiro | `tf install-kiro` | 重新运行脚本 | 删除 `.kiro/skills/`、`.kiro/steering/` |
30
+ | Windsurf | `tf install-windsurf` | 重新运行脚本 | 删除 `.windsurf/skills/`、`.windsurf/rules/` |
31
+ | Qwen Code | `tf install-qwen` | 重新运行脚本 | 删除 `.qwen/skills/`、`.qwen/rules/` |
32
+ | Amazon Q Developer | `tf install-amazon-q` | 重新运行脚本 | 删除 `.amazonq/skills/`、`.amazonq/rules/` |
33
+ | Roo Code | `tf install-roocode` | 重新运行脚本 | 删除 `.roo/skills/`、`.roo/rules/` |
34
+ | Continue | `tf install-continue` | 重新运行脚本 | 删除 `.continue/skills/`、`.continue/rules/` |
35
+ | Pi | `tf install-pi` | 重新运行脚本 | 删除 `.pi/skills/` |
36
+ | ZCODE | `tf install-zcode` | 重新运行脚本 | 删除 `.zcode/skills/`、`.zcode/rules/` |
37
+
36
38
 
37
39
  ---
38
40
 
@@ -41,7 +43,7 @@
41
43
  ### 安装（推荐：Marketplace）
42
44
 
43
45
  ```bash
44
- /plugin marketplace add MageByte-Zero/team-flow
46
+ /plugin marketplace add http://team:glpat-qyqtVEKeE3eu6EfrohoAEm86MQp1OjEyOQk.01.0z1ft22h9@172.25.254.5:10080/d40050-gtmc-ai/team-flow.git
45
47
  /plugin install team-flow@team-flow
46
48
  ```
47
49
 
@@ -64,7 +66,7 @@
64
66
  ### 本地安装（开发 / 离线）
65
67
 
66
68
  ```bash
67
- git clone https://github.com/MageByte-Zero/team-flow.git
69
+ git clone http://team:glpat-qyqtVEKeE3eu6EfrohoAEm86MQp1OjEyOQk.01.0z1ft22h9@172.25.254.5:10080/d40050-gtmc-ai/team-flow.git
68
70
 
69
71
  # 在 Claude Code 中执行：
70
72
  /plugin install file:/absolute/path/to/team-flow
@@ -807,4 +809,4 @@ Checkpoint 是任务级恢复上下文。`result-ready` handoff 在继续受影
807
809
 
808
810
  推荐流程：`exploring -> specifying -> bridging -> approved-for-build -> execution plan -> executing -> closing`
809
811
 
810
- hotfix 快速路径：`exploring -> bridging -> approved-for-build -> executing`。hotfix 可以跳过完整的 `proposal.md`、`design.md`、`tasks.md`、`specs/`，但仍然必须先生成一份新的最小 `execution-contract.md`，并完成 DP-3 批准后才能开始实现。
812
+ hotfix 快速路径：`exploring -> bridging -> approved-for-build -> executing`。hotfix 可以跳过完整的 `proposal.md`、`design.md`、`tasks.md`、`specs/`，但仍然必须先生成一份新的最小 `execution-contract.md`，并完成 DP-3 批准后才能开始实现。
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # team-flow
2
2
 
3
- > 当前版本：`v0.43.1`
3
+ > 当前版本：`v0.44.0`
4
4
 
5
5
  > 统一插件：**team-flow**（spec 驱动开发）+ **compound-engineering 核心子集**（全局复利）+ **architecture-design**（4A+DDD 增量设计）+ **prototype**（本地 HTML 原型）+ **e2e**（AC 驱动 E2E）+ **workflow-orchestrator**（产品级编排）+ **workflow-bootstrap**（既有项目接入）。一次安装，七套能力协同。
6
6
 
@@ -34,7 +34,7 @@
34
34
  git clone <your-repo> && <cli> plugin install ./team-flow
35
35
  ```
36
36
 
37
- > 不同宿主 CLI 的安装子命令略有差异（如 Claude Code 为 `/plugin add`，Cursor 为 `plugin install`）。以宿主文档为准；本插件提供单一 `plugin.json`，一次安装即加载全部 24 个 skills。
37
+ > 不同宿主 CLI 的安装子命令略有差异（如 Claude Code 为 `/plugin add`，Cursor 为 `plugin install`）。以宿主文档为准；本插件提供单一 `plugin.json`，一次安装即加载全部 25 个 skills。
38
38
 
39
39
  ## 配置（插件层扩展字段）
40
40
 
@@ -70,7 +70,7 @@ specs/<cap>/ 每变更设计/任务/契约 + learnings.md
70
70
  STRATEGY.md CONCEPTS.md 策略 / 领域词汇
71
71
  ```
72
72
 
73
- ## 九套能力（24 skills）
73
+ ## 十套能力（25 skills）
74
74
 
75
75
  - **team-flow**（9）：workflow-start / need-explorer / spec-writer / contract-builder / build-executor / code-reviewer / spec-merger / release-archivist / bug-investigator
76
76
  - **compound 核心子集**（6）：ce-brainstorm / ce-plan / ce-compound / ce-strategy / ce-ideate / ce-proof
@@ -82,10 +82,11 @@ STRATEGY.md CONCEPTS.md 策略 / 领域词汇
82
82
  - **会话交接**（1）：session-handoff（上下文腐化时压缩会话为交接文档，v0.16.0）
83
83
  - **工作流反馈**（1）：workflow-feedback（工作流问题结构化记录，与 ce-compound 互补，v0.16.0）
84
84
  - **设计系统**（1）：design-system（独立创建/迭代项目级设计系统，用户主导交互，v0.19.0）
85
+ - **业务分析**（1）：business-analysis（将任意输入整理为 requirement/vN/business-analysis.md，多轮单问澄清，独立外挂，v0.44.0）
85
86
 
86
- ### 配套 agents（15 个，v0.30.0 增至 15）
87
+ ### 配套 agents（16 个，v0.30.0 增至 16）
87
88
 
88
- 全部由编排层 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（发布归档）。
89
+ 全部由编排层 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（独立业务分析）。
89
90
 
90
91
  ### 命名约定
91
92
 
package/agents/business-analysis.md ADDED
@@ -0,0 +1,53 @@
1
+ ---
2
+ name: business-analysis
3
+ description: "独立业务分析 agent：交互式整理 requirement/vN/business-analysis.md，产出 Requirements List 与 Scenario List，支持多轮单问澄清与待办记录，写入前必须阻塞用户确认。"
4
+ model: inherit
5
+ color: blue
6
+ tools: ["Read", "Bash", "Grep", "Glob", "Write", "Edit"]
7
+ skills:
8
+ - business-analysis
9
+ ---
10
+
11
+ 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`.
12
+
13
+ **Your preloaded Skill contains the detailed methodology.** Follow it for HOW. This prompt defines WHO you are and WHAT you must deliver.
14
+
15
+ ## Artifact Ownership
16
+
17
+ You are the sole owner of `requirement/vN/business-analysis.md`. No other agent or orchestrator should modify this file directly.
18
+
19
+ ## Inputs
20
+
21
+ | Parameter | Description |
22
+ |-----------|-------------|
23
+ | `user_input` | Raw user input: a sentence, document, meeting notes, etc. |
24
+ | `version` | Target version, e.g. `v1`; auto-resolved if omitted |
25
+
26
+ ## Structured Output Contract
27
+
28
+ Return the following YAML to the caller after each interaction:
29
+
30
+ ```yaml
31
+ status: drafting | waiting_for_user | confirmed | blocked
32
+ version: vN
33
+ artifact_path: requirement/vN/business-analysis.md
34
+ open_todos: []
35
+ summary: "..."
36
+ ```
37
+
38
+ ## Red Lines
39
+
40
+ **DO:**
41
+ - Ask one question at a time
42
+ - Record unanswered questions as TODOs in `## Open Questions / TODOs`
43
+ - Keep entries as 🔵 pending until the user explicitly confirms them
44
+ - Write acceptance criteria that are concrete and testable
45
+
46
+ **DON'T:**
47
+ - DO NOT write `ledger.md`
48
+ - DO NOT modify `.team-flow.yaml` state or workflow fields
49
+ - DO NOT use generic roles like "user"
50
+ - DO NOT produce untestable acceptance criteria
51
+ - DO NOT write process flow details, Mermaid diagrams, or L1-L4 process tables
52
+
53
+ End your final response with an explicit terminal marker line: `FINAL VERDICT: <DONE | BLOCKED | FAIL>`
package/docs/README_en.md CHANGED
@@ -126,7 +126,7 @@ npm install -g team-flow
126
126
 
127
127
  ### Version
128
128
 
129
- - Current: `v0.43.1`
129
+ - Current: `v0.44.0`
130
130
  - 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.
131
131
  - Self-contained — no OpenSpec or Superpowers runtime required
132
132
  - 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 CHANGED
@@ -1,35 +1,33 @@
1
- # Capability Spec
2
-
3
1
  ## ADDED Requirements
4
2
 
5
3
  ### Requirement: User can use dark mode
6
4
 
7
- The system SHALL provide a dark theme variant for the primary user interface.
5
+ The system SHALL provide a user-facing dark mode for the web UI that can be toggled between light and dark themes.
8
6
 
9
- #### Scenario: Initial load follows system preference
7
+ #### Scenario: Manual toggle
10
8
 
11
- - **WHEN** a first-time visitor opens the application and has no saved theme preference
12
- - **THEN** the interface uses the operating system color-scheme preference
9
+ - **WHEN** the user clicks the theme toggle in the UI
10
+ - **THEN** the interface switches to the selected theme immediately
13
11
 
14
- #### Scenario: User manually switches theme
12
+ #### Scenario: System preference on first load
15
13
 
16
- - **WHEN** the user activates the theme toggle
17
- - **THEN** the interface switches between light and dark mode immediately
14
+ - **WHEN** the user opens the application for the first time
15
+ - **THEN** the interface theme matches the system preference by default
18
16
 
19
17
  ### Requirement: User preference persists
20
18
 
21
- The system SHALL persist an explicit user theme choice across reloads.
19
+ The system SHALL persist the user's explicit theme choice across browser sessions using localStorage or an equivalent mechanism.
22
20
 
23
- #### Scenario: Saved choice overrides system preference
21
+ #### Scenario: Return visit
24
22
 
25
- - **WHEN** a returning user has a saved theme choice
26
- - **THEN** the application loads using the saved choice instead of the current system preference
23
+ - **WHEN** the user revisits the application after explicitly choosing dark mode
24
+ - **THEN** the interface renders in dark mode without requiring another toggle
27
25
 
28
26
  ### Requirement: Theme maintains readable contrast
29
27
 
30
- The system SHALL preserve readable text and UI contrast in both light and dark mode.
28
+ The system SHALL ensure that all core page colors and text combinations remain readable in both light and dark themes.
31
29
 
32
- #### Scenario: Primary content remains readable
30
+ #### Scenario: Dark mode readability
33
31
 
34
- - **WHEN** the user views text, surfaces, and interactive controls in dark mode
35
- - **THEN** foreground and background combinations remain readable and distinguishable
32
+ - **WHEN** the interface is in dark mode
33
+ - **THEN** text and interactive elements meet WCAG contrast requirements against dark backgrounds
package/docs/examples/refactor-auth-boundary/specs/auth-boundary/spec.md CHANGED
@@ -1,45 +1,33 @@
1
- # auth-request-gating Specification
2
-
3
1
  ## MODIFIED Requirements
4
2
 
5
3
  ### Requirement: Protected requests use one authentication boundary
6
4
 
7
- The system SHALL evaluate protected requests through one shared authentication boundary instead of scattered controller-level auth logic.
8
-
9
- #### Scenario: Valid protected request
5
+ The system SHALL route all protected requests through a single authentication boundary instead of scattering checks across route handlers and service helpers.
10
6
 
11
- - **WHEN** a protected request includes valid authentication credentials
12
- - **THEN** the shared authentication boundary produces an authenticated request context
13
- - **AND** downstream handlers use that context instead of re-parsing credentials independently
7
+ #### Scenario: Protected endpoint request
14
8
 
15
- #### Scenario: Missing credentials
16
-
17
- - **WHEN** a protected request arrives without required credentials
18
- - **THEN** the shared authentication boundary rejects the request consistently
19
- - **AND** the request does not continue into protected business logic
9
+ - **WHEN** a protected endpoint receives a request
10
+ - **THEN** the authentication boundary evaluates credentials and produces a stable auth decision before the route handler executes
20
11
 
21
12
  ### Requirement: Auth failures map consistently
22
13
 
23
- The system SHALL map authentication and authorization failures through standardized request-level outcomes.
14
+ The system SHALL map unauthorized and forbidden outcomes from the authentication boundary to consistent response formats across all protected routes.
24
15
 
25
- #### Scenario: Invalid token
16
+ #### Scenario: Missing credentials
26
17
 
27
- - **WHEN** token validation fails
28
- - **THEN** the request receives the standardized unauthorized outcome
29
- - **AND** downstream handlers are not invoked
18
+ - **WHEN** a protected request lacks valid credentials
19
+ - **THEN** the boundary returns an unauthorized decision and the route responds with the standard unauthorized format
30
20
 
31
- #### Scenario: Authenticated but forbidden
21
+ #### Scenario: Insufficient permissions
32
22
 
33
- - **WHEN** the requester is authenticated but lacks required access
34
- - **THEN** the request receives the standardized forbidden outcome
35
- - **AND** the outcome is produced without ad hoc controller-specific branching
23
+ - **WHEN** a protected request has valid credentials but insufficient permissions
24
+ - **THEN** the boundary returns a forbidden decision and the route responds with the standard forbidden format
36
25
 
37
26
  ### Requirement: Existing approved login behavior remains unchanged
38
27
 
39
- The refactor SHALL preserve already approved login and session semantics while changing the internal auth boundary shape.
28
+ The system SHALL preserve existing externally approved login and session behavior while moving request-level checks behind the new boundary.
40
29
 
41
- #### Scenario: Existing login flow
30
+ #### Scenario: Successful login
42
31
 
43
- - **WHEN** a user signs in through the existing approved login path
44
- - **THEN** the resulting session or token behavior remains externally unchanged
45
- - **AND** the new boundary consumes the established auth artifacts without requiring a new client contract
32
+ - **WHEN** a user completes the existing login flow
33
+ - **THEN** session creation and token issuance behavior remains identical to the pre-refactor implementation
package/docs/solutions/INDEX.md CHANGED
@@ -2,6 +2,7 @@
2
2
  <!-- 每条一行，按 severity 降序，≤150 行硬上限 -->
3
3
  | date | phase | domain | type | severity | summary | file |
4
4
  |------|-------|--------|------|----------|---------|------|
5
+ | 2026-08-17 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-17-no-summary.md |
5
6
  | 2026-08-07 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-07-no-summary.md |
6
7
  | 2026-08-06 | cross-phase | general | insight | medium | (no summary) | cross-phase/2026-08-06-no-summary.md |
7
8
  | 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 ADDED
@@ -0,0 +1,17 @@
1
+ ---
2
+ phase: cross-phase
3
+ domain: general
4
+ type: insight
5
+ severity: medium
6
+ date: 2026-08-17
7
+ source:
8
+ ---
9
+
10
+ ## 问题描述
11
+ (no summary)
12
+
13
+ ## 根因/模式
14
+ （待补充）
15
+
16
+ ## 预防措施/应用方式
17
+ （待补充）