@rpamis/comet 0.1.7 → 0.1.8

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

@@ -14,29 +14,14 @@ description: "Comet Phase 3: Plan and Build. Invoke with /comet-build. Create pl
 
 ### 0. Entry State Verification (Entry Check)
 
-Before performing any operations, read and verify the current state:
+Execute entry verification:
 
-**Checklist:**
-1. `openspec/changes/<name>/.comet.yaml` exists
-2. `phase` field value is `"build"`
-3. `design_doc` field is non-null and non-empty
-4. File referenced by `design_doc` exists (e.g., `docs/superpowers/specs/YYYY-MM-DD-topic-design.md`)
-5. `openspec/changes/<name>/proposal.md` exists and is non-empty
-6. `openspec/changes/<name>/tasks.md` exists and is non-empty
-
-**Verification method:**
-- `cat openspec/changes/<name>/.comet.yaml` to read all fields
-- Use `ls` or `test -f` to confirm design_doc file exists
-
-**Failure output:**
-```
-[HARD STOP] Entry check failed for comet-build
-  Expected: phase=build, design_doc=<path> exists
-  Actual:   phase=<actual-value>, design_doc=<actual-value or file does not exist>
-  Suggestion: Run comet-design first, or verify design_doc file exists.
+```bash
+COMET_STATE=$(find . -path '*/comet/scripts/comet-state.sh' -type f -print -quit)
+bash "$COMET_STATE" check <name> build
 ```
 
-Proceed to Step 1 only after verification passes.
+Proceed to Step 1 after verification passes. The script outputs specific failure reasons when verification fails.
 
 ### 1. Create Plan
 
@@ -59,7 +44,7 @@ design-doc: docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md
 Record plan path:
 
 ```bash
-sed -i 's|^plan:.*|plan: docs/superpowers/plans/YYYY-MM-DD-feature.md|' openspec/changes/<name>/.comet.yaml
+bash "$COMET_STATE" set <name> plan docs/superpowers/plans/YYYY-MM-DD-feature.md
 ```
 
 No manual phase update needed — guard auto-transitions when exit conditions are met.
@@ -77,7 +62,11 @@ Plan has been written to the current branch. Before starting execution, choose w
 - Change involves ≤ 3 files → Recommend A
 - Need parallel development, current branch has uncommitted work → Recommend B
 
-After user selection, update `isolation` in `openspec/changes/<name>/.comet.yaml`. `isolation` only allows one of the following values:
+After user selection, update `isolation` field. `isolation` only allows one of the following values:
+
+```bash
+bash "$COMET_STATE" set <name> isolation <value>
+```
 
 - `branch`
 - `worktree`
@@ -103,7 +92,11 @@ Present plan summary to user (task count, involved modules), then ask for execut
 - Task count ≤ 2 and no cross-module dependencies → Recommend B
 - From hotfix path → Recommend B
 
-After user selection, update `build_mode` in `openspec/changes/<name>/.comet.yaml`. `build_mode` only allows one of the following values:
+After user selection, update `build_mode` field. `build_mode` only allows one of the following values:
+
+```bash
+bash "$COMET_STATE" set <name> build_mode <value>
+```
 
 - `subagent-driven-development`
 - `executing-plans`

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

@@ -14,30 +14,14 @@ description: "Comet Phase 2: Deep Design. Invoke with /comet-design. Produce Des
 
 ### 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 `"design"`
-3. `workflow` field value is `"full"`
-4. `design_doc` field is `null` or empty
-5. `openspec/changes/<name>/proposal.md` exists and is non-empty
-6. `openspec/changes/<name>/design.md` exists and is non-empty
-7. `openspec/changes/<name>/tasks.md` exists and is non-empty
-
-**Verification method:**
-- `cat openspec/changes/<name>/.comet.yaml` to read all fields
-- Check checklist items one by one
-
-**Failure output:**
-```
-[HARD STOP] Entry check failed for comet-design
-  Expected: phase=design, design_doc=<empty/null>, workflow=full
-  Actual:   phase=<actual-value>, design_doc=<actual-value>, workflow=<actual-value>
-  Suggestion: Run comet-open first, or check if .comet.yaml was modified out of sequence.
+Execute entry verification:
+
+```bash
+COMET_STATE=$(find . -path '*/comet/scripts/comet-state.sh' -type f -print -quit)
+bash "$COMET_STATE" check <name> design
 ```
 
-Proceed to Step 1 only after verification passes.
+Proceed to Step 1 after verification passes. The script outputs specific failure reasons when verification fails.
 
 ### 1a. Read Existing Context
 
@@ -70,7 +54,7 @@ Record design_doc path, then run guard to auto-transition:
 
 ```bash
 # Record design_doc path
-sed -i 's|^design_doc:.*|design_doc: docs/superpowers/specs/YYYY-MM-DD-topic-design.md|' openspec/changes/<name>/.comet.yaml
+bash "$COMET_STATE" set <name> design_doc docs/superpowers/specs/YYYY-MM-DD-topic-design.md
 
 # Auto-transition to next phase
 bash $COMET_GUARD <change-name> design --apply

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

@@ -22,25 +22,14 @@ Applicable for bug fixes, hotfixes, small-scale behavior corrections. Does not i
 
 ### 0. Entry State Verification (Entry Check)
 
-Before performing any operations, verify current state:
+Execute entry verification:
 
-**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 hotfix
-
-**Failure output (has conflict):**
-```
-[HARD STOP] Entry check failed for comet-hotfix
-  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 hotfix is in progress.
+```bash
+COMET_STATE=$(find . -path '*/comet/scripts/comet-state.sh' -type f -print -quit)
+bash "$COMET_STATE" check <name> open
 ```
 
-Proceed to process steps only after verification passes.
+Proceed to process steps after verification passes. The script outputs specific failure reasons when verification fails.
 
 Execution chain: open → build → verify → archive. Hotfix provides default decisions for each phase: streamlined open, direct build, scale-based verification, archive after verification passes.
 
@@ -56,34 +45,11 @@ After the skill loads, follow its guidance to create streamlined artifacts:
   - `tasks.md` — fix task list
 - **No delta spec needed** (unless fix changes existing spec acceptance scenarios)
 
-Create independent `.comet.yaml` file under `openspec/changes/<name>/`:
-
-```yaml
-workflow: hotfix
-phase: build
-design_doc: null
-plan: null
-build_mode: direct
-isolation: branch
-verify_mode: light
-verify_result: pending
-verified_at: null
-archived: false
-```
+Initialize Comet state file:
 
-【Write verification】After creation completion, must verify:
-  cat openspec/changes/<name>/.comet.yaml
-  Confirm workflow line value is "hotfix"
-  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.
+```bash
+bash "$COMET_STATE" init <name> hotfix
+```
 
 ### 2. Direct Build (preset build)
 

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

@@ -13,28 +13,14 @@ description: "Comet Phase 1: Open. Invoke with /comet-open. Explore ideas throug
 
 ### 0. Entry State Verification (Entry Check)
 
-Before performing any operations, read and verify the current state:
+Execute entry verification:
 
-**Checklist:**
-1. `openspec/changes/<name>/` directory exists (created by openspec-new-change)
-2. `openspec/changes/<name>/.comet.yaml` file does not exist (not yet initialized)
-3. `openspec/changes/<name>/proposal.md` exists and is non-empty
-4. `openspec/changes/<name>/design.md` exists and is non-empty
-5. `openspec/changes/<name>/tasks.md` exists and is non-empty
-
-**Verification method:**
-- Read the above paths to confirm existence/non-existence
-- If `.comet.yaml` already exists, read its `phase` field: if phase is not empty, output `[HARD STOP]` and prompt that there may already be an active change
-
-**Failure output:**
-```
-[HARD STOP] Entry check failed for comet-open
-  Expected: .comet.yaml does not exist, proposal.md + design.md + tasks.md exist
-  Actual:   phase=<actual-value>, design_doc=<actual-value> (or file does not exist)
-  Suggestion: Check if another change with the same name is already active.
+```bash
+COMET_STATE=$(find . -path '*/comet/scripts/comet-state.sh' -type f -print -quit)
+bash "$COMET_STATE" check <name> open
 ```
 
-Proceed to Step 1 only after verification passes.
+Proceed to Step 1 after verification passes. The script outputs specific failure reasons when verification fails.
 
 ### 1. Explore Idea
 
@@ -59,18 +45,10 @@ openspec/changes/<name>/
 
 ### 3. Initialize Comet State
 
-Create an independent `.comet.yaml` file under `openspec/changes/<name>/`:
-
-```yaml
-workflow: full
-phase: design
-design_doc: null
-plan: null
-build_mode: null
-verify_mode: null
-verify_result: pending
-verified_at: null
-archived: false
+Initialize Comet state file:
+
+```bash
+bash "$COMET_STATE" init <name> full
 ```
 
 ### 4. Content Completeness Check

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

@@ -23,25 +23,14 @@ Applicable for small-scale non-bug changes, such as copy adjustments, configurat
 
 ### 0. Entry State Verification (Entry Check)
 
-Before performing any operations, verify current state:
+Execute entry verification:
 
-**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.
+```bash
+COMET_STATE=$(find . -path '*/comet/scripts/comet-state.sh' -type f -print -quit)
+bash "$COMET_STATE" check <name> open
 ```
 
-Proceed to process steps only after verification passes.
+Proceed to process steps after verification passes. The script outputs specific failure reasons when verification fails.
 
 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.
 
@@ -57,34 +46,11 @@ After the skill loads, follow its guidance to create streamlined artifacts:
   - `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
-```
+Initialize Comet state file:
 
-【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.
+```bash
+bash "$COMET_STATE" init <name> tweak
+```
 
 ### 2. Lightweight Build (preset build)
 

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

@@ -14,44 +14,24 @@ description: "Comet Phase 4: Verify and Complete. Invoke with /comet-verify. Ver
 
 ### 0. Entry State Verification (Entry Check)
 
-Before performing any operations, read and verify the current state:
+Execute entry verification:
 
-**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.
+```bash
+COMET_STATE=$(find . -path '*/comet/scripts/comet-state.sh' -type f -print -quit)
+bash "$COMET_STATE" check <name> verify
 ```
 
-Proceed to Step 1 only after verification passes.
+Proceed to Step 1 after verification passes. The script outputs specific failure reasons when verification fails.
 
 ### 1. Change Scale Assessment
 
-Determine change scale based on the following metrics:
+Execute scale assessment:
 
-| 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:
+```bash
+bash "$COMET_STATE" scale <name>
+```
 
-- `light`
-- `full`
+Script automatically counts tasks, delta specs, and changed files to determine whether to use light or full verification mode, and sets the verify_mode field.
 
 ### 2a. Lightweight Verification (Small Changes)
 

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

@@ -151,7 +151,7 @@ archived: false
 |------|---------|
 | `openspec list --json` 失败 | 检查 openspec 是否已安装，提示用户运行 `openspec init` |
 | 子 skill 不可用（如 `superpowers:brainstorming`） | 停止流程，提示安装或启用对应 skill |
-| `.comet.yaml` 格式异常或缺失 | 以文件状态为准（tasks.md、docs/superpowers/），修正元数据后继续 |
+| `.comet.yaml` 格式异常或缺失 | 以文件状态为准（tasks.md、docs/superpowers/），使用 `bash $COMET_STATE set <name> <field> <value>` 修正元数据后继续 |
 | Maven 编译/测试失败 | 返回 build 阶段修复，不进入 verify |
 | change 目录结构不完整 | 按 `comet-open` 的产物要求补齐缺失文件 |
 
@@ -169,6 +169,12 @@ COMET_GUARD=$(find . -path '*/comet/scripts/comet-guard.sh' -type f -print -quit
 bash "$COMET_GUARD" <change-name> <phase>
 ```
 
+**状态管理脚本**：`comet-state.sh` 提供 init/set/get/check/scale 五个子命令，统一管理状态文件字段：
+
+```bash
+COMET_STATE=$(find . -path '*/comet/scripts/comet-state.sh' -type f -print -quit)
+```
+
 **自动状态更新**：guard 支持 `--apply` 参数，验证通过后自动更新 `.comet.yaml` 状态字段：
 
 ```bash

package/assets/skills-zh/comet-archive/SKILL.md

@@ -15,27 +15,14 @@ description: "Comet 阶段 5：归档。用 /comet-archive 调用。同步 delta
 
 ### 0. 入口状态验证（Entry Check）
 
-在执行任何操作之前，读取并验证当前状态：
+执行入口验证：
 
-**检查清单：**
-1. `openspec/changes/<name>/.comet.yaml` 存在
-2. `phase` 字段的值为 `"archive"`
-3. `verify_result` 字段的值为 `"pass"`
-4. `archived` 字段为 `"false"` 或 null（尚未归档）
-
-**验证方式：**
-- `cat openspec/changes/<name>/.comet.yaml` 读取全部字段
-- 如 `verify_result` 不是 `"pass"`，必须先完成验证
-
-**失败输出：**
-```
-[HARD STOP] Entry check failed for comet-archive
-  Expected: phase=archive, verify_result=pass, archived=false|null
-  Actual:   phase=<实际值>, verify_result=<实际值>, archived=<实际值>
-  Suggestion: Run comet-verify first, or this change was already archived.
+```bash
+COMET_STATE=$(find . -path '*/comet/scripts/comet-state.sh' -type f -print -quit)
+bash "$COMET_STATE" check <name> archive
 ```
 
-验证通过后才进入步骤 1。
+验证通过后继续 Step 1。验证失败时脚本会输出具体失败原因。
 
 ### 1. 执行归档
 

package/assets/skills-zh/comet-build/SKILL.md

@@ -14,29 +14,14 @@ description: "Comet 阶段 3：计划与构建。用 /comet-build 调用。制
 
 ### 0. 入口状态验证（Entry Check）
 
-在执行任何操作之前，读取并验证当前状态：
+执行入口验证：
 
-**检查清单：**
-1. `openspec/changes/<name>/.comet.yaml` 存在
-2. `phase` 字段的值为 `"build"`
-3. `design_doc` 字段非 null 且非空
-4. `design_doc` 引用的文件存在（例如 `docs/superpowers/specs/YYYY-MM-DD-topic-design.md`）
-5. `openspec/changes/<name>/proposal.md` 存在且非空
-6. `openspec/changes/<name>/tasks.md` 存在且非空
-
-**验证方式：**
-- `cat openspec/changes/<name>/.comet.yaml` 读取全部字段
-- 用 `ls` 或 `test -f` 确认 design_doc 文件存在
-
-**失败输出：**
-```
-[HARD STOP] Entry check failed for comet-build
-  Expected: phase=build, design_doc=<path> exists
-  Actual:   phase=<实际值>, design_doc=<实际值或文件不存在>
-  Suggestion: Run comet-design first, or verify design_doc file exists.
+```bash
+COMET_STATE=$(find . -path '*/comet/scripts/comet-state.sh' -type f -print -quit)
+bash "$COMET_STATE" check <name> build
 ```
 
-验证通过后才进入步骤 1。
+验证通过后继续 Step 1。验证失败时脚本会输出具体失败原因。
 
 ### 1. 制定计划
 
@@ -59,7 +44,7 @@ design-doc: docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md
 先记录 plan 路径：
 
 ```bash
-sed -i 's|^plan:.*|plan: docs/superpowers/plans/YYYY-MM-DD-feature.md|' openspec/changes/<name>/.comet.yaml
+bash "$COMET_STATE" set <name> plan docs/superpowers/plans/YYYY-MM-DD-feature.md
 ```
 
 无需手动更新 phase，guard 会在退出条件满足后自动流转。
@@ -77,7 +62,11 @@ sed -i 's|^plan:.*|plan: docs/superpowers/plans/YYYY-MM-DD-feature.md|' openspec
 - 变更涉及 ≤ 3 个文件 → 推荐 A
 - 需要并行开发、当前分支有未提交工作 → 推荐 B
 
-用户选择后，在 `openspec/changes/<name>/.comet.yaml` 中更新 `isolation`。`isolation` 只允许以下值之一：
+用户选择后，更新 `isolation` 字段。`isolation` 只允许以下值之一：
+
+```bash
+bash "$COMET_STATE" set <name> isolation <value>
+```
 
 - `branch`
 - `worktree`
@@ -103,7 +92,11 @@ sed -i 's|^plan:.*|plan: docs/superpowers/plans/YYYY-MM-DD-feature.md|' openspec
 - 任务数 ≤ 2 且无跨模块依赖 → 推荐 B
 - 来自 hotfix 路径 → 推荐 B
 
-用户选择后，在 `openspec/changes/<name>/.comet.yaml` 中更新 `build_mode`。`build_mode` 只允许以下值之一：
+用户选择后，更新 `build_mode` 字段。`build_mode` 只允许以下值之一：
+
+```bash
+bash "$COMET_STATE" set <name> build_mode <value>
+```
 
 - `subagent-driven-development`
 - `executing-plans`

package/assets/skills-zh/comet-design/SKILL.md

@@ -14,30 +14,14 @@ description: "Comet 阶段 2：深度设计。用 /comet-design 调用。通过
 
 ### 0. 入口状态验证（Entry Check）
 
-在执行任何操作之前，读取并验证当前状态：
-
-**检查清单：**
-1. `openspec/changes/<name>/.comet.yaml` 存在
-2. `phase` 字段的值为 `"design"`
-3. `workflow` 字段的值为 `"full"`
-4. `design_doc` 字段为 `null` 或空
-5. `openspec/changes/<name>/proposal.md` 存在且非空
-6. `openspec/changes/<name>/design.md` 存在且非空
-7. `openspec/changes/<name>/tasks.md` 存在且非空
-
-**验证方式：**
-- `cat openspec/changes/<name>/.comet.yaml` 读取全部字段
-- 逐条比对检查清单
-
-**失败输出：**
-```
-[HARD STOP] Entry check failed for comet-design
-  Expected: phase=design, design_doc=<empty/null>, workflow=full
-  Actual:   phase=<实际值>, design_doc=<实际值>, workflow=<实际值>
-  Suggestion: Run comet-open first, or check if .comet.yaml was modified out of sequence.
+执行入口验证：
+
+```bash
+COMET_STATE=$(find . -path '*/comet/scripts/comet-state.sh' -type f -print -quit)
+bash "$COMET_STATE" check <name> design
 ```
 
-验证通过后才进入步骤 1。
+验证通过后继续 Step 1。验证失败时脚本会输出具体失败原因。
 
 ### 1a. 读取已有上下文
 
@@ -70,7 +54,7 @@ Design 摘要: <design.md 架构决策>
 
 ```bash
 # 记录 design_doc 路径
-sed -i 's|^design_doc:.*|design_doc: docs/superpowers/specs/YYYY-MM-DD-topic-design.md|' openspec/changes/<name>/.comet.yaml
+bash "$COMET_STATE" set <name> design_doc docs/superpowers/specs/YYYY-MM-DD-topic-design.md
 
 # 自动流转到下一阶段
 bash $COMET_GUARD <change-name> design --apply

package/assets/skills-zh/comet-hotfix/SKILL.md

@@ -22,25 +22,14 @@ Hotfix 是 Comet 五阶段能力的预设工作流，不是独立的平行流程
 
 ### 0. 入口状态验证（Entry Check）
 
-在执行任何操作之前，验证当前状态：
+执行入口验证：
 
-**检查清单：**
-1. `openspec/changes/<name>/` 目录不存在，或目录存在但 `.comet.yaml` 不存在（无冲突）
-
-**验证方式：**
-- `test -d openspec/changes/<name>` 检查目录
-- 如目录存在，`test -f openspec/changes/<name>/.comet.yaml` 检查配置文件
-- 如 `.comet.yaml` 已存在，读取 `phase` 检查是否为未完成的 hotfix
-
-**失败输出（有冲突）：**
-```
-[HARD STOP] Entry check failed for comet-hotfix
-  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 hotfix is in progress.
+```bash
+COMET_STATE=$(find . -path '*/comet/scripts/comet-state.sh' -type f -print -quit)
+bash "$COMET_STATE" check <name> open
 ```
 
-验证通过后才进入流程步骤。
+验证通过后继续流程步骤。验证失败时脚本会输出具体失败原因。
 
 执行链路：open → build → verify → archive。Hotfix 为每个阶段提供默认决策：精简开启、直接构建、按规模验证、验证通过后归档。
 
@@ -56,34 +45,11 @@ Hotfix 是 Comet 五阶段能力的预设工作流，不是独立的平行流程
   - `tasks.md` — 修复任务清单
 - **无需 delta spec**（除非修复改变了已有 spec 的验收场景）
 
-在 `openspec/changes/<name>/` 下创建独立的 `.comet.yaml` 文件：
-
-```yaml
-workflow: hotfix
-phase: build
-design_doc: null
-plan: null
-build_mode: direct
-isolation: branch
-verify_mode: light
-verify_result: pending
-verified_at: null
-archived: false
-```
+初始化 Comet 状态文件：
 
-【写入验证】创建完成后必须验证：
-  cat openspec/changes/<name>/.comet.yaml
-  确认 workflow 行的值为 "hotfix"
-  确认 phase 行的值为 "build"
-  确认 design_doc 行的值为 "null"
-  确认 plan 行的值为 "null"
-  确认 build_mode 行的值为 "direct"
-  确认 isolation 行的值为 "branch"
-  确认 verify_mode 行的值为 "light"
-  确认 verify_result 行的值为 "pending"
-  确认 verified_at 行的值为 "null"
-  确认 archived 行的值为 "false"
-  如任一字段不匹配，重试写入后再次验证。最多重试 2 次，仍失败则报告错误并终止。
+```bash
+bash "$COMET_STATE" init <name> hotfix
+```
 
 ### 2. 直接构建（preset build）