← ClaudeAtlas

inquiry-graphlisted

追問圖 — a question-graph harness over the user's Obsidian vault (`inquiry/`). Every question the user asks an AI becomes a node; follow-ups anchor to a specific atom of the parent answer; the question stack (the "return address") is printable; closing a node requires the user's own restatement, which is back-propagated to the parent and up to the root's big picture; cross-tree links the user did not notice are proposed for ratification and drawn on Obsidian canvases. Use whenever the user asks a conceptual or technical question they want recorded, says part of an answer is unclear ("A3 不懂", "P1 是什麼", "這裡不懂", "我不知道哪裡不懂"), asks where they are in a chain of follow-ups ("/where", "我問到哪了", "回到大問題"), wants to close a question ("/resolve", "懂了,收掉這題"), asks whether questions connect ("/weave", "這跟之前問的有關嗎"), or wants the canvas regenerated ("/map"). Trigger on "/ask", "/where", "/resolve", "/weave", "/map", "追問", "追問圖", "記進追問圖", "連回大圖", "先不追". Do NOT trigger for ordinary coding work — only when the user invokes a comman
yapeepee/agent-harnesses · ★ 1 · AI & Automation · score 59
Install: claude install-skill yapeepee/agent-harnesses
# Inquiry Graph — 追問圖 · questions as an anchored graph, big picture by backprop v1.0.2 (2026-09-05; core v1.0 2026-08-22). The user's long-standing failure with AI answers decomposes into three independent faults, and this harness is one mechanism per fault: | fault | mechanism | artefact | |---|---|---| | **定位失敗** — "I know I don't understand, but I can't point at *what*" | **atom protocol**: every answer is cut into addressable atoms `A1…` and the premises it *assumes* are listed as `P1…` | `## 回答` = 直答 + 原子 + 假設你已經懂 + 邊界 | | **堆疊遺失** — follow-ups go depth-first, the return address is lost, unfollowed siblings are forgotten | **anchored edges + `/where` + restatement backprop** | `parent`/`anchor` frontmatter; `## 子問題回流` on the parent; `## 大圖` on the root | | **跨樹盲區** — two big questions touch the same mechanism and the user never sees it | **concept layer + `/weave` proposals** the user ratifies | `## AI 提案連結` callouts; purple `?` edges on the canvas | The one design change from the user's original sketch: the *graph* was the sketch's centrepiece, but fault 1 happens **before** any graph can help — an answer without handles gives edges nothing to anchor to. So the first component is the answer protocol (`references/answer-protocol.md`); the canvas only draws the anchors it produces. The failure modes this harness is engineered against: **the answer without handles**, and **the depth-first walk without a stack**. Every rule below serves one of the two. Session scope: v