@rpamis/comet 0.1.4 → 0.1.6

package/assets/skills/comet-tweak/SKILL.md

@@ -1,152 +1,154 @@
----
-name: comet-tweak
-description: "Comet 预设路径：非 bug 的小改动（tweak）。跳过 brainstorming 和完整 plan，直接 open → lightweight build → light verify → archive。适用于文案、配置、文档或 prompt 的局部优化。"
----
-
-# Comet 预设路径：Tweak
-
-Tweak 是 Comet 五阶段能力的预设工作流，不是独立的平行流程。它复用 open、build、verify、archive 能力，仅跳过 brainstorming 和完整 plan。
-
-适用于非 bug 的小范围变更，例如文案调整、配置调整、文档或 prompt 的局部优化。
-
-**适用条件**（必须全部满足）：
-1. 不新增 capability
-2. 不改变架构
-3. 不涉及接口变化
-4. 通常不超过 3 个 tasks、5 个文件
-
-**不适用**：如变更过程中发现需要 capability、架构或接口调整，应升级为完整 `/comet` 流程。
-
----
-
-## 流程（preset workflow，4 阶段）
-
-### 0. 入口状态验证（Entry Check）
-
-在执行任何操作之前，验证当前状态：
-
-**检查清单：**
-1. `openspec/changes/<name>/` 目录不存在，或目录存在但 `.comet.yaml` 不存在（无冲突）
-
-**验证方式：**
-- `test -d openspec/changes/<name>` 检查目录
-- 如目录存在，`test -f openspec/changes/<name>/.comet.yaml` 检查配置文件
-- 如 `.comet.yaml` 已存在，读取 `phase` 检查是否为未完成的 tweak
-
-**失败输出（有冲突）：**
-```
-[HARD STOP] Entry check failed for comet-tweak
-  Expected: openspec/changes/<name>/.comet.yaml does not exist (new change)
-  Actual:   .comet.yaml exists with phase=<实际值>
-  Suggestion: Pick a different change name, or check if an existing tweak is in progress.
-```
-
-验证通过后才进入流程步骤。
-
-执行链路：open → lightweight build → light verify → archive。Tweak 为每个阶段提供默认决策：精简开启、轻量构建、轻量验证、验证通过后归档。
-
-### 1. 快速开启（preset open）
-
-复用 Comet open 能力创建 change，但使用 tweak 默认值：不执行 `openspec-explore` 长探索，直接进入精简 change 创建。
-
-**立即执行：** 使用 Skill 工具加载 `openspec-new-change` 技能。禁止跳过此步骤。
-
-技能加载后，按其指引创建精简版产物：
-  - `proposal.md` — 变更动机 + 目标 + 范围
-  - `design.md` — 简短实现说明（无需方案对比）
-  - `tasks.md` — 不超过 3 个任务
-- **无需 delta spec**（除非变更改变了已有 spec 的验收场景；一旦需要 delta spec，升级为完整 `/comet`）
-
-在 `openspec/changes/<name>/` 下创建独立的 `.comet.yaml` 文件：
-
-```yaml
-workflow: tweak
-phase: build
-design_doc: null
-plan: null
-build_mode: direct
-verify_mode: light
-verify_result: pending
-verified_at: null
-archived: false
-```
-
-【写入验证】创建完成后必须验证：
-  cat openspec/changes/<name>/.comet.yaml
-  确认 workflow 行的值为 "tweak"
-  确认 phase 行的值为 "build"
-  确认 design_doc 行的值为 "null"
-  确认 plan 行的值为 "null"
-  确认 build_mode 行的值为 "direct"
-  确认 verify_mode 行的值为 "light"
-  确认 verify_result 行的值为 "pending"
-  确认 verified_at 行的值为 "null"
-  确认 archived 行的值为 "false"
-  如任一字段不匹配，重试写入后再次验证。最多重试 2 次，仍失败则报告错误并终止。
-
-### 2. 轻量构建（preset build）
-
-使用 tweak 默认值：`build_mode: direct`。跳过 `superpowers:brainstorming` 和 `superpowers:writing-plans`。
-
-**立即执行：** 按 tasks.md 逐个执行任务：
-
-1. 读取 `openspec/changes/<name>/tasks.md`，获取未完成任务列表
-2. 对每个未完成任务：
-   - 根据任务描述修改目标文件
-   - 运行 `mvn spotless:apply` 格式化
-   - 运行相关测试确认通过
-   - 将 tasks.md 中对应 `- [ ]` 勾选为 `- [x]`
-   - 提交代码，commit message 格式：`tweak: <简述变更>`
-3. 全部任务完成后进入验证
-
-### 3. 轻量验证（preset verify）
-
-复用 `/comet-verify`。Tweak 必须保持轻量验证条件：≤ 3 tasks、≤ 5 files、无 delta spec、无新 capability。
-
-**立即执行：** 使用 Skill 工具加载 `comet-verify` 技能。禁止跳过此步骤。
-
-如规模评估进入完整验证路径，停止 tweak，升级为完整 `/comet`。
-
-验证通过后，按 `/comet-verify` 的规则将 `.comet.yaml` 的 `verify_result` 记录为 `pass`，归档前不得跳过该状态。
-
-### 4. 归档（preset archive）
-
-复用 `/comet-archive`。归档前必须满足 `.comet.yaml` 中 `verify_result: pass`。
-
-**立即执行：** 使用 Skill 工具加载 `comet-archive` 技能进行归档。禁止跳过此步骤。
-
----
-
-## 连续执行模式
-
-<IMPORTANT>
-Tweak 流程为 **一次性连续执行**。调用 `/comet-tweak` 后，agent 必须自动走完全部 4 个阶段，中间不停顿等待用户输入（除非遇到升级条件需要用户确认）。
-
-执行顺序：快速开启 → 轻量构建 → 轻量验证 → 归档 → 完成
-
-每个阶段完成后立即进入下一阶段，无需用户再次输入。阶段内部仍必须按上文要求调用对应 Comet/OpenSpec/Superpowers skill。
-</IMPORTANT>
-
----
-
-## 升级条件
-
-执行过程中出现以下情况时，停止 tweak 流程，升级为完整 `/comet`：
-
-1. 需要新增 capability
-2. 需要架构调整
-3. 需要接口变化
-4. 影响范围扩大到 > 5 个文件
-5. 任务数超过 3 个
-6. 需要 delta spec
-
-升级方式：在当前 change 基础上补充 Design Doc（执行 `/comet-design`），后续正常走完整流程。
-
----
-
-## 退出条件
-
-- 小改动已完成，测试通过
-- change 已归档
-- 未新增 capability、架构调整或接口变化
-- **阶段守卫**：build → verify 前运行 `bash $COMET_GUARD <change-name> build`，verify → archive 前运行 `bash $COMET_GUARD <change-name> verify`
+---
+name: comet-tweak
+description: "Comet preset path: Non-bug small changes (tweak). Skip brainstorming and full plan, directly open → lightweight build → light verify → archive. Applicable for copy, configuration, documentation or prompt local optimization."
+---
+
+# Comet Preset Path: Tweak
+
+Tweak is a preset workflow of Comet's five-phase capabilities, not a separate parallel process. It reuses open, build, verify, archive capabilities, only skipping brainstorming and full plan.
+
+Applicable for small-scale non-bug changes, such as copy adjustments, configuration adjustments, documentation or prompt local optimization.
+
+**Applicable conditions** (all must be met):
+1. No new capability
+2. No architecture changes
+3. No interface changes involved
+4. Usually not exceeding 3 tasks, 5 files
+
+**Not applicable**: If change process discovers need for capability, architecture, or interface adjustments, should upgrade to full `/comet` workflow.
+
+---
+
+## Process (preset workflow, 4 phases)
+
+### 0. Entry State Verification (Entry Check)
+
+Before performing any operations, verify current state:
+
+**Checklist:**
+1. `openspec/changes/<name>/` directory does not exist, or directory exists but `.comet.yaml` does not exist (no conflict)
+
+**Verification method:**
+- `test -d openspec/changes/<name>` to check directory
+- If directory exists, `test -f openspec/changes/<name>/.comet.yaml` to check config file
+- If `.comet.yaml` exists, read `phase` to check if it's an incomplete tweak
+
+**Failure output (has conflict):**
+```
+[HARD STOP] Entry check failed for comet-tweak
+  Expected: openspec/changes/<name>/.comet.yaml does not exist (new change)
+  Actual:   .comet.yaml exists with phase=<actual-value>
+  Suggestion: Pick a different change name, or check if an existing tweak is in progress.
+```
+
+Proceed to process steps only after verification passes.
+
+Execution chain: open → lightweight build → light verify → archive. Tweak provides default decisions for each phase: streamlined open, lightweight build, lightweight verification, archive after verification passes.
+
+### 1. Quick Open (preset open)
+
+Reuse Comet open capability to create change, but use tweak defaults: do not execute `openspec-explore` long exploration, directly enter streamlined change creation.
+
+**Immediately execute:** Use the Skill tool to load the `openspec-new-change` skill. Skipping this step is prohibited.
+
+After the skill loads, follow its guidance to create streamlined artifacts:
+  - `proposal.md` — change motivation + goals + scope
+  - `design.md` — brief implementation description (no solution comparison needed)
+  - `tasks.md` — not exceeding 3 tasks
+- **No delta spec needed** (unless change changes existing spec acceptance scenarios; once delta spec needed, upgrade to full `/comet`)
+
+Create independent `.comet.yaml` file under `openspec/changes/<name>/`:
+
+```yaml
+workflow: tweak
+phase: build
+design_doc: null
+plan: null
+build_mode: direct
+isolation: branch
+verify_mode: light
+verify_result: pending
+verified_at: null
+archived: false
+```
+
+【Write verification】After creation completion, must verify:
+  cat openspec/changes/<name>/.comet.yaml
+  Confirm workflow line value is "tweak"
+  Confirm phase line value is "build"
+  Confirm design_doc line value is "null"
+  Confirm plan line value is "null"
+  Confirm build_mode line value is "direct"
+  Confirm isolation line value is "branch"
+  Confirm verify_mode line value is "light"
+  Confirm verify_result line value is "pending"
+  Confirm verified_at line value is "null"
+  Confirm archived line value is "false"
+  If any field does not match, retry write then verify again. Maximum 2 retries, report error and terminate if still fails.
+
+### 2. Lightweight Build (preset build)
+
+Use tweak defaults: `build_mode: direct`. Skip `superpowers:brainstorming` and `superpowers:writing-plans`.
+
+**Immediately execute:** Execute tasks one by one according to tasks.md:
+
+1. Read `openspec/changes/<name>/tasks.md`, get incomplete task list
+2. For each incomplete task:
+   - Modify target file according to task description
+   - Run `mvn spotless:apply` to format
+   - Run related tests to confirm pass
+   - Check corresponding `- [ ]` to `- [x]` in tasks.md
+   - Commit code, commit message format: `tweak: <brief change description>`
+3. After all tasks complete, enter verification
+
+### 3. Lightweight Verification (preset verify)
+
+Reuse `/comet-verify`. Tweak must maintain lightweight verification conditions: ≤ 3 tasks, ≤ 5 files, no delta spec, no new capability.
+
+**Immediately execute:** Use the Skill tool to load the `comet-verify` skill. Skipping this step is prohibited.
+
+If scale assessment enters full verification path, stop tweak, upgrade to full `/comet`.
+
+After verification passes, record `.comet.yaml` `verify_result` as `pass` according to `/comet-verify` rules, must not skip this status before archiving.
+
+### 4. Archive (preset archive)
+
+Reuse `/comet-archive`. Must satisfy `verify_result: pass` in `.comet.yaml` before archiving.
+
+**Immediately execute:** Use the Skill tool to load the `comet-archive` skill to archive. Skipping this step is prohibited.
+
+---
+
+## Continuous Execution Mode
+
+<IMPORTANT>
+Tweak workflow is **one-time continuous execution**. After invoking `/comet-tweak`, agent must automatically complete all 4 phases, without pausing to wait for user input mid-way (unless encountering upgrade conditions requiring user confirmation).
+
+Execution order: quick open → lightweight build → lightweight verification → archive → complete
+
+After each phase completes, immediately enter next phase, no need for user input again. Within each phase, must still call corresponding Comet/OpenSpec/Superpowers skill according to above requirements.
+</IMPORTANT>
+
+---
+
+## Upgrade Conditions
+
+When the following situations occur during execution, stop tweak workflow, upgrade to full `/comet`:
+
+1. Need new capability
+2. Need architecture adjustments
+3. Need interface changes
+4. Impact scope expands to > 5 files
+5. Task count exceeds 3
+6. Need delta spec
+
+Upgrade method: On current change basis, supplement Design Doc (execute `/comet-design`), then proceed normally with full workflow.
+
+---
+
+## Exit Conditions
+
+- Small change completed, tests pass
+- Change archived
+- No new capability, architecture adjustments, or interface changes
+- **Phase guard**: Before build → verify run `bash $COMET_GUARD <change-name> build`, before verify → archive run `bash $COMET_GUARD <change-name> verify`

package/assets/skills/comet-verify/SKILL.md

@@ -1,164 +1,164 @@
----
-name: comet-verify
-description: "Comet 阶段 4：验证与收尾。用 /comet-verify 调用。验证实现符合设计，处理开发分支。"
----
-
-# Comet 阶段 4：验证与收尾（Verify）
-
-## 前置条件
-
-- 代码已提交（阶段 3 完成）
-- tasks.md 全部任务已完成
-
-## 步骤
-
-### 0. 入口状态验证（Entry Check）
-
-在执行任何操作之前，读取并验证当前状态：
-
-**检查清单：**
-1. `openspec/changes/<name>/.comet.yaml` 存在
-2. `phase` 字段的值为 `"verify"`
-3. `verify_result` 字段为 `"pending"` 或 null（尚未验证通过）
-
-**验证方式：**
-- `cat openspec/changes/<name>/.comet.yaml` 读取全部字段
-- 如 `verify_result` 已是 `"pass"`，说明此 change 已验证过
-
-**失败输出：**
-```
-[HARD STOP] Entry check failed for comet-verify
-  Expected: phase=verify, verify_result=pending|null
-  Actual:   phase=<实际值>, verify_result=<实际值>
-  Suggestion: Run comet-build first, or this change was already verified.
-```
-
-验证通过后才进入步骤 1。
-
-### 1. 改动规模评估
-
-根据以下指标判定改动规模：
-
-| 指标 | 小（轻量验证） | 大（完整验证） |
-|------|---------------|---------------|
-| tasks.md 任务数 | ≤ 3 | > 3 |
-| 变更文件数（git diff --stat） | ≤ 5 | > 5 |
-| 是否有 delta spec | 无 | 有 |
-| 是否新增 capability | 否 | 是 |
-
-**判定规则**：任一指标命中"大" → 完整验证。全部命中"小" → 轻量验证。
-
-判定完成后，在 `openspec/changes/<name>/.comet.yaml` 中记录实际验证模式。`verify_mode` 只允许以下值之一：
-
-- `light`
-- `full`
-
-Few-shot 示例：
-
-```yaml
-# 全部指标命中“小”
-phase: verify
-verify_mode: light
-verify_result: pending
-```
-
-```yaml
-# 任一指标命中”大”
-phase: verify
-verify_mode: full
-verify_result: pending
-```
-
-【写入验证】更新完成后必须验证：
-  cat openspec/changes/<name>/.comet.yaml
-  确认 verify_mode 行的值为 “<light 或 full>”
-  如不匹配，重试写入后再次验证。最多重试 2 次，仍失败则报告错误并终止。
-
-### 2a. 轻量验证（小改动）
-
-当规模评估结果为"小"时，跳过 `openspec-verify-change`，直接执行以下检查：
-
-1. tasks.md 全部任务已完成 `[x]`
-2. 改动文件与 tasks.md 描述一致（`git diff --stat` 对照 tasks 内容）
-3. 编译通过（Maven 项目先执行 `mvn spotless:apply`，再执行 `mvn compile` 或等效命令）
-4. 相关测试通过
-5. 无明显安全问题（无硬编码密钥、无新增 unsafe 操作）
-
-**通过标准**：5 项全部 OK，无 CRITICAL 问题。
-
-**报告格式**：简表列出 5 项检查结果 + PASS/FAIL。
-
-**跳过项**（不在轻量验证中检查）：
-- spec scenario 覆盖率
-- design doc 一致性深度比对
-- code pattern consistency 建议
-- delta spec 与 design doc 漂移检测
-
-### 2b. 完整验证（大改动）
-
-当规模评估结果为"大"时：
-
-**立即执行：** 使用 Skill 工具加载 `openspec-verify-change` 技能。禁止跳过此步骤。
-
-技能加载后，按其指引验证。检查项：
-1. tasks.md 全部任务已完成（`[x]`）
-2. 实现符合 design.md 设计决策
-3. 实现符合 brainstorming 设计文档
-4. 能力规格场景全部通过
-5. proposal.md 目标已满足
-6. delta spec 与 design doc 无矛盾（若 Build 阶段有增量修改 spec，检查 design doc 是否有对应记录）
-7. `docs/superpowers/specs/` 关联的设计文档可定位（文件存在且与当前 change 相关）
-
-验证不通过时：报告缺失项，返回阶段 3 补充（调用 `/comet-build`）。
-
-**Spec 漂移处理**：
-- 若检查项 6 发现矛盾（delta spec 有内容但 design doc 未体现），提示用户：
-  - 选项 A：在 design doc 追加 "Implementation Divergence" 节记录偏差原因
-  - 选项 B：回退到 Build 阶段，补充 brainstorming 更新 design doc
-  - 选项 C：确认偏差可接受，继续验证（归档时 design doc 将标记为 `superseded-by-main-spec`）
-
-### 3. 收尾（Superpowers）
-
-**立即执行：** 使用 Skill 工具加载 `superpowers:finishing-a-development-branch` 技能。禁止跳过此步骤。
-
-如 `superpowers:finishing-a-development-branch` 不可用，停止流程并提示安装或启用 Superpowers 技能，不要用普通对话替代该步骤。
-
-技能加载后，按其指引收尾。分支处理选项：
-1. 本地合并到主分支
-2. 推送并创建 PR
-3. 保持分支（稍后处理）
-4. 丢弃工作
-
-**确认项**：
-- Maven 测试或构建命令前已执行 `mvn spotless:apply`
-- 全部测试通过
-- 无遗留的 spotless 格式问题
-- 无硬编码密钥或安全问题
-
-## 退出条件
-
-- 验证报告通过
-- 分支已处理
-- `.comet.yaml` 中 `verify_result` 已记录为 `pass`
-- **阶段守卫**：运行 `bash $COMET_GUARD <change-name> verify`，全部 PASS 后才允许流转
-
-退出前在 `.comet.yaml` 中合并更新以下字段（保留其他字段不变）：
-
-```yaml
-phase: archive
-verify_result: pass
-verified_at: YYYY-MM-DD
-```
-
-【写入验证】更新完成后必须验证：
-  cat openspec/changes/<name>/.comet.yaml
-  确认 phase 行的值为 "archive"
-  确认 verify_result 行的值为 "pass"
-  确认 verified_at 行的值非空（格式为 YYYY-MM-DD）
-  如任一字段不匹配，重试写入后再次验证。最多重试 2 次，仍失败则报告错误并终止。
-
-## 自动流转
-
-退出条件满足后，**无需等待用户再次输入**，直接执行下一阶段：
-
-> **REQUIRED NEXT SKILL:** 调用 `comet-archive` skill 进入归档阶段。
+---
+name: comet-verify
+description: "Comet Phase 4: Verify and Complete. Invoke with /comet-verify. Verify implementation matches design, handle development branch."
+---
+
+# Comet Phase 4: Verify and Complete (Verify)
+
+## Prerequisites
+
+- Code has been committed (Phase 3 complete)
+- All tasks in tasks.md are complete
+
+## Steps
+
+### 0. Entry State Verification (Entry Check)
+
+Before performing any operations, read and verify the current state:
+
+**Checklist:**
+1. `openspec/changes/<name>/.comet.yaml` exists
+2. `phase` field value is `"verify"`
+3. `verify_result` field is `"pending"` or null (not yet verified)
+
+**Verification method:**
+- `cat openspec/changes/<name>/.comet.yaml` to read all fields
+- If `verify_result` is already `"pass"`, this change has already been verified
+
+**Failure output:**
+```
+[HARD STOP] Entry check failed for comet-verify
+  Expected: phase=verify, verify_result=pending|null
+  Actual:   phase=<actual-value>, verify_result=<actual-value>
+  Suggestion: Run comet-build first, or this change was already verified.
+```
+
+Proceed to Step 1 only after verification passes.
+
+### 1. Change Scale Assessment
+
+Determine change scale based on the following metrics:
+
+| Metric | Small (lightweight verification) | Large (full verification) |
+|------|-------------------------------|--------------------------|
+| tasks.md task count | ≤ 3 | > 3 |
+| Changed file count (git diff --stat) | ≤ 5 | > 5 |
+| Has delta spec | No | Yes |
+| New capability added | No | Yes |
+
+**Decision rule**: Any metric hitting "large" → full verification. All hitting "small" → lightweight verification.
+
+After determination, record actual verification mode in `openspec/changes/<name>/.comet.yaml`. `verify_mode` only allows one of the following values:
+
+- `light`
+- `full`
+
+Few-shot examples:
+
+```yaml
+# All metrics hit "small"
+phase: verify
+verify_mode: light
+verify_result: pending
+```
+
+```yaml
+# Any metric hits "large"
+phase: verify
+verify_mode: full
+verify_result: pending
+```
+
+【Write verification】After update completion, must verify:
+  cat openspec/changes/<name>/.comet.yaml
+  Confirm verify_mode line value is "<light or full>"
+  If not matching, retry write then verify again. Maximum 2 retries, report error and terminate if still fails.
+
+### 2a. Lightweight Verification (Small Changes)
+
+When scale assessment result is "small", skip `openspec-verify-change`, directly execute the following checks:
+
+1. All tasks in tasks.md completed `[x]`
+2. Changed files consistent with tasks.md description (`git diff --stat`对照 tasks content)
+3. Build passes (for Maven projects, first execute `mvn spotless:apply`, then execute `mvn compile` or equivalent command)
+4. Related tests pass
+5. No obvious security issues (no hardcoded secrets, no new unsafe operations)
+
+**Pass standard**: All 5 items OK, no CRITICAL issues.
+
+**Report format**: Brief table listing 5 check results + PASS/FAIL.
+
+**Skipped items** (not checked in lightweight verification):
+- spec scenario coverage
+- design doc consistency deep comparison
+- code pattern consistency recommendations
+- delta spec and design doc drift detection
+
+### 2b. Full Verification (Large Changes)
+
+When scale assessment result is "large":
+
+**Immediately execute:** Use the Skill tool to load the `openspec-verify-change` skill. Skipping this step is prohibited.
+
+After the skill loads, follow its guidance to verify. Check items:
+1. All tasks in tasks.md completed (`[x]`)
+2. Implementation matches design.md design decisions
+3. Implementation matches brainstorming design document
+4. All capability specification scenarios pass
+5. proposal.md goals satisfied
+6. No contradiction between delta spec and design doc (if Build phase had incremental spec modifications, check if design doc has corresponding records)
+7. `docs/superpowers/specs/` associated design document can be located (file exists and relates to current change)
+
+When verification fails: report missing items, return to Phase 3 to supplement (invoke `/comet-build`).
+
+**Spec drift handling**:
+- If check item 6 finds contradiction (delta spec has content but design doc doesn't reflect it), prompt user:
+  - Option A: Append "Implementation Divergence" section to design doc recording deviation reason
+  - Option B: Roll back to Build phase, supplement brainstorming to update design doc
+  - Option C: Confirm deviation acceptable, continue verification (design doc will be marked as `superseded-by-main-spec` during archiving)
+
+### 3. Completion (Superpowers)
+
+**Immediately execute:** Use the Skill tool to load the `superpowers:finishing-a-development-branch` skill. Skipping this step is prohibited.
+
+If `superpowers:finishing-a-development-branch` is unavailable, stop the process and prompt to install or enable Superpowers skills. Do not substitute this step with normal conversation.
+
+After the skill loads, follow its guidance to complete. Branch handling options:
+1. Local merge to main branch
+2. Push and create PR
+3. Keep branch (handle later)
+4. Discard work
+
+**Confirmation items**:
+- Maven test or build commands have executed `mvn spotless:apply`
+- All tests pass
+- No remaining spotless formatting issues
+- No hardcoded secrets or security issues
+
+## Exit Conditions
+
+- Verification report passed
+- Branch handled
+- `.comet.yaml` `verify_result` recorded as `pass`
+- **Phase guard**: Run `bash $COMET_GUARD <change-name> verify`, allow transition only after all PASS
+
+Before exit, merge and update the following fields in `.comet.yaml` (keep other fields unchanged):
+
+```yaml
+phase: archive
+verify_result: pass
+verified_at: YYYY-MM-DD
+```
+
+【Write verification】After update completion, must verify:
+  cat openspec/changes/<name>/.comet.yaml
+  Confirm phase line value is "archive"
+  Confirm verify_result line value is "pass"
+  Confirm verified_at line value is non-empty (format YYYY-MM-DD)
+  If any field does not match, retry write then verify again. Maximum 2 retries, report error and terminate if still fails.
+
+## Automatic Transition
+
+After exit conditions are met, **proceed immediately to the next phase without waiting for user input**:
+
+> **REQUIRED NEXT SKILL:** Invoke `comet-archive` skill to enter the archiving phase.