@rpamis/comet 0.1.6 → 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
 
@@ -56,17 +41,13 @@ design-doc: docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md
 
 ### 2. Update Plan Status
 
-Merge and update the following fields in `openspec/changes/<name>/.comet.yaml` (keep other fields unchanged):
+Record plan path:
 
-```yaml
-phase: build
-plan: docs/superpowers/plans/YYYY-MM-DD-feature.md
+```bash
+bash "$COMET_STATE" set <name> plan docs/superpowers/plans/YYYY-MM-DD-feature.md
 ```
 
-【Write verification】After update completion, must verify:
-  cat openspec/changes/<name>/.comet.yaml
-  Confirm plan line value is "docs/superpowers/plans/YYYY-MM-DD-feature.md"
-  If not matching, retry write then verify again. Maximum 2 retries, report error and terminate if still fails.
+No manual phase update needed — guard auto-transitions when exit conditions are met.
 
 ### 3. Workspace Isolation
 
@@ -81,27 +62,14 @@ 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, merge and update `isolation` in `openspec/changes/<name>/.comet.yaml` (keep other fields unchanged). `isolation` only allows one of the following values:
-
-- `branch`
-- `worktree`
+After user selection, update `isolation` field. `isolation` only allows one of the following values:
 
-Few-shot examples:
-
-```yaml
-# User selects create branch / A
-isolation: branch
-```
-
-```yaml
-# User selects create worktree / B
-isolation: worktree
+```bash
+bash "$COMET_STATE" set <name> isolation <value>
 ```
 
-【Write verification】After update completion, must verify:
-  cat openspec/changes/<name>/.comet.yaml
-  Confirm isolation line value is "<branch or worktree>"
-  If not matching, retry write then verify again. Maximum 2 retries, report error and terminate if still fails.
+- `branch`
+- `worktree`
 
 **Execute isolation**:
 
@@ -124,29 +92,16 @@ 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, merge and update `build_mode` in `openspec/changes/<name>/.comet.yaml` (keep other fields unchanged). `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`
 - `direct` (only for hotfix preset use)
 
-Few-shot examples:
-
-```yaml
-# User selects robust mode / A
-build_mode: subagent-driven-development
-```
-
-```yaml
-# User selects fast mode / B
-build_mode: executing-plans
-```
-
-【Write verification】After update completion, must verify:
-  cat openspec/changes/<name>/.comet.yaml
-  Confirm build_mode line value is "<subagent-driven-development or executing-plans or direct>"
-  If not matching, retry write then verify again. Maximum 2 retries, report error and terminate if still fails.
-
 Then, **immediately execute:** Use the Skill tool to load the corresponding skill. Skipping this step is prohibited.
 
 If the selected Superpowers skill is unavailable, stop the process and prompt to install or enable the corresponding skill. Do not substitute this step with normal conversation.
@@ -183,18 +138,13 @@ When the initial spec is found incomplete during implementation, handle by scale
 - `.comet.yaml` `phase` updated to `verify`
 - **Phase guard**: Run `bash $COMET_GUARD <change-name> build`, allow transition only after all PASS
 
-Before exit, merge and update the following fields in `.comet.yaml` (keep other fields unchanged):
+Before exit, run guard to auto-transition:
 
-```yaml
-phase: verify
-verify_result: pending
+```bash
+bash $COMET_GUARD <change-name> build --apply
 ```
 
-【Write verification】After update completion, must verify:
-  cat openspec/changes/<name>/.comet.yaml
-  Confirm phase line value is "verify"
-  Confirm verify_result line value is "pending"
-  If any field does not match, retry write then verify again. Maximum 2 retries, report error and terminate if still fails.
+State file is automatically updated to `phase: verify`, `verify_result: pending`.
 
 ## Automatic Transition
 

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
 
@@ -66,18 +50,17 @@ After the skill loads, follow its guidance to produce:
 
 ### 2. Update Comet State
 
-Merge and update the following fields in `openspec/changes/<name>/.comet.yaml` (keep other fields unchanged):
+Record design_doc path, then run guard to auto-transition:
+
+```bash
+# Record design_doc path
+bash "$COMET_STATE" set <name> design_doc docs/superpowers/specs/YYYY-MM-DD-topic-design.md
 
-```yaml
-phase: build
-design_doc: docs/superpowers/specs/YYYY-MM-DD-topic-design.md
+# Auto-transition to next phase
+bash $COMET_GUARD <change-name> design --apply
 ```
 
-【Write verification】After update completion, must verify:
-  cat openspec/changes/<name>/.comet.yaml
-  Confirm phase line value is "build"
-  Confirm design_doc line value is "docs/superpowers/specs/YYYY-MM-DD-topic-design.md"
-  If any field does not match, retry write then verify again. Maximum 2 retries, report error and terminate if still fails.
+State file is updated automatically. No manual editing of other fields required.
 
 ### 3. Dual Spec Division of Labor
 

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
 
@@ -57,53 +43,14 @@ openspec/changes/<name>/
 └── tasks.md          # Task checklist (checkboxes)
 ```
 
-### 2b. Incrementally Modify Existing Capability (Optional)
-
-**Trigger condition:** proposal.md mentions modifying an existing capability, or user explicitly requests incremental modification.
-
-**Applicable scenario:** Incremental modification to archived functionality (not a brand-new capability).
+### 3. Initialize Comet State
 
-When proposal.md goals involve modifying an existing capability:
-1. Check if `openspec/specs/<capability>/spec.md` main spec already exists
-2. If it exists, copy the main spec as a delta spec baseline:
+Initialize Comet state file:
 
 ```bash
-mkdir -p openspec/changes/<name>/specs/<capability>/
-cp openspec/specs/<capability>/spec.md openspec/changes/<name>/specs/<capability>/spec.md
+bash "$COMET_STATE" init <name> full
 ```
 
-3. In the copied delta spec, organize changes in delta format (`## ADDED`, `## MODIFIED`, `## REMOVED`)
-4. Note in proposal.md: `based on existing capability: <capability-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
-```
-
-【Write verification】After creation, must verify:
-  cat openspec/changes/<name>/.comet.yaml
-  Confirm workflow line value is "full"
-  Confirm phase line value is "design"
-  Confirm design_doc line value is "null"
-  Confirm plan line value is "null"
-  Confirm build_mode line value is "null"
-  Confirm verify_mode line value is "null"
-  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.
-
 ### 4. Content Completeness Check
 
 Confirm the three documents have complete content:

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,65 +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:
-
-| 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
-```
+Execute scale assessment:
 
-```yaml
-# Any metric hits "large"
-phase: verify
-verify_mode: full
-verify_result: pending
+```bash
+bash "$COMET_STATE" scale <name>
 ```
 
-【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.
+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)
 
@@ -142,20 +101,13 @@ After the skill loads, follow its guidance to complete. Branch handling options:
 - `.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):
+Before exit, run guard to auto-transition:
 
-```yaml
-phase: archive
-verify_result: pass
-verified_at: YYYY-MM-DD
+```bash
+bash $COMET_GUARD <change-name> verify --apply
 ```
 
-【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.
+State file is automatically updated to `phase: archive`, `verify_result: pass`, `verified_at: YYYY-MM-DD`.
 
 ## Automatic Transition
 

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` 的产物要求补齐缺失文件 |
 
@@ -161,7 +161,7 @@ archived: false
 
 ### 脚本定位
 
-Comet 阶段守卫脚本 `comet-guard.sh` 随 skill 包分发，位于 `comet/scripts/` 目录。
+Comet 阶段守卫脚本 `comet-guard.sh` 和归档脚本 `comet-archive.sh` 随 skill 包分发，位于 `comet/scripts/` 目录。
 **不硬编码平台路径**，运行时通过以下命令自定位：
 
 ```bash
@@ -169,6 +169,25 @@ 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
+bash "$COMET_GUARD" <change-name> <phase> --apply
+```
+
+**归档脚本**：一键完成归档全部步骤：
+
+```bash
+COMET_ARCHIVE=$(find . -path '*/comet/scripts/comet-archive.sh' -type f -print -quit)
+bash "$COMET_ARCHIVE" <change-name>
+```
+
 后续文档中 `bash $COMET_GUARD <change> <phase>` 均指此命令。加载 comet 后，agent 应在 shell 环境中缓存 `COMET_GUARD` 路径，避免重复 `find`。
 
 ### 文件结构
@@ -185,7 +204,7 @@ openspec/                              # OpenSpec — WHAT
 │   │   ├── specs/<capability>/spec.md # Delta 能力规格
 │   │   └── tasks.md                   # 任务清单
 │   └── archive/YYYY-MM-DD-<name>/     # 已归档
-└── specs/<capability>/spec.md         # 主 specs（归档时从 delta 同步）
+└── specs/<capability>/spec.md         # 主 specs（归档时从 delta 覆盖）
 
 docs/superpowers/                      # Superpowers — HOW
 ├── specs/YYYY-MM-DD-<topic>-design.md # 设计文档（技术 RFC，归档时标注状态）
@@ -202,5 +221,5 @@ docs/superpowers/                      # Superpowers — HOW
 6. **增量更新分级** — 小编辑、中重 brainstorming、大新 change
 7. **Plan 必须关联 change** — 文件头包含 `change:` 和 `design-doc:` 元数据
 8. **归档闭环** — design doc 和 plan 必须标注 `archived-with` 状态
-9. **增量修改已有功能** — 基于 main spec 创建 delta spec 基线，不从零编写
+9. **增量修改已有功能** — 直接 open 新 change，brainstorming 会读取已有 main spec 作为上下文
 10. **Preset 有上限** — hotfix/tweak 满足升级条件时及时切换到完整流程