@givolt/i3-composer-agent 2.3.7 → 3.1.0

package/bin/retired-sop-fingerprints.json

@@ -0,0 +1,213 @@
+{
+  "schemaVersion": 1,
+  "purpose": "Factory fingerprints only for safe owned-resource retirement; no old resource contents retained.",
+  "sources": [
+    {
+      "commit": "edf528abd8cdec66ed48c0c21eaba303cac076ba",
+      "scope": "reviewed old SOP native-install rendering",
+      "fileCount": 62
+    },
+    {
+      "commit": "d08bd88b2b5d597d42285c53c63779cd74342771",
+      "scope": "reviewed old SOP native-install rendering",
+      "fileCount": 63
+    }
+  ],
+  "files": {
+    "i3-composer-agent/references/engineering-skeleton-resources/README.md": [
+      "ff0b1942f517afc8d2b19eeeb3be9edb75c96cd7448347060ea256a2dbfcecb6"
+    ],
+    "i3-composer-agent/references/engineering-skeleton-resources/adoption.md": [
+      "7c5614439dcdb4466babb2844e977f40533d450f2a6769dcd498700ca2cc0211"
+    ],
+    "i3-composer-agent/references/engineering-skeleton-resources/catalog.json": [
+      "4c66ae6002141422954d6061784207fbc30ac7e3732adf5a5154dbe393c4fd24"
+    ],
+    "i3-composer-agent/references/engineering-skeleton-resources/directory-standard.md": [
+      "0186fd9922f5215f07f4585a9d36d60fc6b2af2c5080d3c38293f0a520ee4669"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/README.md": [
+      "bc7682df3abf7072e91fe00a7f45fb1a82cb216c81311b6951820d6ff8f8f2c0",
+      "9d8ce39c1cb121add394703f7be608cb79506efa0e486310b714b81f75e40ba6"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/ad/README.md": [
+      "8fa71b98a5269ae6571a9e5dbe2579419e41781183d0545d86687a44464f9535"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/ad/assets-manifest.json": [
+      "9723899fe88246c9cdec56c26d5a8f2f9af687ca85a2ee4c45d5a090ab7c9a97"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/ad/prompts/01-generate.md": [
+      "21d8fa23aee4787fa215e25aeecfcbf74bb2f6fb9f9e1103c32f34f577c9f3bb"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/ad/prompts/02-review.md": [
+      "60e2fdfc8a302c317f948b63af52555abd7bd711b7c161bbc9e9ba6d2aecc0f4"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/ad/prompts/03-revise.md": [
+      "462d37d715cdc3733481034218065f998a815bc4dc83f4036095c7ff8fe33e4f"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/ad/prompts/04-recheck.md": [
+      "3c585b8d8cf3afa03400e4027658b3763eef707e28a31dedd62aca73e8aa8e2e"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/ad/templates/AD.md": [
+      "12795726ba22b1b1d78f7c1cb8f01cdc612bcf4258320b8848c956fc5d9a838b"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/assets-manifest.json": [
+      "947b7221bd46d3a78cbfdb5978af874f5c5d0c5086ccb7371a5c9dca2f2033a5",
+      "318f95e8d713e6c3a12de7cf798f41503e8150efbe1f707aaa8db01790a67fa2"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/brd/README.md": [
+      "6259a9635321b0d307f7269cf0e02fcee7ea1907665cc26ed83cd2d250b71ab5"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/brd/assets-manifest.json": [
+      "0c30b154491590605873d8e01d596c7139c98eadda7830d5954d1fcc6df4b97b"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/brd/prompts/01-generate.md": [
+      "f0dd26a6f14491201b57737d39ba1e9c910aa00eb9d3b102ed49e33eb11e72ad"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/brd/prompts/02-review.md": [
+      "65268bc7f4c9145708faa030dd10eac70153229f0c431457a496e3ffed57383d"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/brd/prompts/03-revise.md": [
+      "c7765fc8d02f99a3582e27adf40d0501dbabf889b6d07664dedda7e7786473ac"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/brd/prompts/04-recheck.md": [
+      "3d368f2b654a1ec4de9903b6c694430d8d228a958feea28f8bda50c91c238217"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/brd/templates/BRD.md": [
+      "60e1030c3ea87ba744a55da798dc1056ddc9b2a8c274158cf42c300af71427d1"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/codebuddy-project-guide.md": [
+      "1204abff6ed77742b8fb8c9d896e75375c680828c9e8c72801f09fd9dcf3d741"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/controlled-handoff.md": [
+      "2e0d60bf761a54632e0e30fa603977bbed59954d01a1d86ff2c631c25f97649a"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/controlled_handoff.py": [
+      "a1a283544705b2af5b160446d6aa7c2bdf31c84455a5ca15c50cd7234fedfc31"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/handoff-contract.md": [
+      "e0683a906b0b73150ef4e8ccab9f8a8ddfb2be0f8e7cb614cc5c8ebaa0e2a222"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/handoff.py": [
+      "3bf15a56359c7dbd66d97e1b6ec0a813b97aed371d20b44c3d92f52debae9c5c"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/lifecycle-contract.md": [
+      "7e649350a66c4ef7387a8e1736f971bfe09e819ce44130d12313776d292d23ab"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/plan-handoff.md": [
+      "3633f4907b989f0d9ba55393c390c59f749bbc7d09dee7e147e5519036a41057"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/prd/README.md": [
+      "994b0b3787227a177375a78e6c53c782a81a6e99441004a836394eec8243a24b"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/prd/assets-manifest.json": [
+      "1e1074971bd93414616d3d66a0b2da63d56a8c19f239165c774f50a552a17c7e"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/prd/prompts/01-generate.md": [
+      "33b0f249f93b3ccf1571a608fa0d2ddd3993cd3483b9d87a64618c8c9baeba67"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/prd/prompts/02-review.md": [
+      "dd9d2691591a04b5445630c30906f226b070e53ea61b1d2875a04e61ffe43ab4"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/prd/prompts/03-revise.md": [
+      "688968944b69d41db68b006096090b2f7db563473c932f4bdc550b9158ea545f"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/prd/prompts/04-recheck.md": [
+      "1d7960f9e92363cbf1f1c841c0506e5852d2cb859615375caff53f4da537f4d2"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/prd/template-contracts.md": [
+      "478b2d6d92898077c38af1156d7b305fc6127b7cb6743068fa107f05d916053b"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/prd/templates/AD.md": [
+      "accd3c5870584c5942458935df78724447852e070d173a84142c784b3327813c"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/prd/templates/PRD.md": [
+      "ab257108b4a6d05ec776139b64e1a18f4a29eeb2fbfedf881732ec4fbd8f5c87"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/recovery-contract.md": [
+      "a15709274e8ac88510f4bfc4c8970ef25a037e11d419b2ce6e4ba891225ceca2"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/review-handoff.md": [
+      "19b44ff8e9d26bc802d57ec76f39dbd2eb97cb4c3ed60aa146e085c46d9a1207"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/selection-handoff.md": [
+      "bac7445b776e16bef0c3a7ecaa3fdb37e55e19037dd5dccd7f453804543285ad"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/selection_handoff.py": [
+      "d2b1f8622c3969abca8fd69cd59b024387e3d0e1c208e00cef31a9032484d448"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/stages.json": [
+      "da2ccd8bab9acfaa260b5b6c1159d9a69dfa22d2e1ddf15777b61fbd3d434ba3",
+      "3a131b57220ebc9a4d0fcd7f8ba8de9bb461bf694097390c5e6334020bc8e16b"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/technical-baseline/README.md": [
+      "b56df22a69f34b5fcc60b621cce82b5fb009c92ae2f653635f27e8aafc189394",
+      "d6c628d90ed9a896aeb3610ef699062d55353db8d87f05d6e70db2cc9acd9708"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/technical-baseline/assets-manifest.json": [
+      "d23b6f1efe325e1a52d789453d1889b9e199cac1db0fb55dc6a31b9547e52d13",
+      "c177ed9625c5330d3876ccd749d4eb150f72595c6832f6f4898e0f40ed96815e"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/technical-baseline/baselines/PROVENANCE.md": [
+      "bb362aafbf6cd015e9ff7838575e308ade00951aa20aa709be1e80c9d8162c9a",
+      "45bcb01f55706e3745b24178c40027739d79236c0ef8ae0ab8776a184a8c2ffb"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/technical-baseline/baselines/企业应用-技术规约_v0.0.2.md": [
+      "52bd2692ec9e4bfa0456feca9c0c912cd5c06f27519e563416f35af73c0d140f"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/technical-baseline/references/engineering-directory-v0.2.0/adoption.md": [
+      "537b1ad152ea324c91ccaee3fe58bc0b90477a39c4c4c55633093da7c7f81c72"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/technical-baseline/references/engineering-directory-v0.2.0/directory-standard.md": [
+      "98a6d0a72af41e94020bd43fa162a0a6ace504a7c3a75de6bf045cad662b35ba"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/technical-baseline/templates/TECHNICAL-BASELINE.md": [
+      "07a0d16049290f90e73049eaad06636a37d5322488acc8e0352d52f121136c8a"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/template-contracts.md": [
+      "6ba87654fbbf861a0c8ed7e440161e36cbe902e3beaba625c5ec29553aa896c1"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/testcase/README.md": [
+      "e07ae9254f514f075a54bbf0784724694628918489f5d09eaef33f6a6a2e302c"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/testcase/assets-manifest.json": [
+      "77c60991357f7deb8515641047f5f6f7c61aa052310c62a2dca5b20b2c82a2b3"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/testcase/prompts/01-generate.md": [
+      "f861de54675fb10f62f791d4eeec0448bff5c4e0af84c432075c1af68e244a98"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/testcase/prompts/02-review.md": [
+      "bf37eed2c696b61e424cbc7198d116d0779521a6331cd78e1608e3d9ea3691d5"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/testcase/prompts/03-revise.md": [
+      "f0f9e90e604c0b4762a5f00f69fa13b88d29d353d2054382cb24cc37de7412df"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/testcase/prompts/04-recheck.md": [
+      "84612397bc99db0aaf6dc2da6459ff44440b77ece4261faf4275e09d5d61b2f6"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/testcase/templates/TestCase.md": [
+      "c1bc7183ae418a8662b824fc830cc93e62ec14a6075766c36248eaf22ee07eef"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/verification/README.md": [
+      "63f8e6b158ed1b9bb778b2401eeef106e22c18df20ab815d373b17d4db1cdc34"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/verification/check_execution.py": [
+      "b65d757755e7d1a0ba934d79d7d70132e27a273a5cfa07d0df7e57dc03d21e63"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/verification/check_native_execution.py": [
+      "fccc755128cb76c3f77341e7c1ae83ee4ed3a29c38745581d74224b70d9f6577"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/verification/check_reads.py": [
+      "c451ac1b79f1c0f90881166616e943c26c314848f8af965e88618bc4e55f5b8a"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/verification/review-output.schema.json": [
+      "ac0e266ec2567ea40238d2e59830e288efcba1867aff7df14127b77bf044cacb"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/verification/review_handoff.py": [
+      "176e2e06b1df8fbc67130c91b08628e515cd5440c0208c8b5d8376802eb46d9b"
+    ],
+    "i3-composer-agent/references/enterprise-sop-resources/technical-baseline/baselines/企业应用-技术规约_v0.0.3.md": [
+      "6ed32557f19d609f465a7c6e4b8e395522fb24c6d6cdfc81d8ddef93460514c5"
+    ]
+  }
+}

package/bin/wizard.cjs

@@ -42,18 +42,9 @@ async function chooseSettings(options, agents, ask) {
     }
     const supported=agents.some(host=>['codebuddy','workbuddy'].includes(host));
     let hooks=options.hooks||options.prototypeHooks||(supported?'default':'keep');
-    const hookGroups=options.hookGroups||'prototype',codebuddyProduct=options.codebuddyProduct,
+    const hookGroups=options.hookGroups,codebuddyProduct=options.codebuddyProduct,
       codebuddyTranscriptRoot=options.codebuddyTranscriptRoot,codebuddySkillRouting=options.codebuddySkillRouting;
-    if(process.platform==='win32'&&hooks==='default'){
-      hooks='keep';console.log('Windows 原型 Hooks 尚待实机验证，本次保留设置。');
-    }else if(supported&&hooks==='default')console.log('默认注册原型审计 Hooks；保留明确禁用状态。IDE/CLI 运行时自动识别，其他 Hook 组不新增注册。');
-    let prototypeSkills = options.prototypeSkills;
-    if (prototypeSkills === undefined) {
-      console.log('可选原型依赖：所选项将联网下载官方固定版本，安装到本次宿主范围；已有可用内容复用。');
-      prototypeSkills = await menu(ask, 'UIUX / antDv：1. 两项都安装（推荐），2. 仅 UIUX，3. 仅 antDv，4. 跳过 [1]（0 取消）： ', { '1': 'uiux,antdv', '2': 'uiux', '3': 'antdv', '4': 'none' }, '1');
-      if (prototypeSkills === null) return null;
-    }
-    return { agents, scope, hooks, hookGroups, codebuddyProduct, codebuddyTranscriptRoot, codebuddySkillRouting, prototypeSkills };
+    return { agents, scope, hooks, hookGroups, codebuddyProduct, codebuddyTranscriptRoot, codebuddySkillRouting };
 }
 async function choose(options, identity) {
   console.log(identity);
@@ -67,20 +58,18 @@ async function confirm(plan, selection = {}) {
   for (const target of plan.targets) {
     console.log(`  ${target.agents.join(', ')}: ${target.skillsDirectory}`);
     if (target.commandsDirectory) console.log(`  命令：${target.commandsDirectory}`);
-    console.log(`  评测：${target.evalsDirectory}`);
-    console.log(`  脚本：${target.scriptsDirectory}`);
-    console.log(`  Hook：${target.hooksDirectory}`);
+    console.log(`  使用说明：${target.docsDirectory}`);
   }
   if (plan.conflicts.length) console.log(`将替换 ${plan.conflicts.length} 个已有内容；安装成功后清理旧文件，失败则恢复。`);
   if (plan.reused.length) console.log(`将复用同版本的 ${plan.reused.length} 个未修改内容。`);
   if (selection.hooks) {
     for(const hook of Array.isArray(selection.hooks)?selection.hooks:[selection.hooks]){
-      console.log(`${hook.host} Hooks：${hook.action==='enable'?'注册 '+hook.groups.join('、'):'保留现状'}；IDE/CLI 自动识别。`);
-      console.log('桌面端重载；CodeBuddy CLI 在 /hooks 审核。真实调用和补调须在宿主验证。');
+      if(hook.action!=='enable')continue;
+      console.log(`${hook.host} Hooks：注册 ${hook.groups.join('、')}。`);
+      console.log('设置改变后重载桌面端；CodeBuddy CLI 按宿主要求在 /hooks 审核。');
     }
   }
-  if (selection.prototypeSkills !== undefined) console.log(`可选依赖：${selection.prototypeSkills === 'none' ? '跳过' : selection.prototypeSkills.split(',').map(id => id === 'uiux' ? 'UIUX Pro Max' : 'antDv 官方 Skill 与工具').join('、')}。`);
-  console.log('包含技能、共享资料和完整评测/Hook/脚本配套。安装不执行评测。');
+  console.log('将安装所选宿主的技能、命令、使用说明和配套资源。');
   return session(async ask => {
     while (true) {
       const answer = await ask('确认安装这些内容：1. 开始安装，0. 取消 [0]： ');

package/commands/i3-sop.toml

@@ -0,0 +1,19 @@
+description = "显式使用企业 SOP，复用原规格方法完成单阶段文档与交接"
+# i3-description-source: "description = \"显式使用企业 SOP，复用原规格方法完成单阶段文档与交接\""
+
+prompt = """
+<!-- i3:zh-CN:start -->
+## 中文交互与输出
+
+默认使用简体中文回复，包括追问、选项说明、阶段进度、分析、规格、计划、验收、代码审查与发布报告。只有用户明确要求其他语言时才切换；输入中出现英文术语、代码或引用不构成切换语言的要求。
+下文的工程步骤、审批要求、退出条件和工具约束完整有效。英文示例中的人类可读标题、说明和占位内容在实际输出时应译为中文；保留原有信息与验证标准，不删减方法。
+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，复用原规格方法完成单阶段文档与交接
+<!-- 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.
+
+$ARGUMENTS
+"""

package/commands/i3-ui-demo.toml

@@ -0,0 +1,21 @@
+description = "使用内置模板和固定设计、组件能力创建及增量修改 UI 原型。"
+# i3-description-source: "description = \"Create and incrementally update template-based Vue and antdv-next UI demos\""
+
+prompt = """
+<!-- i3:zh-CN:start -->
+## 中文交互与输出
+
+默认使用简体中文回复，包括追问、选项说明、阶段进度、分析、规格、计划、验收、代码审查与发布报告。只有用户明确要求其他语言时才切换；输入中出现英文术语、代码或引用不构成切换语言的要求。
+下文的工程步骤、审批要求、退出条件和工具约束完整有效。英文示例中的人类可读标题、说明和占位内容在实际输出时应译为中文；保留原有信息与验证标准，不删减方法。
+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 保留其原始语义与机器值。不得因翻译降低门槛，角色不能互相委派。
+
+适用说明：使用内置模板和固定设计、组件能力创建及增量修改 UI 原型。
+<!-- i3:zh-CN:end -->
+
+Explicitly invoke the i3-ui-demo skill in the current session for the request below.
+Keep its template choices, dependency preparation, output locations and verification rules in that skill.
+Preserve explicit read-only limits, confirmed choices and manual edits. Continue necessary user choices in this session.
+
+$ARGUMENTS
+"""

package/docs/codebuddy-setup.md

@@ -9,8 +9,8 @@ npx @givolt/i3-composer-agent --codebuddy
 ```
 
 向导预选 CodeBuddy，可增加其他工具，再选择项目或全局范围。
-项目安装提供 `.codebuddy/skills/`（26 个技能）、
-`commands/`（10 个命令）和 `agents/`（4 个角色）。
+项目安装提供 `.codebuddy/skills/`（28 个技能）、
+`commands/`（12 个命令）和 `agents/`（4 个角色）。
 同级 `i3-composer-agent/` 是配套工具根，集中提供 `package.json`、`evals/`、`hooks/`、`scripts/`、`docs/`、`references/` 和校验输入 `adapters/`，
 只有一份实际技能、命令和角色，评测与宿主共用。
 全局使用 `~/.codebuddy/` 的相同结构。默认中文说明和回复；技能/命令标识不改名。
@@ -40,28 +40,26 @@ CodeBuddy 与 WorkBuddy 项目共用 `.codebuddy/`；同版本追加客户端会
 全局目录彼此独立。WorkBuddy 桌面版建议全局安装，详见 [WorkBuddy 说明](workbuddy-setup.md)。
 升级或同名冲突先查看 `--dry-run`，再确认或使用 `--yes --force`。
 
-## 原型官方依赖可选安装
+## 原型必备依赖默认准备
 
-默认安装仅包含 i3 自身技能，UIUX Pro Max 与 antDv 官方 Skill 可不安装。CodeBuddy 项目安装可明确选择：
+向导默认准备 `ui-ux-pro-max`（基线 2.15.0）、`antdv` 官方 Skill 和 `@antdv-next/cli`（基线 0.0.0-beta.6，固定官方快照），不再选择单项或跳过。保留工具、项目／全局范围和一次最终确认。
 
-```bash
-npx @givolt/i3-composer-agent --codebuddy --scope project --yes --prototype-skills uiux,antdv
-```
+缺失时安装；同版检查通过即复用；高版保留并提示，兼容检查通过才接受；低版提示升级，沿用整体安装确认。低版设计技能升级前完整备份，旧 CLI 目录保留。版本未知、资源损坏或查询失败时不显示安装完成。两项通过后只显示“安装完毕”和本包版本。
 
-值为 none、uiux、antdv 或 uiux,antdv；默认 none。可选工具跟随宿主和项目／全局范围，位于基址下 `tools/i3-prototype/`；旧项目 `.prototype-tools` 保持读取兼容。需要固定本次版本时使用 `npx @givolt/i3-composer-agent@2.3.7`。已安装后可随时单独检测／补装，无需重装 i3：
+`i3-ui-demo` 专用工具位于所选宿主范围的 `tools/i3-ui-demo/`。工具版本可较高，但实际组件及查询知识始终使用 `antdv-next` 1.6.0。安装／检查不代表宿主已实际调用 Skill。
 
 ```bash
-node .codebuddy/skills/i3-ui-prototype/scripts/prototype-dependencies.cjs check --host codebuddy --scope project --project .
-node .codebuddy/skills/i3-ui-prototype/scripts/prototype-dependencies.cjs install --host codebuddy --scope project --project . --skills uiux,antdv
+node .codebuddy/skills/i3-ui-demo/scripts/dependencies.cjs check --host codebuddy --scope project --project .
+node .codebuddy/skills/i3-ui-demo/scripts/dependencies.cjs prepare --host codebuddy --scope project --project . --accept
 ```
 
-检测只读，不下载安装。安装需要网络，固定官方版本并保留原名与来源，已有可用安装复用；已有不可用目录保留并提示修复，不自动覆盖、全局升级或安装 Python。UIUX 专业模式缺项时提示，用户明确选择基础模式后仍可生成并保留同样功能验收；antDv Skill 缺失可按官方版本资料渠道实施。后续安装不改变已有实例模式或旧验收，CodeBuddy 必要时重载窗口／新建会话。目录与检测通过不等于宿主实际调用。
+只有已授权安装时才使用 `--accept`；缺项时也可重新运行向导。`--prototype-skills none` 或单项旧参数会提示移除，不会跳过检查后声称安装完毕。
 
 ## 主会话原型流程与使用入口
 
 原型由主会话使用 `.codebuddy/skills/i3-ui-prototype/`，按同一方法完成需求理解、设计、制作、修订与验证。Skill 保存模板、能力、框架和验收规则；按任务需要复用前端工程方法、官方框架知识、UIUX Pro Max 和浏览器测试能力。HTML 是内容参考，生成结果采用真实框架组件。
 
-模板编辑、构建、证据登记和后续修改的完整命令见[首期使用与续接](ui-prototype-native/USAGE.md)。
+模板编辑、构建、证据登记和后续修改以当前 [i3-ui-prototype 技能](../skills/i3-ui-prototype/SKILL.md)及其相关参考资料为准。
 
 自然语言可以这样提出任务：
 
@@ -106,11 +104,11 @@ node .codebuddy/skills/i3-ui-prototype/scripts/native-pilot.cjs preview prototyp
 
 在业务项目运行 `node .codebuddy/i3-composer-agent/scripts/run-evals.js --min-rank1 95`，
 可检查中英文触发，不调用模型；进入 `.codebuddy/i3-composer-agent/` 可运行 `npm test` 和 `node scripts/run-evals.js --locale zh-CN --min-rank1 95`。全局安装使用脚本的全局绝对路径。五项校验、行为评测和样例用法见
-[评测说明](../evals/README.md)。CodeBuddy／WorkBuddy 默认注册原型审计 Hooks，其他组按需管理。
+[评测说明](../evals/README.md)。原型审计 Hooks 已移除；其他原版组按需显式管理。
 
 ## CodeBuddy 统一 Hooks 管理
 
-原版 `session-start`、`sdd-cache`、`simplify-ignore` 与新增 `prototype` 四组统一由安装器及 `.codebuddy/i3-composer-agent/hooks/manage.cjs` 管理。`i3-prototype.cjs` 是新增审计注册入口，委托 Skill 内原有实现；旧 helper 和 `--prototype-hooks` 参数保留。原版脚本保持，包装只处理宿主路径与输入字段。测试/说明文件不注册。
+原版 `session-start`、`sdd-cache`、`simplify-ignore` 三组由 `.codebuddy/i3-composer-agent/hooks/manage.cjs` 按需管理，原脚本不改。prototype 审计组已退役；安装升级清理本包旧注册，两个旧回调入口均不再执行审计。旧 helper 和 `--prototype-hooks` 仅保留检查／清理兼容。
 
 ```sh
 # 已安装后只读列举/检查，项目根运行
@@ -121,13 +119,13 @@ node .codebuddy/i3-composer-agent/hooks/manage.cjs enable --host codebuddy --sco
 node .codebuddy/i3-composer-agent/hooks/manage.cjs disable --host codebuddy --scope project --project . --groups sdd-cache
 ```
 
-全局改用 `~/.codebuddy/i3-composer-agent/hooks/manage.cjs` 和 `--scope global`，继续指定测试项目来判断有效来源。发行 CLI 可用 `hooks list|check|enable|disable` 子命令；安装时使用 `--hooks enable --hook-groups <ids>`，默认注册 prototype 并保留明确禁用，显式 keep 保留全部既有开关。启停不指定组时兼容旧用法仅针对 prototype，list/check 默认全部。
+全局改用 `~/.codebuddy/i3-composer-agent/hooks/manage.cjs` 和 `--scope global`，继续指定项目来判断有效来源。发行 CLI 支持 `hooks list|check|enable|disable`；安装时显式启用原版组用 `--hooks enable --hook-groups <ids> --codebuddy-product ide|cli`。默认不新增注册；升级及 keep 均精确清理本包旧 prototype 注册，其他组的开关保留。enable 必须指定组；disable 未指定组时仅兼容旧 prototype 清理，list/check 默认检查三组及退役状态。
 
-`session-start` 需要明确 `--skill-routing hook`，已有原生路由时不选该组；安装器对应 `--codebuddy-skill-routing hook`。上游三组需要 Bash、jq 和相应 SHA 工具，缓存另需 curl，缺依赖会在启用前拒绝；不自动安装。prototype 新注册默认 auto 自动识别；旧 `--product ide|cli` 兼容。项目／全局新启用默认从 Hook 自动识别当前会话日志，可选 `--transcript-root <实际目录|auto>`。已有手动限制保留，首次尚无原生事件显示 awaiting-native-event，不能当成已验收。全局跟随绝对 CODEBUDDY_CONFIG_DIR，默认 ~/.codebuddy；不移动原生日志。原型严格证据规则见 Skill 的 execution-evidence 参考资料。
+`session-start` 需要明确 `--skill-routing hook`，已有原生路由时不选该组；安装器对应 `--codebuddy-skill-routing hook`。上游三组需要 Bash、jq 和相应 SHA 工具，缓存另需 curl，缺依赖会在启用前拒绝；不自动安装。启用需指定实际 IDE／CLI。全局跟随绝对 CODEBUDDY_CONFIG_DIR，默认 ~/.codebuddy。原型不再注册或扫描会话日志；历史兼容见 Skill 的 execution-evidence 参考资料。
 
-配置合并到所选范围 `settings.json`，通用归属在 `state/i3-composer-agent/hooks.json`，原型归属保持 `state/i3-prototype/installation.json`。上游适配缓存在 `<host-base>/cache/i3-composer-agent/hooks/<projectKey>/`；全局按项目隔离。已识别的手动原版注册只报告，不自动接管或重复注册。代码块保护运行时会临时替换文件内容，存在未恢复备份时拒绝移除该组，先结束会话恢复。
+配置合并到所选范围 `settings.json`，通用归属在 `state/i3-composer-agent/hooks.json`。旧原型 installation.json 清理前归档到 `state/i3-prototype/history/`，原会话记录保留。被手改的自有注册或未知归属会停止处理，保留现场。上游适配缓存在 `<host-base>/cache/i3-composer-agent/hooks/<projectKey>/`；全局按项目隔离。已识别的手动原版注册只报告，不自动接管或重复注册。代码块保护存在未恢复备份时拒绝移除该组，先结束会话恢复。
 
-IDE 项目设置覆盖全局；CLI 合并后按组选择有效来源避免同组重复执行。CLI 变更后在原生 `/hooks` 审核并新建会话，IDE 重载。文件存在、注册、回调观察与业务验收分别显示；原版 triggered 不表示已验证模型行为。首期仍待用户实际宿主验收，Windows Hooks 未验证，Windows 默认保留设置并提示尚待实机验证。
+IDE 项目设置覆盖全局；CLI 合并后按组选择有效来源避免同组重复执行。CLI 变更后在原生 `/hooks` 审核并新建会话，IDE 重载。文件存在、注册、回调观察与业务验收分别显示；原版 triggered 不表示已验证模型行为。首期仍待用户实际宿主验收，Windows 的原版 Hook 启用仍未验证；旧原型精确清理不新增可执行命令。
 
 依据：[CodeBuddy IDE Hooks](https://www.codebuddy.cn/docs/ide/Features/Hooks)、[CodeBuddy CLI Hooks](https://www.codebuddy.cn/docs/cli/hooks)。
 
@@ -150,7 +148,7 @@ npx @givolt/i3-composer-agent --prepare --codebuddy
 按宿主选择范围并启用后新建会话。兼容清单声明 `.claude/commands/` 与 `commands/`。
 插件命令示例为 `/i3-composer-agent:i3-spec`、`/i3-composer-agent:i3-plan`、
 `/i3-composer-agent:i3-build auto` 和 `/i3-composer-agent:i3-ship`。
-默认原生安装和导出均包含完整评测、Hook 与脚本；原生安装默认注册 prototype，插件导出不自动启用 Hook。
+默认原生安装和导出均包含完整评测、原版 Hook 与兼容脚本，不自动启用 Hook；原生升级清理本包旧原型审计注册。
 文件落盘、宿主发现和模型实际执行应分别验证。
 
 目录遵循 [配置目录参考](https://www.codebuddy.cn/docs/cli/codebuddy-dir)，可参照
@@ -160,15 +158,14 @@ npx @givolt/i3-composer-agent --prepare --codebuddy
 原型共享资料统一在项目 prototypes/：新索引 prototypes/index.json，准备范围 prototypes/.preparation/<id>/scope.json。新原生 scope.moduleIds 自动生成 appliesTo；旧索引、输入和实例保持兼容，安装升级不自动迁移。工具及运行缓存使用所选宿主基址；全局浏览器缓存按业务项目身份隔离。详细规则和只读查询／显式迁移命令见 i3-ui-prototype/references/project-layout.md。
 
 
-## 默认原型 Hooks、自动识别与补调
+## 原型审计退役与本地 antDv
 
-首次项目／全局安装默认注册 prototype，无需选择 IDE 或 CLI，其他上游 Hook 组不新增注册。已有明确禁用保留，显式 --hooks keep 可以跳过；升级保留用户设置与已有其他组。注册不代表已触发；桌面重载、CLI 在 /hooks 审核后按实际项目检查。
+CodeBuddy／WorkBuddy 项目和全局的新安装均不注册原型审计 Hook。升级只清理精确归属的旧注册并归档记录；原型与 QA、其他 Hook 和用户权限保留。被手改或未知归属先报告，不强行清理。清理后重载受影响宿主。
 
 ```bash
 node .codebuddy/i3-composer-agent/hooks/manage.cjs check --host codebuddy --scope project --project .
-node .codebuddy/i3-composer-agent/hooks/manage.cjs enable --host codebuddy --scope project --project . --groups prototype
 node .codebuddy/i3-composer-agent/hooks/manage.cjs disable --host codebuddy --scope project --project . --groups prototype
 node .codebuddy/skills/i3-ui-prototype/scripts/prototype-dependencies.cjs query --host codebuddy --scope project --project . --kind info --component Table --version 1.5.2
 ```
 
-query 使用已准备的本地 Node／CLI，不能代替 antDv Skill 加载；知识版本与目标组件版本分别核对。新实例使用 buddy-ab-v2，旧实例保留原合同。漏调 Skill 后受管写入被拒，反馈具体调用名，成功加载后重试；每缺项最多两次、任务最多六次自动纠正，持续失败如实阻塞。记录包含补调和成功重试的原生引用，不能用模型自述或文件读取代替。
+check 只读；disable 只清理旧 prototype 注册，enable 已拒绝。query 不代替 antDv Skill 加载，知识版本与目标组件版本分别核对。实际 Skill 调用、固定业务断言、构建和浏览器验收要求保留，正常流程不要求审计 Hook 绑定，自动调用审计显示未验证。

package/docs/codex-setup.md

@@ -7,7 +7,7 @@ npx @givolt/i3-composer-agent --codex
 ```
 
 项目范围写入 `.agents/skills/`，全局写入 `~/.agents/skills/`，并安装同级 `i3-composer-agent/references/`。
-提供全部 26 个 `i3-` 技能，中文选择说明与默认中文回复在每个入口独立生效。
+提供全部 28 个 `i3-` 技能，中文选择说明与默认中文回复在每个入口独立生效。
 同级 `evals/`、`hooks/`、`scripts/`、`docs/` 各自以 `i3-composer-agent/` 分组资料。
 命令与角色文件也会提供，供按需阅读，其自动发现由宿主决定。
 从项目目录执行 `node .agents/i3-composer-agent/scripts/run-evals.js --min-rank1 95`
@@ -37,6 +37,6 @@ Codex 已有原生技能路由，勿把元技能全文预加载为常驻上下
 
 ## 可选原型工具
 
-原型辅助工具位于本宿主基址的 `tools/i3-prototype/`，支持项目和全局范围；旧项目 `.prototype-tools` 继续读取兼容。项目安装可使用 `npx @givolt/i3-composer-agent@2.3.7 --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.1.0 --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/comparison.md

@@ -0,0 +1,131 @@
+<!--
+  This document is for developers evaluating the project. It is NOT a skill and
+  is not meant to be loaded into an agent's context. It lives in docs/ so it
+  stays out of the agent's working set.
+-->
+
+# How agent-skills compares
+
+> **Upstream research:** This comparison is retained from Addy Osmani's `agent-skills` at commit `aeac41d4d005999432bb7312f7ff06383a91d59d`. Its experiments describe the upstream project; they are not independent evaluations of i3 Composer Agent.
+
+People often ask how **agent-skills** relates to the two other "skills for coding agents" collections they hear about most: **Superpowers** (Jesse Vincent / obra) and **Matt Pocock's skills**. All three are good, share a lot of DNA, and are worth learning from. This page is an honest map of how they are *shaped* differently, so you can pick the one that fits how you work, or borrow across all three.
+
+> **TL;DR** — They optimize for different moments. **agent-skills** organizes the *whole product lifecycle* (Define, Plan, Build, Verify, Review, Ship) with review personas, anti-rationalization guards, and an in-repo eval framework that checks the skills actually route and behave. **Superpowers** leans into *autonomous, reasoning-heavy* runs with subagents, a strict pipeline, and worktree isolation. **Matt Pocock's skills** are a *sharp, opinionated Claude Code toolkit* distilled from one expert's daily workflow, with a signature "grill me" interrogation loop. None is "best" in the abstract; it depends on the work in front of you.
+
+---
+
+## At a glance
+
+| | **agent-skills** | **Superpowers** | **Matt Pocock's skills** |
+|---|---|---|---|
+| **Core idea** | Encode the full senior-engineering lifecycle as skills | A complete development *methodology* built on composable skills | One expert's Claude Code workflow, open-sourced and evolving |
+| **Organizing principle** | SDLC **phases** (Define to Ship) behind a meta-skill router | A single disciplined loop: brainstorm, plan, execute, review | A curated toolbox of focused, composable commands |
+| **Catalog size** | 25 skills spanning the whole lifecycle | ~14 skills, deep on the inner build loop | ~30 skills, grouped into engineering / productivity / in-progress / deprecated |
+| **Lifecycle coverage** | Broad: idea refinement, API and UI design, security, performance, CI/CD, observability, deprecation, ADRs, launch | Deep but narrow: TDD, debugging, planning, review, skill authoring | Define and Build heavy: grilling, PRDs, issues, TDD, architecture, bug triage, knowledge management |
+| **Entry points** | Slash commands mapped 1:1 to phases (`/spec` `/plan` `/build` `/test` `/review` `/code-simplify` `/ship`, plus `/webperf`), with a `/build auto` full-plan mode | Skill-chained pipeline (`brainstorming`, `writing-plans`, `subagent-driven-development`) | Slash commands (`/grill-me`, `/tdd`, `/to-prd`, `/diagnosing-bugs`, `/grill-with-docs`) |
+| **Distinctive mechanisms** | Anti-rationalization tables and Red Flags in every skill; parallel review **personas** in `/ship`; reference checklists; a **three-tier eval framework** in CI | Subagent-driven development with a task reviewer (spec + quality) and a fix loop; git-worktree isolation; skills-that-write-skills, pressure-tested | The **grilling** primitive (one question at a time, design-tree walking); seam-based TDD; explicit user-invoked vs model-invoked split; issue-tracker integration |
+| **Quality measurement** | Trigger, routing, and behavioral evals run against the catalog (in-repo, some in CI) | Pressure-testing methodology is core to its philosophy; the eval suite itself now lives in a separate repo | None shipped in-repo |
+| **Tooling reach** | Claude Code, Cursor, Gemini CLI, Antigravity, OpenCode, Windsurf, Copilot, Kiro, Codex, Command Code, plus the `npx skills` CLI | One of the widest and most actively churned surfaces: Claude Code, Codex, Cursor, Copilot CLI, OpenCode, Kimi, Factory Droid, Antigravity, Pi | Claude Code first, distributed via `npx skills add`; other agents work with varying fidelity |
+| **Governance** | Actively reviews and merges community contributions; every skill ships an eval | Largely solo-authored; a substantial backlog of unmerged community PRs | Solo-authored, self-merged, developed openly in public |
+| **Best for** | Driving a feature through every phase with a human checkpoint at each | Long, autonomous, reasoning-heavy or exploratory work | A pragmatic, battle-tested daily loop, strongest at requirements and TDD |
+
+*(We deliberately leave out star counts and adoption figures: they are cited wildly differently across blogs and change weekly. All three are actively used and maintained.)*
+
+---
+
+## The three projects, in their own terms
+
+### Superpowers (obra)
+
+A full software-development *methodology* built on composable skills. It bets on **autonomy and upfront reasoning**. A session runs a deliberately linear pipeline: Socratic brainstorming that writes a dated spec and permits exactly one handoff, detailed plans written to be executable by "an enthusiastic junior engineer with poor taste and no context," then subagent-driven execution where a fresh subagent implements each task and a task reviewer signs off on both spec compliance and code quality before it closes, with a fix loop for anything it flags and a whole-branch review on the most capable model at the end. Git worktrees keep parallel work isolated, and its `writing-skills` skill applies TDD to documentation itself: no skill ships without a failing test first.
+
+Its strengths are real: hand off a sizable chunk and come back to a reviewed result, with strong guardrails against an agent rationalizing its way past the process. The trade-offs are the flip side of that discipline. Coverage is narrow (it is an inner-loop build methodology, not a security-to-launch lifecycle), the single pipeline can feel heavy on small changes, and the recent direction has been about paying down that cost, for example consolidating to a single task reviewer for roughly twice the speed and half the tokens. The loudest thing its community keeps asking for, multi-agent team execution, is not yet in the box.
+
+**Repo:** <https://github.com/obra/superpowers>
+
+### Matt Pocock's skills
+
+Matt open-sourced the Claude Code skills he actually uses, and the collection has grown into a broad, opinionated toolbox organized in public, complete with visible `in-progress/` and `deprecated/` directories that model the discipline the skills preach. The center of gravity is not TDD, it is **grilling**: a reusable interrogation loop that asks one question at a time, walks each branch of the design tree resolving dependencies in order, offers a recommended answer per question, prefers reading the codebase over asking, and refuses to proceed until you confirm a shared understanding. `grill-me` and `grill-with-docs` are thin wrappers over it. The TDD skill is distinctive too and cheerfully heterodox ("refactoring is not part of the loop," it belongs to code review), and there is a deliberate split between user-invoked and model-invoked skills to treat agent context as a scarce budget.
+
+Its strengths are authenticity and sharpness: this is how one very good engineer ships, not a committee's idea of a framework, and the requirements-grilling loop is genuinely excellent. The trade-offs: it is Claude Code first in practice (other agents surface reliability rough edges), there are no in-repo evals to catch regressions, lifecycle coverage past Build is thin, and some skills couple to a personal setup wizard and tracker conventions. Recent work is pushing from single-session skills toward multi-session orchestration through issue trackers (the in-progress `wayfinder`).
+
+**Repo:** <https://github.com/mattpocock/skills> · related: <https://github.com/mattpocock/agent-rules-books>
+
+### agent-skills (this project)
+
+agent-skills organizes the **entire product lifecycle** as skills, with a meta-skill (`using-agent-skills`) that routes a task to the right one. Every skill carries a **Common Rationalizations** table (the excuses an agent makes to skip a step, each rebutted) and **Red Flags**. Slash commands map one-to-one to lifecycle phases; `/build auto` runs a whole approved plan in one pass; and `/ship` fans out review **personas** (`code-reviewer`, `security-auditor`, `test-engineer`, `web-performance-auditor`) in parallel, then merges them into a go/no-go. It keeps a human checkpoint at each phase, ships seven reference checklists including a Definition of Done, and runs across most major agent tools with a single-command install on several of them.
+
+What is newer, and the current point of difference: a **three-tier eval framework** lives in the repo. Tier 1 checks structure, Tier 2 checks that each skill's description carries the vocabulary users actually say and that no two skills collide on routing (deterministic, runs in CI), and Tier 3 grades an agent's real execution trace against per-skill expectations. Neither of the other two ships that kind of in-repo, catalog-wide measurement today. The honest trade-off in the other direction: agent-skills has less of a single opinionated "run" than Superpowers, and none of the three has yet solved durable cross-session memory well.
+
+---
+
+## A real head-to-head: Superpowers vs. agent-skills
+
+Om Mishra ran a controlled experiment, same model, same repo, same prompt in Claude Code, changing only the skill framework, and wrote it up:
+
+**["Superpowers vs Agent-Skills: Faster Shipping, Safer Reasoning"](https://www.linkedin.com/pulse/superpowers-vs-agent-skills-faster-shipping-safer-reasoning-om-mishra-dzakf/)** by Om Mishra
+
+Summarized fairly:
+
+- **agent-skills** moved to code faster (~8 min vs ~12) and ran **more validation passes** (7 vs 5, including the full test suite). That broader validation caught a compatibility issue *outside* the immediate feature that the feature-specific tests missed. He gave it the edge on **validation depth** for that task.
+- **Superpowers** invested more **upfront architectural reasoning**, which he still prefers as his daily driver for evolving production systems and exploratory work with no established pattern to follow.
+- Token efficiency was effectively identical; both replanned once.
+
+It is one developer's single-task experiment, not a benchmark, but it is a concrete illustration of the core trade-off: **broad disciplined validation versus heavy upfront reasoning**. His own conclusion is the honest one: pick the tool to the task.
+
+---
+
+## How to decide what to use
+
+The at-a-glance table tells you how they are shaped. This is how to choose in practice.
+
+### Start with the shape of your work
+
+- **A whole feature, front to back?** agent-skills. It is the only one of the three that carries you from spec through security, performance, and launch with a checkpoint at each phase, so nothing quietly skips the review or the pre-flight.
+- **A big, ambiguous chunk you want to hand off and walk away from?** Superpowers. Its pipeline and subagent review are built to run for a long time and hand back a result that has already been reviewed against the spec.
+- **A fast, focused daily loop, especially getting requirements right before code?** Matt Pocock's skills. The grilling loop is the sharpest requirements tool of the three, and the toolkit stays out of your way.
+
+### Then weight what you actually care about
+
+- **Breadth of coverage** (security, performance, CI/CD, observability, launch): agent-skills is the clear pick; the others are inner-loop focused.
+- **Autonomy over a long run**: Superpowers, by design.
+- **Low ceremony on small changes**: Pocock's toolkit is lightest; agent-skills offers a middle gear (a small change can skip straight to `/test` and `/review`); Superpowers is the most process-heavy.
+- **Confidence that the skills themselves work**: agent-skills is the only one with catalog-wide evals in the repo, so a description or routing regression fails CI rather than surfacing as a mysterious "why didn't the skill fire" later.
+- **Requirements interrogation**: Pocock's grilling is the reference implementation; agent-skills' `interview-me` is close in spirit and gaining an opt-in collaborative mode.
+- **Platform spread**: agent-skills and Superpowers both run almost everywhere; Pocock is happiest on Claude Code.
+- **A human gate at each step vs. a hands-off run**: agent-skills checkpoints by default; Superpowers minimizes mid-run check-ins on purpose.
+
+### Concrete scenarios
+
+- *"Ship a new endpoint with auth, tests, and a security pass before merge."* agent-skills: `/spec` to `/ship`, with the security-auditor and test-engineer personas fanning out at the end.
+- *"Refactor a gnarly subsystem overnight and review it in the morning."* Superpowers: hand it the plan, let subagent-driven development and the task reviewer run.
+- *"I have a vague idea and keep letting the agent guess the requirements."* Pocock's `grill-me` (or agent-skills' `interview-me`) to pin down intent before any code.
+- *"Fix one clear bug, test-first."* Any of them; reach for the lightest one you already have installed.
+- *"Standardize how a team of engineers uses agents across a repo."* agent-skills: the phase commands, personas, and shared checklists give a team a common vocabulary, and the evals keep custom skills honest.
+- *"Roll my own skills and know they trigger correctly."* agent-skills, and borrow Superpowers' pressure-testing discipline for the ones that must not be rationalized away.
+
+### Solo vs. team
+
+For a solo developer, taste and momentum win: pick the one whose defaults match how you already work, and the lowest-ceremony option is often the most-used one. For a team, the calculus shifts toward shared structure and guardrails you can enforce: named phases, review personas, checklists, and evals that fail CI are what keep five people (and their agents) converging on the same standard rather than five private workflows. That is the situation agent-skills is built for, though a team can absolutely adopt Superpowers' review discipline or Pocock's grilling loop within it.
+
+### The shared frontier (true of all three)
+
+None of these has solved **durable cross-session memory** well yet: what an agent learned in one session rarely carries cleanly into the next. All three are circling it (learnings files, handoff artifacts, tracker-backed planning maps). If that is your bottleneck, know that you are at the edge of what any of them ships today, and expect to stitch some of it yourself for now.
+
+---
+
+## Combining them
+
+You do not have to choose exclusively, but combine with care. These are Markdown skills, not runtimes, so cherry-picking *individual* skills works well: pull in Pocock's `grill-me`, a Superpowers isolation pattern, or a specific checklist alongside your main setup.
+
+What does not work is running two of them as your **active router at the same time**. Stacked meta-skills fight over command names (`/tdd` defined in two places), compete on routing logic, and pull in different TDD philosophies, so you get unpredictable behavior rather than the best of both. Pick one framework as your primary router, and borrow from the others a la carte.
+
+---
+
+## Sources
+
+- Superpowers: <https://github.com/obra/superpowers>
+- Matt Pocock's skills: <https://github.com/mattpocock/skills>
+- Om Mishra, *Superpowers vs Agent-Skills*: <https://www.linkedin.com/pulse/superpowers-vs-agent-skills-faster-shipping-safer-reasoning-om-mishra-dzakf/>
+
+*Spotted something inaccurate about another project here? Open an issue or PR. We would rather be fair than flattering.*