@givolt/i3-composer-agent 3.1.0 → 3.2.1

package/.agents/plugins/marketplace.json

@@ -6,7 +6,7 @@
   "plugins": [
     {
       "name": "i3-composer-agent",
-      "version": "3.1.0",
+      "version": "3.2.1",
       "description": "覆盖需求、计划、开发、测试、审查与发布的软件工程技能，默认使用简体中文。",
       "source": {
         "source": "local",

package/.claude/commands/i3-sop.md

@@ -1,6 +1,6 @@
 ---
-description: "显式使用企业 SOP，复用原规格方法完成单阶段文档与交接"
-# i3-description-source: "description: 显式使用企业 SOP，复用原规格方法完成单阶段文档与交接"
+description: "显式使用企业 SOP，生成或修订企业文档、工程 SPEC 和项目计划"
+# i3-description-source: "description: 显式使用企业 SOP，生成或修订企业文档、工程 SPEC 和项目计划"
 ---
 
 <!-- i3:zh-CN:start -->
@@ -11,7 +11,7 @@ description: "显式使用企业 SOP，复用原规格方法完成单阶段文
 Skill/Command/Agent 标识、文件路径、命令参数、代码/API 名称、工具调用参数、JSON 键/类型/枚举、机器状态、测试期望字面量及引用原文保持原样。生成文档正文用中文，SPEC.md、tasks/plan.md、tasks/todo.md、CONSTRAINTS.md 等约定路径不改名。
 严重程度按原规则判断，面向用户可写“严重（Critical）”“必须修复（Required）”“小问题（Nit）”“可选（Optional）”“建议考虑（Consider）”“仅供参考（FYI）”；High/Medium/Low、APPROVE/REQUEST CHANGES 和 GO/NO-GO 保留其原始语义与机器值。不得因翻译降低门槛，角色不能互相委派。
 
-适用说明：显式使用企业 SOP，复用原规格方法完成单阶段文档与交接
+适用说明：显式使用企业 SOP，生成或修订企业文档、工程 SPEC 和项目计划
 <!-- i3:zh-CN:end -->
 
 Invoke the i3-enterprise-sop skill and pass the complete arguments unchanged. The skill owns operation handling, resource selection, original-method invocation, handoff and stopping rules.

package/.claude-plugin/marketplace.json

@@ -8,7 +8,7 @@
   "plugins": [
     {
       "name": "i3-composer-agent",
-      "version": "3.1.0",
+      "version": "3.2.1",
       "source": "./",
       "description": "覆盖需求、计划、开发、测试、审查与发布的软件工程技能，默认使用简体中文。",
       "homepage": "https://github.com/49780522/i3-composer-agent",

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "i3-composer-agent",
-  "version": "3.1.0",
+  "version": "3.2.1",
   "description": "覆盖需求、计划、开发、测试、审查与发布的软件工程技能，默认使用简体中文。",
   "author": {
     "name": "Givolt"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "i3-composer-agent",
-  "version": "3.1.0",
+  "version": "3.2.1",
   "description": "覆盖需求、计划、开发、测试、审查与发布的软件工程技能，默认使用简体中文。",
   "author": {
     "name": "Givolt"

package/.gemini/commands/i3-sop.toml

@@ -1,5 +1,5 @@
-description = "显式使用企业 SOP，复用原规格方法完成单阶段文档与交接"
-# i3-description-source: "description = \"显式使用企业 SOP，复用原规格方法完成单阶段文档与交接\""
+description = "显式使用企业 SOP，生成或修订企业文档、工程 SPEC 和项目计划"
+# i3-description-source: "description = \"显式使用企业 SOP，生成或修订企业文档、工程 SPEC 和项目计划\""
 
 prompt = """
 <!-- i3:zh-CN:start -->
@@ -10,7 +10,7 @@ prompt = """
 Skill/Command/Agent 标识、文件路径、命令参数、代码/API 名称、工具调用参数、JSON 键/类型/枚举、机器状态、测试期望字面量及引用原文保持原样。生成文档正文用中文，SPEC.md、tasks/plan.md、tasks/todo.md、CONSTRAINTS.md 等约定路径不改名。
 严重程度按原规则判断，面向用户可写“严重（Critical）”“必须修复（Required）”“小问题（Nit）”“可选（Optional）”“建议考虑（Consider）”“仅供参考（FYI）”；High/Medium/Low、APPROVE/REQUEST CHANGES 和 GO/NO-GO 保留其原始语义与机器值。不得因翻译降低门槛，角色不能互相委派。
 
-适用说明：显式使用企业 SOP，复用原规格方法完成单阶段文档与交接
+适用说明：显式使用企业 SOP，生成或修订企业文档、工程 SPEC 和项目计划
 <!-- i3:zh-CN:end -->
 
 Invoke the i3-enterprise-sop skill and pass the complete arguments unchanged. The skill owns operation handling, resource selection, original-method invocation, handoff and stopping rules.

package/README.md

@@ -1,4 +1,4 @@
-# i3 Composer Agent v3.1.0
+# i3 Composer Agent v3.2.1
 
 **Intelligence. Integration. Innovation.**
 
@@ -7,37 +7,32 @@
 Skill 和命令使用 `i3-` 前缀。默认简体中文交互；用户明确要求时可切换语言。
 代码标识、路径、参数、工具协议和机器状态保持原样。
 
-## 企业 SOP 文档与规划
+## 企业开发 SOP
 
-新增 `/i3-sop` 命令和 `i3-enterprise-sop` Skill，共 27 个技能、11 个命令。
-标准流程继续使用原 `/i3-spec`、`/i3-plan`、`/i3-build` 等入口；企业 SOP 需要明确选择，
-普通安装或原 using 不会自动切换为企业流程。
-
-在项目中使用短命令加一句任务，缺少范围、主题或来源时由模型先澄清：
+通过 `/i3-sop` 命令或显式选择 `i3-enterprise-sop` Skill，使用同一套四阶段模板、工程 SPEC 和项目规划规则。本版统一为28个技能、12个命令，企业流程由用户逐阶段发起。
 
 ```text
-/i3-sop brd 梳理设备运营的业务能力，先确认业务边界。
-/i3-sop prd 根据已选 BRD，为巡检管理编写任务编排主题 PRD。
-/i3-sop ad 根据已选 PRD 制定详细设计，优先采用本项目现有技术规约。
-/i3-sop testcase 根据当前 AD 设计测试用例和测试报告要求。
-/i3-sop plan 为已选主题制定实施计划，读取完整的设计和必要工程依据。
+/i3-sop brd 根据这份业务诉求梳理业务能力并编写 BRD。
+/i3-sop prd 根据这份 BRD 编写当前主题 PRD，关键缺口先问我。
+/i3-sop ad 根据选定 PRD 编写 AD，优先采用本项目已有的技术规约。
+/i3-sop testcase 根据当前主题的 PRD、配套 AD 设计用例和测试报告要求。
+/i3-sop spec 为当前主题生成工程 SPEC。
+/i3-sop plan 根据我认可的工程 SPEC 制定计划和任务。
 ```
 
-显式 Skill 使用同一规则，例如“使用 i3-enterprise-sop，根据当前 PRD 编写 AD”。
-文档生成／修订复用原 Spec 方法，Plan 动作复用原规划方法，输出原 `tasks/plan.md` 和
-`tasks/todo.md`，交人审阅。计划获准后继续使用原 `/i3-build` 或 `/i3-build auto`；
-auto 仍遵守原规格、Git 基线、明确认可、测试与逐任务提交要求。
+显式 Skill 使用同一规则，例如“使用 i3-enterprise-sop prd，根据这份 BRD 编写当前主题 PRD”。没有给出动作或范围不清楚时，由主会话引导选择。
+
+- T1：`brd`、`prd`、`ad`、`testcase` 分别编写、整理或修订企业文档，真实显式调用原 Spec Skill；采用完整模板和必要来源，保存并核对完整性后自动登记交接清单，交人审阅并停止。
+- T2：用户主动选择 `spec`，读取本 EBC 的交接清单，检查当前主题的 BRD、PRD、AD 及必要依据，真实显式调用原 Spec Skill，形成包含六项内容的工程 SPEC。缺项或冲突先说明，生成后交人审阅并停止。TestCase可选。
+- T3：用户主动选择 `plan`，读取已认可的工程 SPEC，真实显式调用原规划 Skill，输出原 `tasks/plan.md` 与唯一任务清单，交人审阅并停止。计划获准后，由用户启动原 `/i3-build`、`/i3-build auto` 及后续流程。
+
+一个业务项目对应一个EBC。BRD默认直接存于`spec/`根目录，路径为`spec/{EBC名称}-BRD_v{业务版本}.md`；PRD、AD、TestCase默认存于各自PBC目录，路径为`spec/{PBC名称}/{PBC名称}-{主题名称}-{PRD|AD|TestCase}_v{各自版本}.md`。交接清单保存在`spec/handoff.json`，工程规格保存在`spec/SPEC-{PBC名称}-{主题名称}.md`，规划时默认从`spec/`根目录定位当前主题的`SPEC*.md`。同一EBC可包含多个PBC及各自独立主题的PRD，文档版本分别维护。清单只保留`schemaVersion`、`scope`、`selected`，相对路径基于业务项目根，也支持手动传递准确路径；既有明确采用位置或外部原件保留实际路径，不自动迁移。
+
+输入可以是自然语言或外部文档，用户明确选用的自改模板和项目规范优先。Skill自带四份模板、[企业应用具体技术规约](skills/i3-enterprise-sop/references/technical-baseline/baselines/enterprise-application-technical-baseline-v0-0-4.md)、[通用技术规约模板](skills/i3-enterprise-sop/references/technical-baseline/templates/technical-baseline.md)和[目录规范1.0.0](skills/i3-enterprise-sop/references/engineering-skeleton/directory-standard.md)。没有项目替代规范时，AD默认带入具体规约与目录规范；目录规范不等于已生成代码。
 
-支持同一 PBC 的多份独立主题 PRD，各自独立版本并关联对应 AD／TestCase；
-原型按需，可与 AD 并行；独立 TestCase 不作为 Plan 的统一必填前置。
-JSON 交接只保留 `schemaVersion`、`scope`、`selected`，也保留手动传递路径的方式。
-项目自改模板与已有工程规范优先采用，审查只报告问题，不自动修改业务稿。
+正常保存不强制再次全文加载新稿，保留落盘完整性检查、内容自查、人工修改及每阶段审阅停点。原型按需，可与AD并行。完整规则见 [i3-enterprise-sop](skills/i3-enterprise-sop/SKILL.md)。
 
-包内提供四阶段模板／提示词、公共技术规约模板及采用示例，以及工程目录与采用资源 **1.0.0**。
-技术规约示例需按实际项目确认采用，工程目录资源不等于已生成整套业务代码。
-安装后的配套根中可读 [SOP 采用说明](skills/i3-enterprise-sop/references/readme.md) 和
-[工程骨架资源](skills/i3-enterprise-sop/references/engineering-skeleton/readme.md)。
-3.0.0 由人逐阶段发起与审阅；SOP 全流程自动调度和 i3-config 不包含在本次发行。
+标准流程继续使用原 `/i3-spec`、`/i3-plan`、`/i3-build` 等入口。普通安装或原 using 不会自动切换企业流程；原版方法和命令保持。
 
 ## 通过向导安装
 
@@ -198,7 +193,7 @@ CodeBuddy、WorkBuddy、Claude Code 原生安装使用 `/i3-spec`、`/i3-plan`
 | /i3-composer-agent:i3-prototype | 在主会话中分析、创建、检查与迭代 UI 交互原型。 |
 | /i3-composer-agent:i3-review | 从正确性、可读性、架构、安全和性能五个维度审查代码。 |
 | /i3-composer-agent:i3-ship | 并行调用三个专业角色执行发布前检查，主会话汇总 GO/NO-GO 决策与回滚计划。 |
-| /i3-composer-agent:i3-sop | 显式使用企业 SOP，复用原规格方法完成单阶段文档与交接 |
+| /i3-composer-agent:i3-sop | 显式使用企业 SOP，生成或修订企业文档、工程 SPEC 和项目计划 |
 | /i3-composer-agent:i3-spec | 先编写结构化规格、目标、范围与验收标准，再进入实现。 |
 | /i3-composer-agent:i3-test | 执行 TDD：先编写失败测试，再实现和验证；缺陷使用 Prove-It 模式复现。 |
 | /i3-composer-agent:i3-ui-demo | 使用内置模板和固定设计、组件能力创建及增量修改 UI 原型。 |
@@ -237,7 +232,7 @@ ui-ux-pro-max 2.15.0 与 antDv 官方 Skill／CLI（默认 0.0.0-beta.6 固定
 | [i3-deprecation-and-migration](skills/i3-deprecation-and-migration/SKILL.md) | 管理废弃与迁移。适用于替换旧系统、API 或功能、迁移用户、生产数据库无停机扩展/收缩，以及决定维护或退役现有代码。 |
 | [i3-documentation-and-adrs](skills/i3-documentation-and-adrs/SKILL.md) | 记录文档、架构决策与设计理由。适用于编写 ADR、公共 API 发生变化时补充文档、交付功能，以及保存后续工程师和代理理解设计取舍所需的背景。 |
 | [i3-doubt-driven-development](skills/i3-doubt-driven-development/SKILL.md) | 对非平凡决策进行独立的对抗式审查。适用于核查假设、压力测试计划、寻找隐藏失败模式、陌生代码、安全敏感功能、生产认证或高风险不可逆迁移。 |
-| [i3-enterprise-sop](skills/i3-enterprise-sop/SKILL.md) | 组织显式选择的企业 SOP 文档与规划交接。适用于明确调用 i3-enterprise-sop 起草 BRD、PRD、AD、TestCase、制定 Plan 或传递选定资料；短命令先澄清缺口，再复用原版方法。 |
+| [i3-enterprise-sop](skills/i3-enterprise-sop/SKILL.md) | 组织企业开发文档、工程规格和项目规划。适用于显式调用 i3-enterprise-sop 编写、整理或修订 BRD、PRD、AD、TestCase、生成工程 SPEC 或依据规格规划任务。 |
 | [i3-frontend-ui-engineering](skills/i3-frontend-ui-engineering/SKILL.md) | 实现可访问、响应式、具有生产质量的前端界面。适用于页面/组件开发、布局、状态管理、WCAG 无障碍、交互与视觉质量改进。 |
 | [i3-git-workflow-and-versioning](skills/i3-git-workflow-and-versioning/SKILL.md) | 组织 Git 分支、提交、冲突处理、PR 与版本发布。适用于任何代码改动、拆分工作区改动、并行开发、推送、合并、语义化版本、标签及变更日志。 |
 | [i3-idea-refine](skills/i3-idea-refine/SKILL.md) | 通过发散与收敛思考完善模糊想法。适用于创意探索、细化方案、验证假设、压力测试计划，以及确定方向前比较更多选项。 |

package/commands/i3-sop.toml

@@ -1,5 +1,5 @@
-description = "显式使用企业 SOP，复用原规格方法完成单阶段文档与交接"
-# i3-description-source: "description = \"显式使用企业 SOP，复用原规格方法完成单阶段文档与交接\""
+description = "显式使用企业 SOP，生成或修订企业文档、工程 SPEC 和项目计划"
+# i3-description-source: "description = \"显式使用企业 SOP，生成或修订企业文档、工程 SPEC 和项目计划\""
 
 prompt = """
 <!-- i3:zh-CN:start -->
@@ -10,7 +10,7 @@ prompt = """
 Skill/Command/Agent 标识、文件路径、命令参数、代码/API 名称、工具调用参数、JSON 键/类型/枚举、机器状态、测试期望字面量及引用原文保持原样。生成文档正文用中文，SPEC.md、tasks/plan.md、tasks/todo.md、CONSTRAINTS.md 等约定路径不改名。
 严重程度按原规则判断，面向用户可写“严重（Critical）”“必须修复（Required）”“小问题（Nit）”“可选（Optional）”“建议考虑（Consider）”“仅供参考（FYI）”；High/Medium/Low、APPROVE/REQUEST CHANGES 和 GO/NO-GO 保留其原始语义与机器值。不得因翻译降低门槛，角色不能互相委派。
 
-适用说明：显式使用企业 SOP，复用原规格方法完成单阶段文档与交接
+适用说明：显式使用企业 SOP，生成或修订企业文档、工程 SPEC 和项目计划
 <!-- i3:zh-CN:end -->
 
 Invoke the i3-enterprise-sop skill and pass the complete arguments unchanged. The skill owns operation handling, resource selection, original-method invocation, handoff and stopping rules.

package/docs/codex-setup.md

@@ -37,6 +37,6 @@ Codex 已有原生技能路由，勿把元技能全文预加载为常驻上下
 
 ## 可选原型工具
 
-原型辅助工具位于本宿主基址的 `tools/i3-prototype/`，支持项目和全局范围；旧项目 `.prototype-tools` 继续读取兼容。项目安装可使用 `npx @givolt/i3-composer-agent@3.1.0 --codex --scope project --yes --prototype-skills uiux,antdv`；全局安装将 scope 改为 global。可选依赖默认 none，后续也可使用已安装 Skill 的 prototype-dependencies.cjs 单独检测／补装。完整用法见原型 Skill 的 references/optional-skills.md。
+原型辅助工具位于本宿主基址的 `tools/i3-prototype/`，支持项目和全局范围；旧项目 `.prototype-tools` 继续读取兼容。项目安装可使用 `npx @givolt/i3-composer-agent@3.2.1 --codex --scope project --yes --prototype-skills uiux,antdv`；全局安装将 scope 改为 global。可选依赖默认 none，后续也可使用已安装 Skill 的 prototype-dependencies.cjs 单独检测／补装。完整用法见原型 Skill 的 references/optional-skills.md。
 
 原型共享资料统一在项目 prototypes/：新索引 prototypes/index.json，准备范围 prototypes/.preparation/<id>/scope.json。新原生 scope.moduleIds 自动生成 appliesTo；旧索引、输入和实例保持兼容，安装升级不自动迁移。工具及运行缓存使用所选宿主基址；全局浏览器缓存按业务项目身份隔离。详细规则和只读查询／显式迁移命令见 i3-ui-prototype/references/project-layout.md。

package/docs/other-hosts.md

@@ -6,7 +6,7 @@
 
 ## 使用本地分发目录
 
-以下命令使用完整分发包解压目录里的 CLI，适用于本地测试和离线接入。`/absolute/path/to/package` 均替换为实际解压目录；已发布版本也可使用 `npx @givolt/i3-composer-agent@3.1.0` 的对应入口。
+以下命令使用完整分发包解压目录里的 CLI，适用于本地测试和离线接入。`/absolute/path/to/package` 均替换为实际解压目录；已发布版本也可使用 `npx @givolt/i3-composer-agent@3.2.1` 的对应入口。
 
 ### fx
 

package/docs/workbuddy-setup.md

@@ -85,7 +85,7 @@ npx @givolt/i3-composer-agent --workbuddy --scope global --yes --force
 
 ## 可选原型工具
 
-原型辅助工具位于本宿主基址的 `tools/i3-prototype/`，支持项目和全局范围；旧项目 `.prototype-tools` 继续读取兼容。推荐使用 `npx @givolt/i3-composer-agent@3.1.0 --workbuddy --scope global --yes --prototype-skills uiux,antdv`；项目安装将 scope 改为 project。可选依赖默认 none，后续也可使用已安装 Skill 的 prototype-dependencies.cjs 单独检测／补装。完整用法见原型 Skill 的 references/optional-skills.md。
+原型辅助工具位于本宿主基址的 `tools/i3-prototype/`，支持项目和全局范围；旧项目 `.prototype-tools` 继续读取兼容。推荐使用 `npx @givolt/i3-composer-agent@3.2.1 --workbuddy --scope global --yes --prototype-skills uiux,antdv`；项目安装将 scope 改为 project。可选依赖默认 none，后续也可使用已安装 Skill 的 prototype-dependencies.cjs 单独检测／补装。完整用法见原型 Skill 的 references/optional-skills.md。
 
 原型共享资料统一在项目 prototypes/：新索引 prototypes/index.json，准备范围 prototypes/.preparation/<id>/scope.json。新原生 scope.moduleIds 自动生成 appliesTo；旧索引、输入和实例保持兼容，安装升级不自动迁移。工具及运行缓存使用所选宿主基址；全局浏览器缓存按业务项目身份隔离。详细规则和只读查询／显式迁移命令见 i3-ui-prototype/references/project-layout.md。
 

package/evals/cases/i3-enterprise-sop.json

@@ -3,61 +3,99 @@
   "trigger": {
     "positive": [
       {
-        "prompt": "Explicitly use i3-enterprise-sop to record this explicitly selected PRD path without editing business documents",
-        "top_k": 3
+        "prompt": "Explicitly use i3-enterprise-sop to prepare enterprise BRD, PRD, AD and TestCase documents using its bundled templates",
+        "top_k": 1
       },
       {
-        "prompt": "Use i3-enterprise-sop for this named PBC PRD and AD reference handoff",
-        "top_k": 3
+        "prompt": "Use i3-enterprise-sop spec to build an engineering SPEC from the selected topic and registered BRD PRD AD sources",
+        "top_k": 1
       },
       {
-        "prompt": "Explicitly use i3-enterprise-sop in manual handoff mode without creating JSON",
-        "top_k": 3
+        "prompt": "Use i3-enterprise-sop plan for the approved engineering SPEC while reusing original planning and its human review stop",
+        "top_k": 1
       },
       {
-        "prompt": "Explicitly use i3-enterprise-sop to draft this named PBC AD through native Spec, then stop for review",
-        "top_k": 3
+        "prompt": "Use i3-enterprise-sop for read-only analysis of these document inputs; do not generate or register files",
+        "top_k": 1
       },
       {
-        "prompt": "Explicitly use i3-enterprise-sop plan for this selected topic, reuse native planning and stop for review",
-        "top_k": 3
+        "prompt": "Use i3-enterprise-sop to record an explicitly chosen AD path",
+        "top_k": 1
       }
     ],
     "negative": [
       {
-        "prompt": "Write the standard SPEC.md with objectives, behavior and explicit boundaries",
+        "prompt": "Write a standard SPEC.md with objectives and boundaries",
         "owner": "i3-spec-driven-development"
       },
       {
-        "prompt": "Break the approved spec into ordered implementation tasks",
+        "prompt": "Break an approved specification into ordered implementation tasks",
         "owner": "i3-planning-and-task-breakdown"
+      },
+      {
+        "prompt": "Create a i3-ui-demo using the enterprise admin template and antdv-next",
+        "owner": "i3-ui-demo"
       }
     ]
   },
   "evals": [
     {
       "id": 1,
-      "prompt": "Read brief.md. Explicitly use i3-enterprise-sop for the requested path handoff only.",
-      "files": [
-        "i3-enterprise-sop"
-      ],
-      "expected_output": "A handoff of explicitly selected document paths using schemaVersion, scope and selected only, or a read-only manual summary when requested",
+      "kind": "dialogue",
+      "prompt": "Explicitly use i3-enterprise-sop to prepare a PRD from my external BRD. The supplied BRD does not specify who can approve a request. Explain how you will obtain the bundled PRD template, invoke the original method and handle that critical gap before writing. Do not edit the supplied BRD.",
+      "expected_output": "A bounded T1 preparation and real clarification stop using the current template and original Spec method",
+      "expectations": [
+        "Uses the current project-selected template first, otherwise its own bundled PRD template; does not require user-supplied internal paths",
+        "Explicitly loads original Spec through the supported host mechanism and obtains its complete method body before substantive work; naming a method or reading a summary is insufficient",
+        "Checks the actual BRD and prior real answers before asking; does not invent approver permissions or treat a default recommendation as a human decision",
+        "Preserves supplied business files and waits for a genuine answer to a critical unresolved choice"
+      ]
+    },
+    {
+      "id": 2,
+      "kind": "dialogue",
+      "prompt": "Explicitly use i3-enterprise-sop spec. The selected handoff has readable BRD and PRD paths but no matching AD. Tell me the next step without creating an engineering SPEC.",
+      "expected_output": "T2 identifies the missing matching AD and stops for the user to generate or provide it",
+      "expectations": [
+        "Reads the selected work and topic rather than choosing the largest version in the directory",
+        "Requires readable and consistently paired BRD PRD AD for T2; optional TestCase and prototype do not become universal prerequisites",
+        "Names the missing AD and corresponding T1 ad operation, then stops without an engineering SPEC or plan",
+        "Does not mutate handoff during this T2 check or silently substitute a different topic"
+      ]
+    },
+    {
+      "id": 3,
+      "kind": "dialogue",
+      "prompt": "Explicitly use i3-enterprise-sop plan for this approved engineering SPEC. My existing tasks/todo.md contains unfinished work from another effort. Explain how you will reuse the original planning method without overwriting it or starting Build.",
+      "expected_output": "T3 explicitly uses original planning, protects the unfinished plan and retains its review gate",
+      "expectations": [
+        "Actually invokes the original planning Skill through the host's supported mechanism and obtains its full method rather than imitating a planner",
+        "Reads the selected engineering SPEC and necessary referenced evidence, not every topic in the project",
+        "Keeps original unfinished-plan protection, tasks/plan.md and a single task target; asks before replacing conflicting unfinished work",
+        "Maps requirements and design constraints into tasks and verification, then stops for human review without Build"
+      ]
+    },
+    {
+      "id": 4,
+      "kind": "dialogue",
+      "prompt": "Explicitly use i3-enterprise-sop for a saved document self-check. A tool failed while writing a long section, and no complete file result is yet proven. I have authorized only the target document and its handoff entry, not temporary scripts. Explain recovery and reporting; do not claim the document passed.",
+      "expected_output": "Evidence-based recovery at the actual persisted boundary, no extra self-check script files or false approval",
+      "expectations": [
+        "Inspects actual file state and distinguishes no write, partial write and failed receipt after write; resumes only missing or affected parts",
+        "Uses existing read-only tools or in-memory commands for routine self-checks, without writing temporary scripts or enlarging the authorized scope",
+        "Verifies persisted completeness and segment seams without making a full output reread universally mandatory",
+        "Separates structural checks, content self-check, real tool evidence, registration and human approval; retains original failure and stops when the safe boundary cannot be determined"
+      ]
+    },
+    {
+      "id": 5,
+      "kind": "dialogue",
+      "prompt": "Use i3-enterprise-sop only to analyze a request. I have not authorized drafting, directory creation, installation or handoff registration. Give a read-only explanation of T1, T2 and T3.",
+      "expected_output": "Read-only explanation without state changes or autonomous next-stage execution",
       "expectations": [
-        "Paths resolve against the confirmed project root and actual documents are read",
-        "A newly generated draft is only reported by path; selected changes only for an explicit user choice and business text is unchanged",
-        "Manual handoff does not create a JSON file or project directories",
-        "Original skills, commands, plans and task state are unchanged",
-        "No business approval, next-stage execution or publication is inferred",
-        "Drafting BRD, PRD, AD or TestCase loads original Spec successfully and preserves its save-and-stop gate",
-        "New business documents default to spec/ per capability; existing adopted paths are retained",
-        "Only the selected topic and necessary shared dependencies become original Plan inputs; original Build auto gates are retained",
-        "Short brd, prd, ad, testcase and plan actions ask only missing facts and do not write while awaiting an answer",
-        "Explicit plan successfully loads original planning Skill and preserves original command obligations and outputs, without JSON writes or Build",
-        "Manual and JSON Plan complete the same indexed shared reads and original command before native planning; scripts do not count as model reads; actual relevant dependency/build configuration is read rather than inferred from AD commands",
-        "AD capability/topic identity or direct-upstream path/PRD-version conflicts stop before native planning and any plan/todo or candidate-plan writes; suspected header typos are not self-resolved",
-        "PRD and AD independent version numbers may differ when the AD references the exact selected PRD version; optional TestCase/prototype do not become universal blockers",
-        "SOP preparation uses Read/Glob/Grep for file discovery instead of probing shell permission with ls/find/mkdir",
-        "The native plan retains full actual source paths and document versions for PRD, AD, adopted norms, contracts and engineering adoption; aliases in the plan or paths only in the conversation report are insufficient"
+        "Keeps T1 enterprise documents, T2 engineering SPEC and T3 original planning as distinct user-started stages",
+        "Does not create spec directories, handoff JSON, business drafts, plans or install tools during read-only analysis",
+        "Preserves human-review stops and does not call approval or a successful registration equivalent to permission for the next stage"
       ]
     }
   ]

package/evals/zh-CN/cases/i3-enterprise-sop.json

@@ -3,58 +3,104 @@
   "trigger": {
     "positive": [
       {
-        "prompt": "显式使用 i3-enterprise-sop，为本次 PBC 的 PRD 和 AD 做路径交接",
-        "top_k": 3
+        "prompt": "显式使用 i3-enterprise-sop，按企业模板准备BRD、PRD、AD和TestCase。",
+        "top_k": 1
       },
       {
-        "prompt": "显式使用 i3-enterprise-sop，以原 Spec 和企业模板起草本主题 AD 后停轮",
-        "top_k": 3
+        "prompt": "使用 i3-enterprise-sop spec，从登记的本主题BRD、PRD和AD形成工程SPEC。",
+        "top_k": 1
       },
       {
-        "prompt": "显式使用 i3-enterprise-sop，手动传递准确路径，不创建 JSON",
-        "top_k": 3
+        "prompt": "使用 i3-enterprise-sop plan，依据认可的工程SPEC复用原规划技能，交审后停止。",
+        "top_k": 1
       },
       {
-        "prompt": "显式使用i3-enterprise-sop执行plan，只规划本项目选定的任务编排主题，完成后交我审阅",
-        "top_k": 3
+        "prompt": "只读分析 i3-enterprise-sop 文档输入，不写稿或登记。",
+        "top_k": 1
+      },
+      {
+        "prompt": "使用 i3-enterprise-sop，只登记用户明确选定的AD路径，不修改业务稿。",
+        "top_k": 1
       }
     ],
     "negative": [
       {
-        "prompt": "标准流程：编写 SPEC.md，包含目标、命令、工程结构和边界",
+        "prompt": "编写标准SPEC.md，明确目标、命令、工程结构、代码风格、测试策略与边界。",
         "owner": "i3-spec-driven-development"
       },
       {
-        "prompt": "把已选规格拆成依赖有序、带验收和验证的实施任务",
+        "prompt": "把认可的规格拆解为有依赖关系的实施计划和任务。",
         "owner": "i3-planning-and-task-breakdown"
+      },
+      {
+        "prompt": "使用 i3-ui-demo，按企业后台模板和antdV-next制作交互原型。",
+        "owner": "i3-ui-demo"
       }
     ]
   },
   "evals": [
     {
       "id": 1001,
-      "prompt": "读取 brief.md，显式使用 i3-enterprise-sop，只做本次准确路径交接。",
-      "files": [
-        "i3-enterprise-sop"
-      ],
-      "expected_output": "仅登记明确选用路径的三字段清单，或零项目写入的手动输入摘要",
+      "kind": "dialogue",
+      "prompt": "显式使用 i3-enterprise-sop，根据外部BRD准备PRD。BRD没有规定谁能审批申请；请说明如何定位自带PRD模板、调用原方法并处理这个关键缺口，不修改外部BRD。",
+      "expected_output": "A bounded T1 preparation and real clarification stop using the current template and original Spec method",
+      "expectations": [
+        "Uses the current project-selected template first, otherwise its own bundled PRD template; does not require user-supplied internal paths",
+        "Explicitly loads original Spec through the supported host mechanism and obtains its complete method body before substantive work; naming a method or reading a summary is insufficient",
+        "Checks the actual BRD and prior real answers before asking; does not invent approver permissions or treat a default recommendation as a human decision",
+        "Preserves supplied business files and waits for a genuine answer to a critical unresolved choice",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留路径、工具参数、JSON协议及机器状态。"
+      ]
+    },
+    {
+      "id": 1002,
+      "kind": "dialogue",
+      "prompt": "显式使用 i3-enterprise-sop spec。清单中BRD和PRD可读但缺少配套AD，请说明下一步，不创建工程SPEC。",
+      "expected_output": "T2 identifies the missing matching AD and stops for the user to generate or provide it",
+      "expectations": [
+        "Reads the selected work and topic rather than choosing the largest version in the directory",
+        "Requires readable and consistently paired BRD PRD AD for T2; optional TestCase and prototype do not become universal prerequisites",
+        "Names the missing AD and corresponding T1 ad operation, then stops without an engineering SPEC or plan",
+        "Does not mutate handoff during this T2 check or silently substitute a different topic",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留路径、工具参数、JSON协议及机器状态。"
+      ]
+    },
+    {
+      "id": 1003,
+      "kind": "dialogue",
+      "prompt": "显式使用 i3-enterprise-sop plan，输入是已经认可的工程SPEC；tasks/todo.md还有其他事项的未完任务。请说明怎样复用原规划并保护现有计划，不开始Build。",
+      "expected_output": "T3 explicitly uses original planning, protects the unfinished plan and retains its review gate",
+      "expectations": [
+        "Actually invokes the original planning Skill through the host's supported mechanism and obtains its full method rather than imitating a planner",
+        "Reads the selected engineering SPEC and necessary referenced evidence, not every topic in the project",
+        "Keeps original unfinished-plan protection, tasks/plan.md and a single task target; asks before replacing conflicting unfinished work",
+        "Maps requirements and design constraints into tasks and verification, then stops for human review without Build",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留路径、工具参数、JSON协议及机器状态。"
+      ]
+    },
+    {
+      "id": 1004,
+      "kind": "dialogue",
+      "prompt": "显式使用 i3-enterprise-sop 做保存后的自查。长章节写入失败，尚不能确认落盘完整；我只授权目标文档和清单登记，没有授权临时脚本。请说明恢复和汇报，不宣称已经通过。",
+      "expected_output": "Evidence-based recovery at the actual persisted boundary, no extra self-check script files or false approval",
+      "expectations": [
+        "Inspects actual file state and distinguishes no write, partial write and failed receipt after write; resumes only missing or affected parts",
+        "Uses existing read-only tools or in-memory commands for routine self-checks, without writing temporary scripts or enlarging the authorized scope",
+        "Verifies persisted completeness and segment seams without making a full output reread universally mandatory",
+        "Separates structural checks, content self-check, real tool evidence, registration and human approval; retains original failure and stops when the safe boundary cannot be determined",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留路径、工具参数、JSON协议及机器状态。"
+      ]
+    },
+    {
+      "id": 1005,
+      "kind": "dialogue",
+      "prompt": "只用 i3-enterprise-sop 分析请求；未授权写稿、建目录、安装或登记。请只读说明T1、T2、T3的关系。",
+      "expected_output": "Read-only explanation without state changes or autonomous next-stage execution",
       "expectations": [
-        "Paths resolve against the confirmed project root and actual documents are read",
-        "A newly generated draft is only reported by path; selected changes only for an explicit user choice and business text is unchanged",
-        "Manual handoff does not create a JSON file or project directories",
-        "Original skills, commands, plans and task state are unchanged",
-        "No business approval, next-stage execution or publication is inferred",
-        "Drafting BRD, PRD, AD or TestCase loads original Spec successfully and preserves its save-and-stop gate",
-        "New business documents default to spec/ per capability; existing adopted paths are retained",
-        "Only the selected topic and necessary shared dependencies become original Plan inputs; original Build auto gates are retained",
-        "Short brd, prd, ad, testcase and plan actions ask only missing facts and do not write while awaiting an answer",
-        "Explicit plan successfully loads original planning Skill and preserves original command obligations and outputs, without JSON writes or Build",
-        "Manual and JSON Plan complete the same indexed shared reads and original command before native planning; scripts do not count as model reads; actual relevant dependency/build configuration is read rather than inferred from AD commands",
-        "AD capability/topic identity or direct-upstream path/PRD-version conflicts stop before native planning and any plan/todo or candidate-plan writes; suspected header typos are not self-resolved",
-        "PRD and AD independent version numbers may differ when the AD references the exact selected PRD version; optional TestCase/prototype do not become universal blockers",
-        "SOP preparation uses Read/Glob/Grep for file discovery instead of probing shell permission with ls/find/mkdir",
-        "The native plan retains full actual source paths and document versions for PRD, AD, adopted norms, contracts and engineering adoption; aliases in the plan or paths only in the conversation report are insufficient",
-        "用简体中文说明实际结果、缺口和未执行事项；保留上述全部工程要求，不推定业务批准、计划批准或发布。"
+        "Keeps T1 enterprise documents, T2 engineering SPEC and T3 original planning as distinct user-started stages",
+        "Does not create spec directories, handoff JSON, business drafts, plans or install tools during read-only analysis",
+        "Preserves human-review stops and does not call approval or a successful registration equivalent to permission for the next stage",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留路径、工具参数、JSON协议及机器状态。"
       ]
     }
   ]

package/package.json

@@ -178,17 +178,6 @@
     "docs/opencode-setup.md",
     "docs/other-hosts.md",
     "docs/skill-anatomy.md",
-    "docs/upstream-repository/AGENTS.md",
-    "docs/upstream-repository/CLAUDE.md",
-    "docs/upstream-repository/CONTRIBUTING.md",
-    "docs/upstream-repository/README.md",
-    "docs/upstream-repository/gitattributes.txt",
-    "docs/upstream-repository/gitignore.txt",
-    "docs/upstream-repository/manifest.json",
-    "docs/upstream-repository/opencode-skills.link",
-    "docs/upstream-repository/skill-gap.yml",
-    "docs/upstream-repository/skills-contributing.md",
-    "docs/upstream-repository/test-plugin-install.yml",
     "docs/windsurf-setup.md",
     "docs/workbuddy-setup.md",
     "plugin.json",
@@ -420,17 +409,6 @@
       "docs/opencode-setup.md",
       "docs/other-hosts.md",
       "docs/skill-anatomy.md",
-      "docs/upstream-repository/AGENTS.md",
-      "docs/upstream-repository/CLAUDE.md",
-      "docs/upstream-repository/CONTRIBUTING.md",
-      "docs/upstream-repository/README.md",
-      "docs/upstream-repository/gitattributes.txt",
-      "docs/upstream-repository/gitignore.txt",
-      "docs/upstream-repository/manifest.json",
-      "docs/upstream-repository/opencode-skills.link",
-      "docs/upstream-repository/skill-gap.yml",
-      "docs/upstream-repository/skills-contributing.md",
-      "docs/upstream-repository/test-plugin-install.yml",
       "docs/windsurf-setup.md",
       "docs/workbuddy-setup.md",
       "plugin.json",
@@ -487,7 +465,7 @@
       "scripts/validate-versions.js"
     ]
   },
-  "version": "3.1.0",
+  "version": "3.2.1",
   "repository": {
     "type": "git",
     "url": "https://github.com/49780522/i3-composer-agent.git"

package/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "i3-composer-agent",
-  "version": "3.1.0",
+  "version": "3.2.1",
   "description": "覆盖需求、计划、开发、测试、审查与发布的软件工程技能，默认使用简体中文。",
   "homepage": "https://github.com/49780522/i3-composer-agent",
   "repository": "https://github.com/49780522/i3-composer-agent"