[chore] 4 specs still carry the TBD Purpose archive-stub (idd-all-chain, idd-ic-r011-checkpoint, idd-spawn-manifest, idd-worktree-isolation)

[kiki830621]

Problem

4 specs in openspec/specs/ still carry the literal Spectra archive-stub Purpose:

TBD - created by archiving change ''. Update Purpose after archive.

This is the exact opacity bug just fixed for idd-orchestrator-modes (renamed → idd-pr-hitl-modes + real Purpose; commit b6fd718, v2.76.1). The stub is opaque on sight — a reader cannot tell what the spec governs ("modes of what?").

Spec	Stub origin (source change)
idd-all-chain	add-idd-all-chain-skill
idd-ic-r011-checkpoint	idd-ic-r011-default-file
idd-spawn-manifest	add-idd-all-chain-skill
idd-worktree-isolation	idd-worktree-isolation

Audit note: append-vs-modify-discipline showed up in the grep but is a false positive — its Purpose is real ("Defines the action-scoped modify discipline…"); the word "TBD" just appears in the body. NOT in scope.

Root Cause

Spectra archive materializes a new capability from a delta that has no ## Purpose (Purpose is not in the delta schema), so it writes the TBD … Update Purpose after archive stub and relies on a human to fill it later — with zero enforcement. Nobody filled these 4.

Proposed Solution

Mechanical, doc-only, zero behavior change — same move as the idd-pr-hitl-modes fix: give each of the 4 specs a real, intent-revealing one-sentence Purpose stating what the capability governs. Direct edit of each openspec/specs/<name>/spec.md Purpose section (the delta model cannot express a pure Purpose-fill — see Prevention).

Scope boundary (this is NOT "spec every skill")

Purpose-quality only, NOT spec-coverage. We are explicitly NOT speccing every idd skill — that is over-spec (per idd-diagnose Step 3.5 Layer 1: Plan/Spectra is dead weight for prose / no-external-contract skills). Skills like idd-comment / idd-config / idd-report / idd-edit being prose-only is correct, not a gap. This issue touches ONLY the Purpose text of specs that already exist.

Prevention (structural pairing)

This issue is the backlog (pre-existing stubs). The structural prevention (have archive/validate lint/flag any spec whose Purpose is still the TBD-stub, so promoted specs cannot silently ship opaque) was raised upstream as an inquiry to the Spectra maintainers: kaochenlong/spectra-app#100 — framed as questions, since Spectra is a closed app and this is a behavioral observation against spectra 2.3.1, not verified against source. (Note: the in-app spectra feedback CLI turned out to be a local echo pointing to a dead URL; the live repo is kaochenlong/spectra-app, not the kaochenlong/Spectra the binary prints.) If/when such a lint lands, no new stubs can appear; these 4 are the pre-lint backlog.

Success Criteria

• All 4 specs above have a real Purpose (no TBD … Update Purpose after archive string remains in any openspec/specs/*/spec.md).
• grep -rl "Update Purpose after archive" openspec/specs/ returns empty.
• No behavior change; no requirement deltas.

Source: surfaced during /idd-diagnose #164 + /spectra-discuss (naming + Purpose lesson; sister of the idd-orchestrator-modes → idd-pr-hitl-modes rename, commit b6fd718)

---

Current Status

Phase: closed
Last updated: 2026-06-01 by idd-close

Key Decisions

• Filled TBD-stub Purpose for 3 specs (idd-all-chain / idd-spawn-manifest / idd-worktree-isolation) — intent-revealing one-paragraph Purpose naming capability + key Requirements. d7ea0a9.
• Scope收斂 4 → 3（idd-ic-r011-checkpoint folded via [chore] git hygiene — 3 pre-existing dirty items pollute cluster PRs (surfaced via #137 tangential sweep) #152）→ 全 repo TBD-stub backlog 清空（0 殘留）.
• Complexity: Simple (doc-only). Verify: light PASS.

Scope Changes

• (none)

Blocking

• (none)

Commits

• d7ea0a9 chore: fill TBD-stub Purpose for 3 specs ([chore] 4 specs still carry the TBD Purpose archive-stub (idd-all-chain, idd-ic-r011-checkpoint, idd-spawn-manifest, idd-worktree-isolation) #180)

Verification

• PASS (light) — grep 0 residual stub; zero normative drift. Closed with full closing summary. Root-cause prevention is upstream (請教：spec delta 是否支援 capability 改名、填 Purpose，以及偵測未填的 TBD Purpose？ kaochenlong/spectra-app#100).

[kiki830621]

Update: idd-ic-r011-checkpoint is now resolved via #152 — its Purpose was filled and the previously-untracked spec committed (de73444). This backlog narrows to the remaining 3 tracked TBD-stub specs: idd-all-chain, idd-spawn-manifest, idd-worktree-isolation.

[kiki830621]

Diagnosis

Type

chore（doc-only spec Purpose 填補）

Analysis

Issue body 已含完整 Problem / Root Cause / Proposed Solution，本 comment 僅補 formal verdict + scope 確認。

Scope 確認（已收斂）：原 body 列 4 specs，但 idd-ic-r011-checkpoint 已於 #152 填好 Purpose + commit（de73444）。grep 現況確認剩 3 specs 帶 TBD stub：

• idd-all-chain — 治理 chain-solve orchestration（root + auto-emergent spawn → 1 cluster branch + 1 PR）
• idd-spawn-manifest — 治理 cross-skill spawn manifest（append-only、atomic、versioned schema、4 sub-skill conformant write）
• idd-worktree-isolation — 治理 managed git-worktree lifecycle（issue-keyed、create/cleanup/list、PR convergence、idd-close auto-GC、staging isolation）

Strategy

• idd-all-chain/spec.md — 填 intent-revealing Purpose（依 5 個 Requirement 歸納）
• idd-spawn-manifest/spec.md — 填 Purpose（依 4 個 Requirement）
• idd-worktree-isolation/spec.md — 填 Purpose（依 7 個 Requirement）
• grep 驗收：openspec/specs/ 0 殘留 TBD - created by archiving stub（排除 append-vs-modify false positive）

Complexity

Simple

• Layer 1 命中：deliverable 是更新既有 prose、零 behavior change（doc restructure）→ 強制 Simple。
• 無新對外 surface、無 decision space（每個 Purpose 由該 spec 自己的 Requirements 機械歸納）→ 非 Plan / 非 Spectra。同 idd-pr-hitl-modes（b6fd718）/ idd-ic-r011-checkpoint（[chore] git hygiene — 3 pre-existing dirty items pollute cluster PRs (surfaced via #137 tangential sweep) #152）先例。

Risks

• Purpose 寫得太空泛（「modes of what」式 opacity 重演）→ mitigate：每句 Purpose 必須點名「治理什麼 capability + 關鍵 Requirements」，不只複述 spec 名。

Residue

(none) — 純機械 doc 填補，完全可 operationalize。

Next: /idd-implement #180

[kiki830621]

Implementation Complete

Checklist (synced from TaskList)

• idd-all-chain/spec.md — Purpose: chain-solve orchestration（root + auto-emergent spawn → 1 cluster branch + 1 PR；eligibility / verify-halt / forest-tree report）→ d7ea0a9
• idd-spawn-manifest/spec.md — Purpose: machine-readable append-only atomic manifest（fixed-path + versioned schema；4 sub-skill conformant write；供 idd-all-chain traversal）→ d7ea0a9
• idd-worktree-isolation/spec.md — Purpose: managed git-worktree lifecycle（issue-keyed、create/cleanup/list、PR convergence、idd-close auto-GC、staging isolation #941↔#942）→ d7ea0a9
• grep 驗收：openspec/specs/ 0 殘留 TBD - created by archiving stub

idd-close 會 refuse 關任何 checklist 還有 - [ ] 的 issue。

Changes

• d7ea0a9: chore — fill TBD-stub Purpose for 3 specs ([chore] 4 specs still carry the TBD Purpose archive-stub (idd-all-chain, idd-ic-r011-checkpoint, idd-spawn-manifest, idd-worktree-isolation) #180)

Files Changed

 openspec/specs/idd-all-chain/spec.md          | 2 +-
 openspec/specs/idd-spawn-manifest/spec.md     | 2 +-
 openspec/specs/idd-worktree-isolation/spec.md | 2 +-

Verification

Doc-only deliverable，無 unit test。驗收 = grep openspec/specs/ 0 殘留 stub（已綠），且每個 Purpose 點名 capability + 關鍵 Requirements（非空泛複述 spec 名 → 規避 opacity 重演）。

Scope Compliance

僅 3 個 spec.md 各 1 行 Purpose，全對應 strategy。非 plugin bundle 檔 → 無版本 bump、無 distribution sync。無 scope creep。

Next: verification pending

[kiki830621]

Verify (PASS) — light

Mode: light（doc-only Purpose fill、零 behavior change → full ensemble = dead weight per Layer 1）。Diff scope: 3 spec.md，各 +1/-1。

Acceptance

• ✅ 0 殘留 stub：grep -rl "TBD - created by archiving change" openspec/specs/ → 空。
• ✅ 每個 Purpose intent-revealing（非空泛）：3 句各點名 capability + 關鍵 Requirements（chain-solve orchestration / spawn manifest contract / worktree lifecycle），規避「modes of what」式 opacity 重演 —— 即 [chore] 4 specs still carry the TBD Purpose archive-stub (idd-all-chain, idd-ic-r011-checkpoint, idd-spawn-manifest, idd-worktree-isolation) #180 要修的本質。
• ✅ Scope：僅 Purpose 段，未動任何 Requirement / Scenario normative 內容（git show d7ea0a9 每檔僅 1 行變更）。

Findings

無 blocking、無 non-blocking。

Result: PASS — 3 specs 的 TBD-stub Purpose 全部填為 intent-revealing 一段式 Purpose，0 殘留，零 normative drift。

Next: /idd-close #180

[kiki830621]

Closing Summary

Problem

4 specs in openspec/specs/ 帶字面 Spectra archive-stub Purpose（TBD - created by archiving change '<X>'. Update Purpose after archive.）—— 一眼看不出該 spec 治理什麼（「modes of what」式 opacity），同 idd-orchestrator-modes 已修的 bug。

Root Cause

Spectra archive 從沒有 ## Purpose 的 delta materialize 新 capability（Purpose 不在 delta schema 內），於是寫 TBD stub 並依賴人事後手填 —— 零 enforcement，沒人填這 4 個。詳見 upstream inquiry kaochenlong/spectra-app#100。

Solution

Mechanical、doc-only、零 behavior change（同 idd-pr-hitl-modes b6fd718 / idd-ic-r011-checkpoint #152 的手法）。其中 idd-ic-r011-checkpoint 已於 #152 折抵填好，本 issue 清掉剩餘 3：

• idd-all-chain — chain-solve orchestration（root + auto-emergent spawn → 1 cluster branch + 1 PR）
• idd-spawn-manifest — machine-readable append-only atomic manifest（4 sub-skill conformant write）
• idd-worktree-isolation — managed git-worktree lifecycle（concurrent-session isolation）

每句 Purpose 點名 capability + 關鍵 Requirements，規避空泛複述。

Verification

Light（doc-only）PASS：grep openspec/specs/ 0 殘留 stub；git show d7ea0a9 每檔僅 Purpose 1 行變更、零 normative drift。

Changes

• d7ea0a9: chore — fill TBD-stub Purpose for 3 specs (idd-all-chain, idd-spawn-manifest, idd-worktree-isolation) ([chore] 4 specs still carry the TBD Purpose archive-stub (idd-all-chain, idd-ic-r011-checkpoint, idd-spawn-manifest, idd-worktree-isolation) #180)

Follow-ups / Residue

• 全 repo TBD-stub backlog 清空（4 → 0）。
• 根因 prevention 屬 upstream（kaochenlong/spectra-app#100：delta Purpose schema + archive Purpose-lint）—— 非本 repo 可修，已 file 給 Spectra 作者。