# harmony-plugin - Doramagic AI Context Pack

> 定位：安装前体验与判断资产。它帮助宿主 AI 有一个好的开始，但不代表已经安装、执行或验证目标项目。

## 充分原则

- **充分原则，不是压缩原则**：AI Context Pack 应该充分到让宿主 AI 在开工前理解项目价值、能力边界、使用入口、风险和证据来源；它可以分层组织，但不以最短摘要为目标。
- **压缩策略**：只压缩噪声和重复内容，不压缩会影响判断和开工质量的上下文。

## 给宿主 AI 的使用方式

你正在读取 Doramagic 为 harmony-plugin 编译的 AI Context Pack。请把它当作开工前上下文：帮助用户理解适合谁、能做什么、如何开始、哪些必须安装后验证、风险在哪里。不要声称你已经安装、运行或执行了目标项目。

## Claim 消费规则

- **事实来源**：Repo Evidence + Claim/Evidence Graph；Human Wiki 只提供显著性、术语和叙事结构。
- **事实最低状态**：`supported`
- `supported`：可以作为项目事实使用，但回答中必须引用 claim_id 和证据路径。
- `weak`：只能作为低置信度线索，必须要求用户继续核实。
- `inferred`：只能用于风险提示或待确认问题，不能包装成项目事实。
- `unverified`：不得作为事实使用，应明确说证据不足。
- `contradicted`：必须展示冲突来源，不得替用户强行选择一个版本。

## 它最适合谁

- **正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**：README 或插件配置提到多个宿主 AI。 证据：`README.md` Claim：`clm_0004` supported 0.86
- **希望把专业流程带进宿主 AI 的用户**：仓库包含 Skill 文档。 证据：`skills/finish-work/SKILL.md`, `skills/harmony-clarify/SKILL.md`, `skills/harmony-conduct/SKILL.md`, `skills/harmony-decompose/SKILL.md` 等 Claim：`clm_0005` supported 0.86

## 它能做什么

- **AI Skill / Agent 指令资产库**（可做安装前预览）：项目包含可被宿主 AI 读取的 Skill 或 Agent 指令文件，可用于把专业流程带入 Claude、Codex、Cursor 等宿主。 证据：`skills/finish-work/SKILL.md`, `skills/harmony-clarify/SKILL.md`, `skills/harmony-conduct/SKILL.md`, `skills/harmony-decompose/SKILL.md` 等 Claim：`clm_0001` supported 0.86
- **多宿主安装与分发**（需要安装后验证）：项目包含插件或 marketplace 配置，说明它面向一个或多个 AI 宿主的安装和分发。 证据：`.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json` Claim：`clm_0002` supported 0.86
- **命令行启动或安装流程**（需要安装后验证）：项目文档中存在可执行命令，真实使用需要在本地或宿主环境中运行这些命令。 证据：`README.md` Claim：`clm_0003` supported 0.86

## 怎么开始

- `npm install -g @harmony-ad/harmony` 证据：`README.md` Claim：`clm_0006` supported 0.86
- `npx @harmony-ad/harmony --help` 证据：`README.md` Claim：`clm_0007` supported 0.86
- `/plugin marketplace add ycomplex/harmony-plugin` 证据：`README.md` Claim：`clm_0008` supported 0.86
- `/plugin install harmony-plugin@ycomplex` 证据：`README.md` Claim：`clm_0009` supported 0.86
- `npm install        # Install dependencies` 证据：`README.md` Claim：`clm_0010` supported 0.86
- `npx tsc --noEmit   # Type-check without emitting` 证据：`README.md` Claim：`clm_0011` supported 0.86

## 继续前判断卡

- **当前建议**：需要管理员/安全审批
- **为什么**：继续前可能涉及密钥、账号、外部服务或敏感上下文，建议先经过管理员或安全审批。

### 30 秒判断

- **现在怎么做**：需要管理员/安全审批
- **最小安全下一步**：先跑 Prompt Preview；若涉及凭证或企业环境，先审批再试装
- **先别相信**：研究结论、引用和实验结果不能在安装前相信。
- **继续会触碰**：研究判断、命令执行、宿主 AI 配置

### 现在可以相信

- **适合人群线索：正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`README.md` Claim：`clm_0004` supported 0.86
- **适合人群线索：希望把专业流程带进宿主 AI 的用户**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`skills/finish-work/SKILL.md`, `skills/harmony-clarify/SKILL.md`, `skills/harmony-conduct/SKILL.md`, `skills/harmony-decompose/SKILL.md` 等 Claim：`clm_0005` supported 0.86
- **能力存在：AI Skill / Agent 指令资产库**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`skills/finish-work/SKILL.md`, `skills/harmony-clarify/SKILL.md`, `skills/harmony-conduct/SKILL.md`, `skills/harmony-decompose/SKILL.md` 等 Claim：`clm_0001` supported 0.86
- **能力存在：多宿主安装与分发**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json` Claim：`clm_0002` supported 0.86
- **能力存在：命令行启动或安装流程**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`README.md` Claim：`clm_0003` supported 0.86
- **存在 Quick Start / 安装命令线索**（supported）：可以相信项目文档出现过启动或安装入口；不要因此直接在主力环境运行。 证据：`README.md` Claim：`clm_0006` supported 0.86

### 现在还不能相信

- **研究结论、引用和实验结果不能在安装前相信。**（unverified）：研究 Skill 可以组织问题和路径，但不能替代真实资料检索、论文核验和实验复现。
- **是否适合你的具体研究领域不能直接相信。**（unverified）：Skill 覆盖很多研究主题，不代表对你的领域、资料要求和可信度标准足够。
- **真实输出质量不能在安装前相信。**（unverified）：Prompt Preview 只能展示引导方式，不能证明真实项目中的结果质量。
- **宿主 AI 版本兼容性不能在安装前相信。**（unverified）：Claude、Cursor、Codex、Gemini 等宿主加载规则和版本差异必须在真实环境验证。
- **不会污染现有宿主 AI 行为，不能直接相信。**（inferred）：Skill、plugin、AGENTS/CLAUDE/GEMINI 指令可能改变宿主 AI 的默认行为。 证据：`.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `CLAUDE.md`, `skills/finish-work/SKILL.md` 等
- **可安全回滚不能默认相信。**（unverified）：除非项目明确提供卸载和恢复说明，否则必须先在隔离环境验证。
- **真实安装后是否与用户当前宿主 AI 版本兼容？**（unverified）：兼容性只能通过实际宿主环境验证。 证据：`.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`
- **项目输出质量是否满足用户具体任务？**（unverified）：安装前预览只能展示流程和边界，不能替代真实评测。

### 继续会触碰什么

- **研究判断**：问题拆解、资料路径、实验路径、结论结构和可信度判断。 原因：研究型 Skill 可能让输出看起来更专业，但不能替代真实证据核验。
- **命令执行**：包管理器、网络下载、本地插件目录、项目配置或用户主目录。 原因：运行第一条命令就可能产生环境改动；必须先判断是否值得跑。 证据：`README.md`
- **宿主 AI 配置**：Claude/Codex/Cursor/Gemini/OpenCode 等宿主的 plugin、Skill 或规则加载配置。 原因：宿主配置会改变 AI 后续工作方式，可能和用户已有规则冲突。 证据：`.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `CLAUDE.md`, `skills/finish-work/SKILL.md` 等
- **本地环境或项目文件**：安装结果、插件缓存、项目配置或本地依赖目录。 原因：安装前无法证明写入范围和回滚方式，需要隔离验证。 证据：`.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json`, `README.md`
- **环境变量 / API Key**：项目入口文档明确出现 API key、token、secret 或账号凭证配置。 原因：如果真实安装需要凭证，应先使用测试凭证并经过权限/合规判断。 证据：`CLAUDE.md`, `README.md`, `commands/harmony-setup.md`
- **宿主 AI 上下文**：AI Context Pack、Prompt Preview、Skill 路由、风险规则和项目事实。 原因：导入上下文会影响宿主 AI 后续判断，必须避免把未验证项包装成事实。

### 最小安全下一步

- **先跑 Prompt Preview**：先验证它能否正确界定研究问题和证据边界，不要先相信研究输出。（适用：任何项目都适用，尤其是输出质量未知时。）
- **只在隔离目录或测试账号试装**：避免安装命令污染主力宿主 AI、真实项目或用户主目录。（适用：存在命令执行、插件配置或本地写入线索时。）
- **先备份宿主 AI 配置**：Skill、plugin、规则文件可能改变 Claude/Cursor/Codex 的默认行为。（适用：存在插件 manifest、Skill 或宿主规则入口时。）
- **不要使用真实生产凭证**：环境变量/API key 一旦进入宿主或工具链，可能产生账号和合规风险。（适用：出现 API、TOKEN、KEY、SECRET 等环境线索时。）
- **安装后只验证一个最小任务**：先验证加载、兼容、输出质量和回滚，再决定是否深用。（适用：准备从试用进入真实工作流时。）

### 退出方式

- **保留安装前状态**：记录原始宿主配置和项目状态，后续才能判断是否可恢复。
- **准备移除宿主 plugin / Skill / 规则入口**：如果试装后行为异常，可以把宿主 AI 恢复到试装前状态。
- **保留资料和结论核验清单**：如果后续发现引用或实验路径不可靠，可以回到证据边界阶段重新校验。
- **记录安装命令和写入路径**：没有明确卸载说明时，至少要知道哪些目录或配置需要手动清理。
- **准备撤销测试 API key 或 token**：测试凭证泄露或误用时，可以快速止损。
- **如果没有回滚路径，不进入主力环境**：不可回滚是继续前阻断项，不应靠信任或运气继续。

## 哪些只能预览

- 解释项目适合谁和能做什么
- 基于项目文档演示典型对话流程
- 帮助用户判断是否值得安装或继续研究

## 哪些必须安装后验证

- 真实安装 Skill、插件或 CLI
- 执行脚本、修改本地文件或访问外部服务
- 验证真实输出质量、性能和兼容性

## 边界与风险判断卡

- **把安装前预览误认为真实运行**：用户可能高估项目已经完成的配置、权限和兼容性验证。 处理方式：明确区分 prompt_preview_can_do 与 runtime_required。 Claim：`clm_0012` inferred 0.45
- **宿主 AI 插件或 Skill 规则冲突**：新规则可能改变用户现有宿主 AI 的工作方式。 处理方式：安装前先检查插件 manifest 和 Skill 文件，必要时隔离测试。 证据：`.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json` Claim：`clm_0013` supported 0.86
- **命令执行会修改本地环境**：安装命令可能写入用户主目录、宿主插件目录或项目配置。 处理方式：先在隔离环境或测试账号中运行。 证据：`README.md` Claim：`clm_0014` supported 0.86
- **待确认**：真实安装后是否与用户当前宿主 AI 版本兼容？。原因：兼容性只能通过实际宿主环境验证。
- **待确认**：项目输出质量是否满足用户具体任务？。原因：安装前预览只能展示流程和边界，不能替代真实评测。
- **待确认**：安装命令是否需要网络、权限或全局写入？。原因：这影响企业环境和个人环境的安装风险。

## 开工前工作上下文

### 加载顺序

- 先读取 how_to_use.host_ai_instruction，建立安装前判断资产的边界。
- 读取 claim_graph_summary，确认事实来自 Claim/Evidence Graph，而不是 Human Wiki 叙事。
- 再读取 intended_users、capabilities 和 quick_start_candidates，判断用户是否匹配。
- 需要执行具体任务时，优先查 role_skill_index，再查 evidence_index。
- 遇到真实安装、文件修改、网络访问、性能或兼容性问题时，转入 risk_card 和 boundaries.runtime_required。

### 任务路由

- **AI Skill / Agent 指令资产库**：先基于 role_skill_index / evidence_index 帮用户挑选可用角色、Skill 或工作流。 边界：可做安装前 Prompt 体验。 证据：`skills/finish-work/SKILL.md`, `skills/harmony-clarify/SKILL.md`, `skills/harmony-conduct/SKILL.md`, `skills/harmony-decompose/SKILL.md` 等 Claim：`clm_0001` supported 0.86
- **多宿主安装与分发**：先说明这是安装后验证能力，再给出安装前检查清单。 边界：必须真实安装或运行后验证。 证据：`.claude-plugin/marketplace.json`, `.claude-plugin/plugin.json` Claim：`clm_0002` supported 0.86
- **命令行启动或安装流程**：先说明这是安装后验证能力，再给出安装前检查清单。 边界：必须真实安装或运行后验证。 证据：`README.md` Claim：`clm_0003` supported 0.86

### 上下文规模

- 文件总数：122
- 重要文件覆盖：40/122
- 证据索引条目：63
- 角色 / Skill 条目：12

### 证据不足时的处理

- **missing_evidence**：说明证据不足，要求用户提供目标文件、README 段落或安装后验证记录；不要补全事实。
- **out_of_scope_request**：说明该任务超出当前 AI Context Pack 证据范围，并建议用户先查看 Human Manual 或真实安装后验证。
- **runtime_request**：给出安装前检查清单和命令来源，但不要替用户执行命令或声称已执行。
- **source_conflict**：同时展示冲突来源，标记为待核实，不要强行选择一个版本。

## Prompt Recipes

### 适配判断

- 目标：判断这个项目是否适合用户当前任务。
- 预期输出：适配结论、关键理由、证据引用、安装前可预览内容、必须安装后验证内容、下一步建议。

```text
请基于 harmony-plugin 的 AI Context Pack，先问我 3 个必要问题，然后判断它是否适合我的任务。回答必须包含：适合谁、能做什么、不能做什么、是否值得安装、证据来自哪里。所有项目事实必须引用 evidence_refs、source_paths 或 claim_id。
```

### 安装前体验

- 目标：让用户在安装前感受核心工作流，同时避免把预览包装成真实能力或营销承诺。
- 预期输出：一段带边界标签的体验剧本、安装后验证清单和谨慎建议；不含真实运行承诺或强营销表述。

```text
请把 harmony-plugin 当作安装前体验资产，而不是已安装工具或真实运行环境。

请严格输出四段：
1. 先问我 3 个必要问题。
2. 给出一段“体验剧本”：用 [安装前可预览]、[必须安装后验证]、[证据不足] 三种标签展示它可能如何引导工作流。
3. 给出安装后验证清单：列出哪些能力只有真实安装、真实宿主加载、真实项目运行后才能确认。
4. 给出谨慎建议：只能说“值得继续研究/试装”“先补充信息后再判断”或“不建议继续”，不得替项目背书。

硬性边界：
- 不要声称已经安装、运行、执行测试、修改文件或产生真实结果。
- 不要写“自动适配”“确保通过”“完美适配”“强烈建议安装”等承诺性表达。
- 如果描述安装后的工作方式，必须使用“如果安装成功且宿主正确加载 Skill，它可能会……”这种条件句。
- 体验剧本只能写成“示例台词/假设流程”：使用“可能会询问/可能会建议/可能会展示”，不要写“已写入、已生成、已通过、正在运行、正在生成”。
- Prompt Preview 不负责给安装命令；如用户准备试装，只能提示先阅读 Quick Start 和 Risk Card，并在隔离环境验证。
- 所有项目事实必须来自 supported claim、evidence_refs 或 source_paths；inferred/unverified 只能作风险或待确认项。

```

### 角色 / Skill 选择

- 目标：从项目里的角色或 Skill 中挑选最匹配的资产。
- 预期输出：候选角色或 Skill 列表，每项包含适用场景、证据路径、风险边界和是否需要安装后验证。

```text
请读取 role_skill_index，根据我的目标任务推荐 3-5 个最相关的角色或 Skill。每个推荐都要说明适用场景、可能输出、风险边界和 evidence_refs。
```

### 风险预检

- 目标：安装或引入前识别环境、权限、规则冲突和质量风险。
- 预期输出：环境、权限、依赖、许可、宿主冲突、质量风险和未知项的检查清单。

```text
请基于 risk_card、boundaries 和 quick_start_candidates，给我一份安装前风险预检清单。不要替我执行命令，只说明我应该检查什么、为什么检查、失败会有什么影响。
```

### 宿主 AI 开工指令

- 目标：把项目上下文转成一次对话开始前的宿主 AI 指令。
- 预期输出：一段边界明确、证据引用明确、适合复制给宿主 AI 的开工前指令。

```text
请基于 harmony-plugin 的 AI Context Pack，生成一段我可以粘贴给宿主 AI 的开工前指令。这段指令必须遵守 not_runtime=true，不能声称项目已经安装、运行或产生真实结果。
```

## 角色 / Skill 索引

- 共索引 12 个角色 / Skill / 项目文档条目。

- **finish-work**（skill）：Use when the user wants to finish, complete, wrap up, land, or merge their current work. Triggers on phrases like "finish", "done", "wrap up", "land this", "merge", "ship it", or "we're done". This is the exit point for ALL development work in this project — it handles the full merge-and-cleanup sequence. In opinionated-mode projects it also drives the releasing + verifying activities; in manual-mode projects it beh… 激活提示：当用户任务与“finish-work”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/finish-work/SKILL.md`
- **harmony-clarify**（skill）：Clarify a ticket's intent into a specification Idea → Clarified . Triggers on "clarify B-123", "what does this ticket mean", "harmony clarify", or picking up an Idea-state ticket. Dialogues with the human, queries domain knowledge first, drafts a clarification, and files it as a brief for accept/edit/defer. 激活提示：当用户任务与“harmony-clarify”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/harmony-clarify/SKILL.md`
- **harmony-conduct**（skill）：Drive one ticket through the gate sequence end to end. Default = pause at every gate for the human's decision controlled . Optional per-run delegation — --pause-at auto-advance up to a gate , --unattended auto-advance to the hard floor , or --escalate auto-advance, but surface any gate genuinely worth a human opinion . A non-discretionary risk-class FLOOR auth / data-migration / irreversible-destructive / shared-cor… 激活提示：当用户任务与“harmony-conduct”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/harmony-conduct/SKILL.md`
- **harmony-decompose**（skill）：Decompose a clarified ticket into a child hierarchy Clarified → Decomposed . Triggers on "decompose B-123", "break this down", "harmony decompose", or picking up a Clarified ticket. Applies the manageability rule; even "no decomposition needed" is an explicit decision. Files a proposal brief; on accept, creates children at Idea state. 激活提示：当用户任务与“harmony-decompose”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/harmony-decompose/SKILL.md`
- **harmony-design-decide**（skill）：Make a design decision on one sub-track Decomposed → Designed . Triggers on "design B-123", "harmony design-decide B-123 --track ux-ui", "decide the technical approach". Runs one of three sub-tracks — Product Design, Technical Design, UX/UI Design — querying domain knowledge, drafting a typed decision, and filing it as a brief. State advances to Designed only when all required sub-tracks are accepted. 激活提示：当用户任务与“harmony-design-decide”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/harmony-design-decide/SKILL.md`
- **harmony-next**（skill）：Pick up the highest-priority thing awaiting me and start the right activity. Triggers on "what's next", "harmony next", "pick up the next thing", "do the next item". Reads the queue, takes the top item, renders its brief, and either resolves it accept/defer/expand/related or hands off to the activity skill that owns it. 激活提示：当用户任务与“harmony-next”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/harmony-next/SKILL.md`
- **harmony-queue**（skill）：Show what's awaiting ME — the opinionated-mode pull queue. Triggers on "my queue", "what's awaiting me", "what should I look at", "harmony queue", "what needs my input". Read-only conductor view that lists every ticket where the ball is in the human's court, with its one-line decision and brief reason. 激活提示：当用户任务与“harmony-queue”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/harmony-queue/SKILL.md`
- **harmony-research**（skill）：Fill a load-bearing knowledge gap via the v1 human-relayed research hand-off. Triggers on "research X", "harmony research", "I don't know enough about Y", or when a gate skill hits a load-bearing gap. Emits concrete research prompts for the human to run in their tool of choice, then ingests the pasted result as Asserted knowledge never auto-Accepted . 激活提示：当用户任务与“harmony-research”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/harmony-research/SKILL.md`
- **harmony-revise-scope**（skill）：Draft a "revise scope / back up" reconciliation for a ticket whose downstream gate revealed the upstream spec was scoped too narrowly — back the run up to an earlier discovery gate clarify/decompose/design and re-run it against the real scope. Triggers on "harmony revise-scope B-123", "back up B-123 to re-clarify", "the scope grew — re-decompose B-123", a revise-scope /"back up" verb at a conductor gate pause, or be… 激活提示：当用户任务与“harmony-revise-scope”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/harmony-revise-scope/SKILL.md`
- **harmony-stale-patch**（skill）：Draft a reconciliation patch for a ticket gone Stale because a knowledge decision it depends on was superseded state-machine §6.4 . Triggers on "patch the stale ticket", "harmony stale-patch B-123", "reconcile B-123 against the superseding decision", or being delegated a Stale item by harmony-next. Reads the superseded decision + its successor, drafts a concrete proposed patch knowledge reconciliation and/or a state… 激活提示：当用户任务与“harmony-stale-patch”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/harmony-stale-patch/SKILL.md`
- **harmony-visual-handoff**（skill）：Run a UX/UI design decision through a generated, manipulable surface + an iterate loop B-328 . Triggers on "visual hand-off", "generate a mockup for this decision", "show me the UX options", and is delegated to by harmony-design-decide's --track ux-ui. Routes glanceable decisions to a parametric preview and flows to a walk-through + storyboard; reserves a design tool Figma for the irreducibly-generative visual resid… 激活提示：当用户任务与“harmony-visual-handoff”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/harmony-visual-handoff/SKILL.md`
- **start-work**（skill）：Use when the user wants to start working on a task, feature, or bug fix. Triggers on phrases like "work on", "start", "pick up", "implement", "fix", or any mention of a Harmony task ID e.g., B-123 . Also use when the user says "let's do X" or describes work they want to begin. This is the entry point for ALL new development work in this project. In opinionated-mode projects it drives the planning + building activiti… 激活提示：当用户任务与“start-work”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/start-work/SKILL.md`

## 证据索引

- 共索引 63 条证据。

- **Harmony**（documentation）：Tools for Harmony https://github.com/ycomplex/harmony-web project management — a CLI for your terminal and an MCP server plugin for Claude Code https://claude.ai/claude-code . 证据：`README.md`
- **Package**（package_manifest）：{ "name": "@harmony-ad/harmony", "version": "0.1.1", "description": "Harmony CLI and MCP server for project management", "type": "module", "bin": { "harmony": "./dist/bin/harmony.js" }, "main": "./dist/index.js", "files": "dist/" , "publishConfig": { "access": "public" }, "scripts": { "build": "esbuild src/index.ts src/bin/harmony.ts --bundle --platform=node --format=esm --outdir=dist --outbase=src --target=node20 --banner:js=\"import{createRequire as cr}from'node:module';const require= cr import.meta.url ;\"", "postbuild": "node scripts/normalize-dist-comments.mjs", "typecheck": "tsc --noEmit", "verify:dist": "rm -rf dist && npm run build && git diff --exit-code dist", "dev": "npm run buil… 证据：`package.json`
- **Finish Work**（skill_instruction）：Safely land completed work: verify readiness, rebase, squash merge, update main, and clean up the worktree and branch. 证据：`skills/finish-work/SKILL.md`
- **Harmony Clarify**（skill_instruction）：Implements the clarifying activity state-machine §4 : Idea → Clarified, producing a clarification knowledge entry. The skill is the agent agent-model §1 : it reads state, drafts, files a brief, and records the result back through MCP. It never edits code discovery role . 证据：`skills/harmony-clarify/SKILL.md`
- **Harmony Conduct conductor — B-458 phase 2a controlled core + B-489 phase 2b autonomy selector + B-485 browser auto-pick…**（skill_instruction）：Harmony Conduct conductor — B-458 phase 2a controlled core + B-489 phase 2b autonomy selector + B-485 browser auto-pickup + B-493 phase 2c risk-class floor & --escalate + B-500 auto-watch by default + B-506 Decomposed split-umbrella branch + B-519 revise-scope / back-up + B-516 floor scoping: pause only in --escalate, release-brief signal otherwise 证据：`skills/harmony-conduct/SKILL.md`
- **Harmony Decompose**（skill_instruction）：Implements the decomposing activity state-machine §4, §8 : Clarified → Decomposed. Decomposition is non-skippable — "no decomposition needed" must be an explicit human decision, not a silent skip. 证据：`skills/harmony-decompose/SKILL.md`
- **Harmony Design-Decide**（skill_instruction）：Implements one sub-track of the designing activity state-machine §5 : Decomposed → Designed. "Design" is the umbrella for three sub-tracks — always name the sub-track explicitly. The skill must NOT write code discovery role : it produces design decisions , not implementations. 证据：`skills/harmony-design-decide/SKILL.md`
- **Harmony Next**（skill_instruction）：Pull the top of the queue and act on it agent-model §5: pick up the highest-priority next thing and start the appropriate activity . One ticket can be named explicitly /harmony-plugin:harmony-next B-301 or left blank to take the highest-priority awaiting item. 证据：`skills/harmony-next/SKILL.md`
- **Harmony Queue**（skill_instruction）：The pull-based conductor view agent-model §5 : what is awaiting you, prioritised, with briefs ready. This is read-only — it never advances state. To act on an item, run /harmony-plugin:harmony-next picks the top item or the activity skill the item points to. 证据：`skills/harmony-queue/SKILL.md`
- **Harmony Research**（skill_instruction）：Implements the cross-cutting researching activity state-machine §4 item 13; agent-model §7.2; B-329 . It does not advance ticket state — it acquires knowledge to unblock a gate clarifying / designing / planning when a load-bearing gap is present. v1 is a human relay: confidently-wrong-from-a-bad-source is worse than "I don't know," so researched knowledge enters Asserted with a review by and is promoted to Accepted only by a human/check — never auto-Accepted. 证据：`skills/harmony-research/SKILL.md`
- **Harmony Revise-Scope B-519, B-529**（skill_instruction）：The mid-run "revise scope / back up" flow for the opinionated-mode conductor. When a downstream discovery gate's discussion reveals the upstream spec was scoped too narrowly, the run must back up to an earlier discovery gate and re-run it natively against the real scope. This skill is the agent that drafts a concrete back-up proposal and files it as a revise-scope-review brief so a human can accept execute the back-up or reject no-op . It is the stale-patch "agent proposes, human disposes" pattern applied to the discovery phase sibling to harmony-stale-patch , but a different trigger, a different brief reason, and entry points stale-patch lacks. 证据：`skills/harmony-revise-scope/SKILL.md`
- **Harmony Stale-Patch**（skill_instruction）：Implements the §6.4 agent patch step of the Stale loop. When a knowledge decision is superseded supersede decision , P2's trigger flags every dependent ticket stale=true and writes stale ref = { type:'decision', id: , superseded by: } P2 A8 — but the flag alone just tells the human "this is stale." This skill is the agent that drafts a concrete proposed patch and files it as a stale-patch-review brief so the human can accept apply or reject knowing-divergence . It never edits code discovery role : it produces a proposed reconciliation , not an implementation. 证据：`skills/harmony-stale-patch/SKILL.md`
- **Harmony Visual Hand-off**（skill_instruction）：Owns the UX/UI sub-track of the designing activity: hand a UX/UI structural decision to a human as a generated, manipulable surface + an iterate loop — the B-328-validated default — then file the framed decision through the same gate machinery the other sub-tracks use. 证据：`skills/harmony-visual-handoff/SKILL.md`
- **Start Work**（skill_instruction）：Set up everything needed to begin a piece of work: find or create the Harmony task, move it to In Progress, create an isolated worktree, and recommend an execution route Execute, Plan, or Explore based on task complexity and uncertainty. 证据：`skills/start-work/SKILL.md`
- **Marketplace**（structured_config）：{ "name": "ycomplex", "owner": { "name": "ycomplex" }, "plugins": { "name": "harmony-plugin", "source": "./", "description": "Harmony project management integration for Claude Code — MCP tools and workflow skills" } } 证据：`.claude-plugin/marketplace.json`
- **Plugin**（structured_config）：{ "name": "harmony-plugin", "version": "0.14.18", "description": "Harmony project management integration for Claude Code — MCP tools and workflow skills", "author": { "name": "ycomplex" }, "repository": "https://github.com/ycomplex/harmony-plugin", "license": "MIT", "keywords": "harmony", "project-management", "workflow", "mcp" } 证据：`.claude-plugin/plugin.json`
- **Harmony Plugin for Claude Code**（documentation）：This is the Harmony plugin for Claude Code — an MCP server, CLI, and workflow skills for Harmony project management. 证据：`CLAUDE.md`
- **License**（source_file）：Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: 证据：`LICENSE`
- **Harmony Plugin Setup**（documentation）：Configure the Harmony plugin for the current project. 证据：`commands/harmony-setup.md`
- **Harmony CLI Implementation Plan**（documentation）：For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development recommended or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox - syntax for tracking. 证据：`docs/superpowers/plans/2026-04-03-harmony-cli.md`
- **Fix Plugin Install Build — Implementation Plan**（documentation）：Fix Plugin Install Build — Implementation Plan 证据：`docs/superpowers/plans/2026-04-14-plugin-install-build.md`
- **Knowledge Promote/Create Re-embed Fix B-401 Implementation Plan**（documentation）：Knowledge Promote/Create Re-embed Fix B-401 Implementation Plan 证据：`docs/superpowers/plans/2026-06-08-knowledge-promote-reembed.md`
- **update knowledge entry / create knowledge entry status-vocab fix B-415 Implementation Plan**（documentation）：update knowledge entry / create knowledge entry status-vocab fix B-415 Implementation Plan 证据：`docs/superpowers/plans/2026-06-08-update-knowledge-status-vocab.md`
- **.Mcp**（structured_config）：{ "harmony": { "command": "node", "args": "${CLAUDE PLUGIN ROOT}/dist/index.js" } } 证据：`.mcp.json`
- **Hooks**（structured_config）：{ "hooks": { "SessionStart": { "matcher": ". ", "hooks": { "type": "command", "command": "if ! -f \"${CLAUDE PLUGIN ROOT}/dist/index.js\" ; then cd \"${CLAUDE PLUGIN ROOT}\" && npm install --silent && npm run build &2; fi; echo '{}'", "timeout": 180 } } } } 证据：`hooks/hooks.json`
- **Auth**（source_file）：interface TokenExchangeResult { access token: string; expires in: number; project id: string; } export class HarmonyAuth ⋮---- constructor apiToken: string async getAccessToken : Promise getProjectId : string getUserId : string private async exchange : Promise 证据：`src/auth.ts`
- **Index**（source_file）：import { Server } from '@modelcontextprotocol/sdk/server/index.js'; import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js'; import { CallToolRequestSchema, ListToolsRequestSchema } from '@modelcontextprotocol/sdk/types.js'; import { HarmonyAuth } from './auth.js'; import { createAuthenticatedClient } from './supabase.js'; import { registerTools, handleToolCall } from './tools/index.js'; ⋮---- async function main 证据：`src/index.ts`
- **Vitest.Config**（source_file）：import { defineConfig } from "vitest/config"; 证据：`vitest.config.ts`
- **Auth**（source_file）：import type { SupabaseClient } from '@supabase/supabase-js'; import { HarmonyAuth } from '../auth.js'; import { createAuthenticatedClient } from '../supabase.js'; import { getActiveProject, ProjectConfig } from './config.js'; export interface AuthenticatedContext { client: SupabaseClient; projectId: string; userId: string; } export async function getAuthenticatedContext projectConfig?: ProjectConfig : Promise 证据：`src/cli/auth.ts`
- **Acceptance Criteria**（source_file）：import { Command } from 'commander'; import { listAcceptanceCriteria, manageAcceptanceCriteria } from '../../tools/acceptance-criteria.js'; import { runCommand } from '../run-command.js'; import { formatTable } from '../formatter.js'; export function registerAcceptanceCriteriaCommands program: Command : void 证据：`src/cli/commands/acceptance-criteria.ts`
- **Activity**（source_file）：import { Command } from 'commander'; import { listActivity } from '../../tools/activity.js'; import { runCommand } from '../run-command.js'; import { formatTable, formatDate } from '../formatter.js'; function buildActivitySummary item: any : string ⋮---- // event ⋮---- export function registerActivityCommand program: Command : void 证据：`src/cli/commands/activity.ts`
- **Auth**（source_file）：import { Command } from 'commander'; import chalk from 'chalk'; import { HarmonyAuth } from '../../auth.js'; import { createAuthenticatedClient } from '../../supabase.js'; import { getProject } from '../../tools/project.js'; import { addProject, removeProject, listProjects } from '../config.js'; import { formatTable } from '../formatter.js'; export function registerAuthCommands program: Command : void 证据：`src/cli/commands/auth.ts`
- **Comments**（source_file）：import { Command } from 'commander'; import { listComments, addComment } from '../../tools/comments.js'; import { runCommand } from '../run-command.js'; import { formatTable, formatDate } from '../formatter.js'; export function registerCommentCommands program: Command : void 证据：`src/cli/commands/comments.ts`
- **Cycles**（source_file）：import { Command } from 'commander'; import { listCycles, createCycle, updateCycle } from '../../tools/cycles.js'; import { runCommand } from '../run-command.js'; import { formatTable, formatDetail } from '../formatter.js'; export function registerCycleCommands program: Command : void 证据：`src/cli/commands/cycles.ts`
- **Dependencies**（source_file）：import { Command } from 'commander'; import { listDependencies, manageDependencies } from '../../tools/dependencies.js'; import { runCommand } from '../run-command.js'; import { formatTable } from '../formatter.js'; export function registerDependencyCommands program: Command : void 证据：`src/cli/commands/dependencies.ts`
- **Knowledge**（source_file）：import { Command } from 'commander'; import { queryKnowledge, getKnowledgeEntry, createKnowledgeEntry, updateKnowledgeEntry, supersedeKnowledgeEntry, } from '../../tools/knowledge.js'; import { runCommand } from '../run-command.js'; import { formatTable, formatDetail, formatDate } from '../formatter.js'; export function registerKnowledgeCommands program: Command : void 证据：`src/cli/commands/knowledge.ts`
- **Milestones**（source_file）：import { Command } from 'commander'; import { listMilestones, createMilestone, updateMilestone, shipMilestone } from '../../tools/milestones.js'; import { runCommand } from '../run-command.js'; import { formatTable, formatDetail } from '../formatter.js'; export function registerMilestoneCommands program: Command : void 证据：`src/cli/commands/milestones.ts`
- **Project**（source_file）：import { Command } from 'commander'; import chalk from 'chalk'; import { getProject } from '../../tools/project.js'; import { switchProject } from '../config.js'; import { runCommand } from '../run-command.js'; import { formatDetail } from '../formatter.js'; export function registerProjectCommands program: Command : void 证据：`src/cli/commands/project.ts`
- **Subtasks**（source_file）：import { Command } from 'commander'; import { listSubtasks, listParent, manageSubtasks } from '../../tools/decomposition.js'; import { updateTask } from '../../tools/tasks.js'; import { runCommand } from '../run-command.js'; import { formatTable } from '../formatter.js'; export function registerSubtaskCommands program: Command : void 证据：`src/cli/commands/subtasks.ts`
- **Tasks**（source_file）：import { Command } from 'commander'; import { listTasks, getTask, createTask, updateTask } from '../../tools/tasks.js'; import { runCommand } from '../run-command.js'; import { formatTable, formatDetail, formatPriority, formatStatus, formatDate } from '../formatter.js'; export function registerTaskCommands program: Command : void 证据：`src/cli/commands/tasks.ts`
- **Config.Test**（source_file）：import { describe, it, expect, vi, beforeEach, afterEach } from 'vitest'; import fs from 'node:fs'; import path from 'node:path'; import os from 'node:os'; import { loadConfig, saveConfig, getActiveProject, addProject, removeProject, switchProject, listProjects, } from './config.js'; 证据：`src/cli/config.test.ts`
- **Config**（source_file）：import fs from 'node:fs'; import path from 'node:path'; import os from 'node:os'; export interface ProjectConfig { name: string; token: string; supabaseUrl?: string; supabaseAnonKey?: string; } export interface HarmonyConfig { activeProject: string null; projects: Record ; } function getConfigDir : string function getConfigFile : string export function loadConfig : HarmonyConfig export function saveConfig config: HarmonyConfig : void export function addProject name: string, token: string, opts?: { supabaseUrl?: string; supabaseAnonKey?: string }, : void export function removeProject name: string : void export function switchProject name: string : void export function getActiveProject : Proj… 证据：`src/cli/config.ts`
- **Formatter.Test**（source_file）：import { describe, it, expect } from 'vitest'; import { formatTable, formatDetail, formatOutput } from './formatter.js'; 证据：`src/cli/formatter.test.ts`
- **Index**（source_file）：import { createRequire } from 'node:module'; import { Command } from 'commander'; import { registerAuthCommands } from './commands/auth.js'; ⋮---- import { registerTaskCommands } from './commands/tasks.js'; import { registerQueryCommand } from './commands/query.js'; import { registerCommentCommands } from './commands/comments.js'; import { registerProjectCommands } from './commands/project.js'; import { registerMemberCommands } from './commands/members.js'; import { registerActivityCommand } from './commands/activity.js'; import { registerEpicCommands } from './commands/epics.js'; import { registerLabelCommands } from './commands/labels.js'; import { registerMilestoneCommands } from './comm… 证据：`src/cli/index.ts`
- **Acceptance Criteria**（source_file）：import type { SupabaseClient } from '@supabase/supabase-js'; import { resolveTaskId } from './resolve-task-id.js'; ⋮---- export async function listAcceptanceCriteria client: SupabaseClient, projectId: string, args: { task id: string }, ⋮---- export async function manageAcceptanceCriteria client: SupabaseClient, projectId: string, userId: string, args: { task id: string; add?: { content: string; checked?: boolean } ; update?: { id: string; content?: string; checked?: boolean } ; delete?: string ; }, 证据：`src/tools/acceptance-criteria.ts`
- **Activity**（source_file）：import type { SupabaseClient } from '@supabase/supabase-js'; import { resolveTaskId } from './resolve-task-id.js'; ⋮---- export async function listActivity client: SupabaseClient, projectId: string, args: { task id: string }, 证据：`src/tools/activity.ts`
- **Comments**（source_file）：import type { SupabaseClient } from '@supabase/supabase-js'; import { resolveTaskId } from './resolve-task-id.js'; ⋮---- export async function listComments client: SupabaseClient, projectId: string, args: { task id: string }, ⋮---- export async function addComment client: SupabaseClient, projectId: string, userId: string, args: { task id: string; content: string }, 证据：`src/tools/comments.ts`
- **Cycles**（source_file）：import type { SupabaseClient } from '@supabase/supabase-js'; ⋮---- export async function listCycles client: SupabaseClient, projectId: string, args: ⋮---- export async function createCycle client: SupabaseClient, projectId: string, userId: string, args: { start date: string; name?: string } ⋮---- export async function updateCycle client: SupabaseClient, projectId: string, args: { cycle id: string; name?: string; end date?: string } function addDays dateStr: string, days: number : string 证据：`src/tools/cycles.ts`
- **Dependencies**（source_file）：import type { SupabaseClient } from '@supabase/supabase-js'; import { resolveTaskId, resolveTaskIds } from './resolve-task-id.js'; ⋮---- export async function listDependencies client: SupabaseClient, projectId: string, args: { task id: string }, ⋮---- export async function manageDependencies client: SupabaseClient, projectId: string, userId: string, args: { task id: string; add?: string ; remove?: string }, 证据：`src/tools/dependencies.ts`
- **Index**（source_file）：import type { SupabaseClient } from '@supabase/supabase-js'; import { getProjectTool, getProject } from './project.js'; import { listEpicsTool, listEpics, createEpicTool, createEpic, updateEpicTool, updateEpic } from './epics.js'; import { listTasksTool, listTasks, getTaskTool, getTask, createTaskTool, createTask, updateTaskTool, updateTask, bulkCreateTasksTool, bulkCreateTasks, } from './tasks.js'; import { listLabels, createLabel, listLabelsTool, createLabelTool } from './labels.js'; import { listChecklistItemsTool, listChecklistItems, manageChecklistItemsTool, manageChecklistItems } from './checklist-items.js'; import { queryTasksTool, queryTasks } from './query-tasks.js'; import { listC… 证据：`src/tools/index.ts`
- **Knowledge**（source_file）：import type { SupabaseClient } from '@supabase/supabase-js'; export interface KnowledgeEntrySummary { id: string; title: string; type: string; status: string; domain: string ; tags: string ; project id: string null; updated at: string; } export interface KnowledgeEntryFull { id: string; workspace id: string; project id: string null; title: string; content: string; type: string; status: string; superseded by: string null; tags: string ; source task id: string null; created by: string; created at: string; updated at: string; } export interface KnowledgeDecisionFull { id: string; workspace id: string; project id: string null; title: string; content: string; type: string; status: string; realiz… 证据：`src/tools/knowledge.ts`
- **Milestones**（source_file）：import type { SupabaseClient } from '@supabase/supabase-js'; ⋮---- export async function listMilestones client: SupabaseClient, projectId: string, args: ⋮---- export async function createMilestone client: SupabaseClient, projectId: string, userId: string, args: { name: string; description?: string } ⋮---- export async function updateMilestone client: SupabaseClient, projectId: string, args: { milestone id: string; name?: string; description?: string } ⋮---- export async function shipMilestone client: SupabaseClient, projectId: string, args: { milestone id: string } 证据：`src/tools/milestones.ts`
- **Project**（source_file）：import type { SupabaseClient } from '@supabase/supabase-js'; import { resolveTrustLevel, type TrustLevel } from './trust-model.js'; ⋮---- interface AgentTrustResolved { level: TrustLevel; overrides: Record ; } type ProjectWithTrust = { id: string; name: string; key: string; description: string null; mode: string; custom statuses: unknown; field definitions: unknown; archived: boolean; agent trust: AgentTrustResolved; k: string : unknown; }; export async function getProject client: SupabaseClient, projectId: string : Promise 证据：`src/tools/project.ts`
- **Query Tasks**（source_file）：import type { SupabaseClient } from '@supabase/supabase-js'; export interface QueryTasksArgs { status?: string; assignee id?: string; epic id?: string; cycle id?: string; milestone id?: string; priority?: string; label ids?: string ; due date from?: string; due date to?: string; stale days?: number; awaiting human input?: boolean; workflow state?: string; workflow activity?: string; stale?: boolean; archived?: boolean; sort by?: 'position' 'due date' 'priority' 'updated at'; limit?: number; offset?: number; } ⋮---- export async function queryTasks client: SupabaseClient, projectId: string, args: QueryTasksArgs, 证据：`src/tools/query-tasks.ts`
- **Tasks**（source_file）：import type { SupabaseClient } from '@supabase/supabase-js'; import { resolveTaskId } from './resolve-task-id.js'; import { resolveAssignee } from './members.js'; import { fetchPendingResolution } from './briefs.js'; import { detectRiskClasses } from './risk-class.js'; ⋮---- export async function listTasks client: SupabaseClient, projectId: string, args: { status?: string; epic id?: string; assignee id?: string; archived?: boolean; label ids?: string ; limit?: number; offset?: number } ⋮---- export async function getTask client: SupabaseClient, projectId: string, args: { task id: string; changed paths?: string }, ⋮---- export async function createTask client: SupabaseClient, projectId: stri… 证据：`src/tools/tasks.ts`
- **Knowledge-query discipline agent-model §7**（documentation）：Knowledge-query discipline agent-model §7 证据：`skills/harmony-shared/knowledge-discipline.md`
- **Role-scoped capability profiles agent-model §3**（documentation）：Role-scoped capability profiles agent-model §3 证据：`skills/harmony-shared/role-profiles.md`
- **Visual hand-off discipline B-328**（documentation）：How to run a UX/UI design decision through a generated, manipulable surface + an iterate loop — the v1 default for UX/UI structural decisions, including flows . Source: the B-328 spike retro docs/next-gen-harmony/2026-05-29-visual-handoff-spike-retro.md , decisions D1–D3 . Any skill that hands a visual decision to a human follows this; harmony-visual-handoff is its first user. 证据：`skills/harmony-shared/visual-handoff.md`
- **Tsconfig**（structured_config）：{ "compilerOptions": { "target": "ES2022", "module": "Node16", "moduleResolution": "Node16", "outDir": "./dist", "rootDir": "./src", "strict": true, "esModuleInterop": true, "declaration": true, "sourceMap": true, "skipLibCheck": true }, "include": "src/ / " , "exclude": "src/ / .test.ts" } 证据：`tsconfig.json`
- **.gitignore**（source_file）：node modules/ .DS Store .worktrees/ coverage/ .harmony-task.json 证据：`.gitignore`
- 其余 3 条证据见 `AI_CONTEXT_PACK.json` 或 `EVIDENCE_INDEX.json`。

## 宿主 AI 必须遵守的规则

- **把本资产当作开工前上下文，而不是运行环境。**：AI Context Pack 只包含证据化项目理解，不包含目标项目的可执行状态。 证据：`README.md`, `package.json`, `skills/finish-work/SKILL.md`
- **回答用户时区分可预览内容与必须安装后才能验证的内容。**：安装前体验的消费者价值来自降低误装和误判，而不是伪装成真实运行。 证据：`README.md`, `package.json`, `skills/finish-work/SKILL.md`

## 用户开工前应该回答的问题

- 你准备在哪个宿主 AI 或本地环境中使用它？
- 你只是想先体验工作流，还是准备真实安装？
- 你最在意的是安装成本、输出质量、还是和现有规则的冲突？

## 验收标准

- 所有能力声明都能回指到 evidence_refs 中的文件路径。
- AI_CONTEXT_PACK.md 没有把预览包装成真实运行。
- 用户能在 3 分钟内看懂适合谁、能做什么、如何开始和风险边界。

---

## Doramagic Context Augmentation

下面内容用于强化 Repomix/AI Context Pack 主体。Human Manual 只提供阅读骨架；踩坑日志会被转成宿主 AI 必须遵守的工作约束。

## Human Manual 骨架

使用规则：这里只是项目阅读路线和显著性信号，不是事实权威。具体事实仍必须回到 repo evidence / Claim Graph。

宿主 AI 硬性规则：
- 不得把页标题、章节顺序、摘要或 importance 当作项目事实证据。
- 解释 Human Manual 骨架时，必须明确说它只是阅读路线/显著性信号。
- 能力、安装、兼容性、运行状态和风险判断必须引用 repo evidence、source path 或 Claim Graph。

- **项目概述与系统架构**：importance `high`
  - source_paths: README.md, package.json, tsconfig.json, src/index.ts, src/bin/harmony.ts
- **CLI 命令、认证与配置**：importance `high`
  - source_paths: src/cli/index.ts, src/cli/commands/auth.ts, src/cli/commands/tasks.ts, src/cli/commands/project.ts, src/cli/commands/epics.ts
- **MCP 服务器、工具注册表与数据访问层**：importance `high`
  - source_paths: src/index.ts, src/tools/index.ts, src/tools/tasks.ts, src/tools/comments.ts, src/tools/labels.ts
- **Claude Code 插件生命周期与工作流技能**：importance `high`
  - source_paths: .claude-plugin/marketplace.json, .claude-plugin/plugin.json, hooks/hooks.json, .mcp.json, commands/harmony-setup.md

## Repo Inspection Evidence / 源码检查证据

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `989bacac62868adce2f1211f8ada3b99084bbdda`
- inspected_files: `README.md`, `package.json`, `docs/superpowers/plans/2026-04-03-harmony-cli.md`, `docs/superpowers/plans/2026-04-14-plugin-install-build.md`, `docs/superpowers/plans/2026-06-08-knowledge-promote-reembed.md`, `docs/superpowers/plans/2026-06-08-update-knowledge-status-vocab.md`, `src/auth.ts`, `src/bin/harmony.ts`, `src/cli/auth.ts`, `src/cli/commands/acceptance-criteria.ts`, `src/cli/commands/activity.ts`, `src/cli/commands/auth.ts`, `src/cli/commands/bulk.ts`, `src/cli/commands/checklist.ts`, `src/cli/commands/comments.ts`, `src/cli/commands/cycles.ts`, `src/cli/commands/dependencies.ts`, `src/cli/commands/epics.ts`, `src/cli/commands/knowledge.ts`, `src/cli/commands/labels.ts`

宿主 AI 硬性规则：
- 没有 repo_clone_verified=true 时，不得声称已经读过源码。
- 没有 repo_inspection_verified=true 时，不得把 README/docs/package 文件判断写成事实。
- 没有 quick_start_verified=true 时，不得声称 Quick Start 已跑通。

## Doramagic Pitfall Constraints / 踩坑约束

这些规则来自 Doramagic 发现、验证或编译过程中的项目专属坑点。宿主 AI 必须把它们当作工作约束，而不是普通说明文字。

### Constraint 1: 可能修改宿主 AI 配置

- Trigger: 项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。
- Host AI rule: 列出会写入的配置文件、目录和卸载/回滚步骤。
- Why it matters: 安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。
- Evidence: capability.host_targets | https://github.com/ycomplex/harmony-plugin | host_targets=mcp_host, claude_code, claude
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 2: 能力判断依赖假设

- Trigger: README/documentation is current enough for a first validation pass.
- Host AI rule: 将假设转成下游验证清单。
- Why it matters: 假设不成立时，用户拿不到承诺的能力。
- Evidence: capability.assumptions | https://github.com/ycomplex/harmony-plugin | README/documentation is current enough for a first validation pass.
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 3: 维护活跃度未知

- Trigger: 未记录 last_activity_observed。
- Host AI rule: 补 GitHub 最近 commit、release、issue/PR 响应信号。
- Why it matters: 新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。
- Evidence: evidence.maintainer_signals | https://github.com/ycomplex/harmony-plugin | last_activity_observed missing
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

- Trigger: no_demo
- Evidence: downstream_validation.risk_items | https://github.com/ycomplex/harmony-plugin | no_demo; severity=medium
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 5: 存在评分风险

- Trigger: no_demo
- Why it matters: 风险会影响是否适合普通用户安装。
- Evidence: risks.scoring_risks | https://github.com/ycomplex/harmony-plugin | no_demo; severity=medium
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 6: issue/PR 响应质量未知

- Trigger: issue_or_pr_quality=unknown。
- Host AI rule: 抽样最近 issue/PR，判断是否长期无人处理。
- Why it matters: 用户无法判断遇到问题后是否有人维护。
- Evidence: evidence.maintainer_signals | https://github.com/ycomplex/harmony-plugin | issue_or_pr_quality=unknown
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 7: 发布节奏不明确

- Trigger: release_recency=unknown。
- Host AI rule: 确认最近 release/tag 和 README 安装命令是否一致。
- Why it matters: 安装命令和文档可能落后于代码，用户踩坑概率升高。
- Evidence: evidence.maintainer_signals | https://github.com/ycomplex/harmony-plugin | release_recency=unknown
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。