@xulthekl/team-flow 0.70.0 → 0.71.0

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

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

package/.claude-plugin/marketplace.json

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

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.70.0",
+  "version": "0.71.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) + design-system (design tokens + component contract + AI primer + showcase) + test-strategy (test strategy design) + project-initialize (new service onboarding) + jarvis (team-flow decision agent, opt-in). 28 skills + 17 agents, one install.",
   "source": "./",
   "author": {

package/.codex-plugin/plugin.json

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

package/.cursor-plugin/marketplace.json

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

package/.cursor-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "team-flow",
   "displayName": "team-flow",
   "description": "Unified workflow plugin: team-flow (spec-driven dev: TDD/SDD/code-review/debugging) + compound-engineering core subset (brainstorm/plan/compound/strategy/ideate/proof, global compounding) + architecture-design (4A+DDD incremental design & global compounding) + prototype (local HTML prototype, zero external deps) + e2e (Playwright E2E, AC-driven) + workflow-orchestrator (product-level workflow orchestration) + workflow-bootstrap (existing project onboarding) + session-handoff (context transfer) + workflow-feedback (issue tracking) + business-analysis (independent requirement/scenario artifact) + jarvis (team-flow decision agent, opt-in). 28 skills + 17 agents, one install.",
-  "version": "0.70.0",
+  "version": "0.71.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.70.0"
+    "version": "0.71.0"
   },
   "plugins": [
     {
       "name": "team-flow",
       "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.70.0",
+      "version": "0.71.0",
       "source": ".",
       "author": {
         "name": "LT",

package/CHANGELOG.md

@@ -4,6 +4,20 @@ All notable changes to `team-flow` will be documented in this file.
 
 The format loosely follows Keep a Changelog.
 
+## [0.71.0] - 2026-09-30
+
+### Changed（prototype 组件复用范式固化——来源 = LT 提出「原型都塞进一个大 index.html，后期会膨胀」+ 实测确认 skill 仅目录级组件化、运行时零复用）
+
+**组件复用范式（四条准则，写入 SKILL.md「组件复用范式」小节 + builder-methodology Step 2「组件抽取准则」）**
+- 每模块独立 html：每个页面/功能模块一个文件落 `pages/`，不把所有内容塞进单一大 `index.html`。
+- 仅共用业务组件才抽：只有跨页面复用的组件才建 `components/<name>.js`；页面专属结构留在本页 `<style>`，不为组件化而组件化。
+- 最轻量零依赖落地：共用组件用 classic `<script src>`（非 module）+ 原生 `customElements` + 内联模板字符串实现，file:// 双击即开，不引入构建工具 / ES module 本地服务器。
+- token 唯一真相源：`assets/design-tokens.css` 经 `<link>` 外置，所有页面/组件经 `var(--token)` 引用；CSS 变量穿透 Shadow DOM。
+
+**Scaffold 改造**
+- 删除旧复制片段 `components/button.html`（运行时零复用，N 页复制 N 份）；新增 `components/my-button.js`（classic script + customElements 运行时组件，用 scaffold 自带 token）作最小示例。
+- `index.html` 与 `pages/index.html` 改为 `<link>` 外置 token + `<script src="components/my-button.js">` 引用 `<my-button>`，示范跨页复用。
+
 ## [0.70.0] - 2026-09-30
 
 ### Added（glaf4 规范直读通道：非委托路径实施/审查规范注入——来源 = LT 提出「不使用 glaf4-dev 时 glaf4 体系项目无法识别规范指导实施」+ glaf4-spec-direct-read-design v1.2 P1.5 两轮收敛）

package/GEMINI.md

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

package/INSTALL.md

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

package/README.md

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

package/docs/README_en.md

@@ -126,7 +126,7 @@ npm install -g team-flow
 
 ### Version
 
-- Current: `v0.70.0`
+- Current: `v0.71.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/team-flow /344/275/277/347/224/250/350/257/264/346/230/216/357/274/210/347/240/224/345/217/221/345/233/242/351/230/237/347/211/210/357/274/211.md"

@@ -1,6 +1,6 @@
 # team-flow 使用说明（研发团队版）
 
-> 版本锚点：v0.70.0（28 skills + 17 agents）· 更新日期：2026-09-21
+> 版本锚点：v0.71.0（28 skills + 17 agents）· 更新日期：2026-09-21
 > 读者：使用 team-flow 做日常研发的工程师。不需要你懂插件内部实现，只需要照着路径走。
 > 配套文档：安装细节见 [INSTALL.md](../INSTALL.md)；状态机细节见 [state-machine.md](state-machine.md)；决策点细节见 [decision-points.md](decision-points.md)；平台差异见 [platform-matrix.md](platform-matrix.md)。
 

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
   "description": "Unified workflow plugin: team-flow (spec-driven dev) + compound-engineering core subset + architecture-design (4A/DDD) + prototype (local HTML) + business-analysis (independent requirement/scenario artifact) + jarvis (team-flow decision agent, opt-in). 28 skills, one install.",
-  "version": "0.70.0",
+  "version": "0.71.0",
   "contextFileName": "GEMINI.md"
 }

package/hooks/session-start

@@ -1,11 +1,11 @@
 #!/usr/bin/env bash
-# v0.70.0: auto-sync CLI version with plugin version
+# v0.71.0: auto-sync CLI version with plugin version
 set -e
 
 # ═══════════════════════════════════════════════════════════════
 # Plugin version (update this when releasing new versions)
 # ═══════════════════════════════════════════════════════════════
-PLUGIN_VERSION="0.70.0"
+PLUGIN_VERSION="0.71.0"
 
 # ═══════════════════════════════════════════════════════════════
 # Step 1: Auto-sync CLI version with plugin version

package/llms.txt

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

package/package.json

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

package/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "team-flow",
-  "version": "0.70.0",
+  "version": "0.71.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) + design-system (design tokens + component contract + AI primer + showcase) + test-strategy (test strategy design) + project-initialize (new service onboarding) + jarvis (team-flow decision agent, opt-in). 28 skills + 17 agents, one install.",
   "author": {
     "name": "LT"

package/skills/prototype/SKILL.md

@@ -94,6 +94,17 @@ prototype/
 - `components/` 必须复用 `.team-flow/design-system/` 契约表组件，**禁止页面内联样式漂移**。
 - 新增组件先沉淀进 `design-system` 再引用。
 
+## 组件复用范式（2026-09-30 大哥拍板）
+
+原型是评审契约、非生产代码，**不追求生产级工程化**。组件化遵循四条准则：
+
+1. **每模块独立 html**：每个页面/功能模块一个独立文件，落在 `pages/`（如 `pages/list.html` / `pages/detail.html`），不把所有内容塞进单一大 `index.html`。
+2. **仅共用业务组件才抽取**：只有**跨页面复用**的组件才建 `components/<name>.js`；页面专属结构留在本页 `<style>`，**不为组件化而组件化**。
+3. **最轻量零依赖落地**：共用组件用 **classic `<script src>`（非 module）+ 原生 `customElements` + 内联模板字符串** 实现，模板不 `fetch` 外部文件；`file://` 双击即开，**不引入构建工具、不起 ES module 本地服务器**。
+4. **token 唯一真相源**：`assets/design-tokens.css` 经 `<link>` 外置（scaffold 已落地），所有页面/组件经 `var(--token)` 引用；CSS 自定义属性穿透 Shadow DOM，自定义元素隔离样式仍能读外置 token。
+
+> 与旧式"复制片段"的区别：旧 `components/*.html` 是 builder 复制进页面的静态片段（运行时零复用，N 页复制 N 份）；本范式组件在运行时注册一次、全站 `<my-x>` 复用，扩容只增页面内容、组件/token 零增长。scaffold 的 `components/my-button.js` 即该范式最小示例。
+
 ## 分支约定
 - 原型随 **PRD 当前版本分支**维护（如 `prd-v2` 分支的 `prototype/` = v2 产品原型）。
 - change 引用其所在 PRD 版本分支的 `prototype/`。

package/skills/prototype/references/builder-methodology.md

@@ -82,6 +82,13 @@ For each page in `confirmed_plan`:
 - Wire navigation links so every page is reachable from `index.html`.
 - Reflect PRD §4 画面 / §7 功能清单 / §8.4 字段 / §8.2 交互 in the page content.
 
+**组件抽取准则（2026-09-30 大哥拍板）**——原型是评审契约、非生产代码，**不追求生产级工程化**：
+- **每模块独立 html**：每个页面/功能模块一个文件落 `pages/`（如 `pages/list.html` / `pages/detail.html`），不把所有内容塞进单一大 `index.html`。
+- **仅共用业务组件才抽**：只有**跨页面复用**的组件才建 `components/<name>.js`；页面专属结构留在本页 `<style>`，**不为组件化而组件化**。
+- **最轻量零依赖落地**：共用组件用 **classic `<script src>`（非 module）+ 原生 `customElements` + 内联模板字符串** 实现（模板不 `fetch` 外部文件）；`file://` 双击即开，**不引入构建工具、不起 ES module 本地服务器**。scaffold 的 `components/my-button.js` 即该范式最小示例。
+- **token 唯一真相源**：`assets/design-tokens.css` 经 `<link>` 外置（scaffold 已落地），页面/组件经 `var(--token)` 引用；CSS 自定义属性穿透 Shadow DOM，组件隔离样式仍能读外置 token。
+- 旧式 `components/*.html` 复制片段**不再使用**（运行时零复用，N 页复制 N 份）；新组件一律 `<name>.js` 自定义元素。
+
 **大产出分片纪律（v0.20.0，防输出预算耗尽/单次 Write 截断）**：规划要**克制**——数据模型/改善方向等推演够用即可，不要把大量输出预算耗在 thinking 阶段的详尽规划上，留足预算给真正 Write 产物。对超大文件（经验阈值 ~800 行，如带完整数据层的 `index.html`）**默认分片写**：
 
 1. 先 `Write` 主体骨架（HTML 结构 + `<style>` token 引用 + 导航 + 空的 `<script>` 数据/渲染占位），落盘一个**可运行的最小入口**；

package/skills/prototype/references/prototype-scaffold/components/my-button.js

@@ -0,0 +1,28 @@
+// 共用业务组件示例：<my-button label="文本" variant="primary|ghost" disabled>
+// 轻量零依赖：classic <script src>（非 module）+ 原生 customElements，
+// file:// 双击即开，无需构建工具或本地服务器。
+// 模板内联为字符串（不 fetch 外部文件，规避 file:// CORS）；
+// 样式用 var(--token) 读 assets/design-tokens.css（CSS 变量穿透 Shadow DOM）。
+class MyButton extends HTMLElement {
+  connectedCallback() {
+    const label = this.getAttribute('label') || '按钮';
+    const variant = this.getAttribute('variant') || 'primary';
+    const disabled = this.hasAttribute('disabled');
+    this.attachShadow({ mode: 'open' }).innerHTML = `
+      <style>
+        :host { display: inline-block; font-family: var(--font-body); }
+        button {
+          font: 600 15px/1 var(--font-body);
+          padding: var(--space-2) var(--space-4);
+          border: 0; border-radius: var(--radius-2);
+          cursor: pointer; transition: background .15s;
+        }
+        :host([variant="primary"]) button { background: var(--accent); color: #fff; }
+        :host([variant="primary"]) button:hover { background: var(--accent-hover); }
+        :host([variant="ghost"]) button { background: var(--surface); color: var(--accent); box-shadow: inset 0 0 0 1px var(--accent); }
+        button:disabled { opacity: .5; cursor: not-allowed; }
+      </style>
+      <button ${disabled ? 'disabled' : ''}>${label}</button>`;
+  }
+}
+customElements.define('my-button', MyButton);

package/skills/prototype/references/prototype-scaffold/index.html

@@ -9,12 +9,17 @@
 </head>
 <body>
   <nav id="nav"><!-- 全局导航：链接各页面 --></nav>
-  <main id="app"><!-- 页面内容容器 --></main>
+  <main id="app">
+    <!-- 共用业务组件示例：<my-button> 由 components/my-button.js 在运行时注册 -->
+    <my-button label="示例按钮" variant="primary"></my-button>
+  </main>
   <!-- Tweaks 控件：替代云端工具栏，纯本地 -->
   <div id="tweaks">
     <label>主题 <select id="theme"><option>light</option><option>dark</option></select></label>
     <label>密度 <input type="range" id="density" min="0" max="2" value="1"></label>
   </div>
   <script>/* 页面内交互，无远程依赖。tweaks 控件用原生 JS + localStorage */</script>
+  <!-- 共用组件：classic script + 原生 customElements，file:// 双击即开（非 module，无需服务器） -->
+  <script src="components/my-button.js"></script>
 </body>
 </html>

package/skills/prototype/references/prototype-scaffold/pages/index.html

@@ -7,5 +7,8 @@
 <body>
   <h1>首页</h1>
   <!-- 示例页面；多页面时在 pages/ 增加 list.html / detail.html 等 -->
+  <!-- 跨页面复用同一组件：引用 ../components/my-button.js -->
+  <my-button label="页面内按钮" variant="ghost"></my-button>
+  <script src="../components/my-button.js"></script>
 </body>
 </html>

package/skills/prototype/references/prototype-scaffold/components/button.html

@@ -1,3 +0,0 @@
-<button class="btn btn--primary">Primary</button>
-<button class="btn btn--ghost">Ghost</button>
-<!-- 样式来自 assets/design-tokens.css + design-system components 规范 -->