feature: /idd-list blocked-state awareness output mode (anti-anxiety surfacing)

[kiki830621]

Problem

Original text (kiki830621 dogfood session, 2026-05-12, repo PsychQuantHsu/psychophysical_representations):

「『等』的狀態正確 surface 後就不再焦慮:7/7 open issues 全 blocked 在 collaborator reply 上,這不是 throughput 問題而是 alignment 問題。把它寫到 closing comment + announcement 後,『我們已經做完所有可控的事』這個資訊就被 explicit 紀錄,下次回來不會誤以為『沒進度』。」

— Source: academic repo dogfood session,/idd-list 結束時剩 7 open issues 全部 blocked-by Hsu reply 或 #17 unblock → user observation: explicit surface 「全部 actionable items are blocked」是 anti-anxiety feature

觀察到的 gap

當前 /idd-list Step 5(Suggest Next Actions)依 phase × PR state matrix 對每個 issue 給建議。但若整個 list 的 actionable suggestions 全部是 "wait for X"(blocked on external),user 看起來像「沒事可做」,易產生兩種誤判:

1. 「沒進度」焦慮:看不到下一步 actionable command,以為自己 stuck;實際上是「該 push 的都 push 了,等對方」
2. 「漏掉了什麼」反向找:user 反覆 scan 看哪個 issue 還沒做,浪費時間;實際應該是「下次回來等 reply」

Dogfood case 結束時 7/7 open issue:

Issue	Phase	Blocker
#16	diagnosed	waiting Hsu Path 1/2 clarify
#17	diagnosed	waiting Hsu Theorem 1 generalization confirm
#21	diagnosed	bundled with #16(同 blocker)
#26	(no phase)	blocked-by #17(soft)
#27	(no phase)	blocked-by #17(soft)
#28	(no phase)	blocked-by #26+#27(soft)
#29	(no phase)	blocked-by #26+#27+#28(soft)

→ 100% blocked-on-external。Plugin 該明示這個狀態,而非繼續對每個 issue 列「/idd-update #N 同步狀態」之類的 false-progress suggestion。

Type

feature

Expected

/idd-list 加 blocked-state awareness output mode:

A. Blocker 偵測

對每個 open issue 掃以下 signal,標記 blocker type:

Signal	Blocker type	偵測來源
Issue body 含 ## Current Status **Next**: 行有「wait」/「pending」/「waiting」/「blocked-by」/「等」	external-collaborator	Current Status block
Issue body 含 Blocked by #M blockquote(--blocked-by flag 留下的)	blocked-by-issue:#M	body scan
Issue body 含 ## Related 或 ## Acceptance criteria 行有「跟 #M 同 batch / 同 PR / 同步」	bundled-with:#M	body scan
Issue body diagnosis comment ### Risks 含「waiting for X reply / clarification」	external-collaborator	latest diagnose comment

B. Footer 加 Blocker Summary

當前 footer:

10 open issue(s) — 4 diagnosed, 6 (no phase)
0 open PR(s); all 10 issues are direct-commit path

新 footer(blocked-state aware):

10 open issue(s) — 4 diagnosed, 6 (no phase)
0 open PR(s); all 10 issues are direct-commit path

⚠ All 7 open issues are blocked:
  - 3 waiting for external collaborator reply (#16 #17 #21)
  - 4 blocked-by upstream issue (#26 #27 #28 #29 → unblocked by #17)
→ No self-actionable work right now. Suggested action: re-run /idd-list after collaborator replies.

C. Suggested next 改寫(under blocked condition)

每個 blocked issue 的 Suggested next 改為 → blocked on <blocker_type>: <description> 而非 /idd-update / /idd-diagnose 之類 false-progress command。

範例:

Suggested next:
  #16 [diagnosed] → blocked on external collaborator: Hsu Path 1/2 clarification
  #17 [diagnosed] → blocked on external collaborator: Hsu Theorem 1 generalization confirm
  #21 [diagnosed] → blocked on #16 unblock (bundled)
  #26 [no phase]  → blocked-by #17 (cascade chain via blocked-by metadata)
  ...
  
Actionable now: (none)

D. --actionable-only flag

新增 flag:/idd-list --actionable-only,filter out 所有 blocked issue,只顯示真正可動工的。空列表時顯示明確 message:

No actionable issues at the moment. All 7 open issues are blocked on external/upstream dependencies.

E. (Optional) Aggregate「等什麼」viewport

進階:/idd-list --waiting 把所有 blocker 按 type 聚合:

Waiting on:
  - Hsu Path 1/2 reply: #16 (blocks #21)
  - Hsu Theorem 1 confirm: #17 (blocks #26-#29 chain)

→ 2 distinct external responses needed to unblock 7 open issues.

幫 user 一眼看清「待辦對方」的清單。

Actual

當前 /idd-list(v2.59.0)的 Step 5 Suggest Next Actions 只依 phase × PR state matrix 給命令,不知道 blocked-state:

• diagnosed + no PR → suggest /idd-implement #N 即使 issue body 寫了 「waiting Hsu reply」
• (no phase) → suggest /idd-update #N 即使 issue 是 blocked-by-other-issue 的 sub-issue
• Footer 沒 aggregate blocked count

→ user 必須手動讀每個 issue 的 body 才能 figure out「真的能動的有哪些」。

Impact

Affected files:

• plugins/issue-driven-dev/skills/idd-list/SKILL.md(add Step 4.5 Blocker Detection + update Step 5 matrix + footer enhancement + new flags)
• plugins/issue-driven-dev/CHANGELOG.md
• plugins/issue-driven-dev/.claude-plugin/plugin.json(version bump)

Sister-of: [issue A — milestone-first SOP](待 file URL) — 兩者同源 dogfood session,合稱「IDD lifecycle visibility hardening」cluster

Acceptance criteria

• idd-list SKILL.md 含 Step 4.5「Blocker Detection」section(signal heuristics + classification)
• idd-list SKILL.md Step 5 matrix 加 blocked-state branch(優先於 phase × PR state)
• idd-list footer 含 Blocker Summary 區塊(觸發條件:≥50% open issues blocked → 自動加;否則隱藏)
• --actionable-only flag 支援
• --waiting flag 支援(aggregate viewport)
• Unit test: 給定一份 mock issue list(混合 blocked + actionable),驗證 output 正確 classify + suggest
• CHANGELOG entry + version bump
• Dogfood:在 PsychQuantHsu/psychophysical_representations 跑 /idd-list --actionable-only 應回「empty + 7 blocked」訊息

Related

• Sister(同 Insight 第 1 點): milestone-first SOP for cross-cluster tracking → filed as feature: milestone-first SOP for cross-cluster tracking (replace Epic issue anti-pattern) #83
• Dogfood source: same session(academic repo /idd-list 結束時觀察)

---

Source: surfaced during /idd-list dogfood in academic repo session 2026-05-12 (PsychQuantHsu/psychophysical_representations)