菜单
Synchronize graph backend index, structured memory, and entry docs with code after verification passes. Use when: verified code changes need graph index sync, memory updates, or entry documentation refresh.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Read-only cross-artifact consistency analysis after planning and before approval. Verifies that spec.md, requirements.json, plan.md, tasks/Tn.md, traceability.json are mutually consistent: no duplicate/ambiguous requirements, every behavior mapped to a task, no orphan tasks, no coverage gaps, no contradictions. Outputs artifact-analysis.json with coverage% and severity. CRITICAL/HIGH findings block the approval gate. Use when: planning produced plan.md + tasks + traceability.json, before the user approves the plan.
Explore 2-3 implementation options with trade-offs when the user describes a new feature or requirement. Use when: the user asks for a new feature design, implementation options, or technical trade-off analysis.
After implementation and before final verification, compare current code/tests against the intent inventory (requirements.json + traceability.json). Classify each requirement/behavior as covered, missing, partial, contradicts, or unrequested. Append missing/partial/contradicts as new tasks back to executing. Repeat until converged: zero blocker findings. Outputs convergence-report.json. Use when: executing produced test-report.md but before loom-verification-before-completion.
Expand each requirement into verifiable Behavior Obligations across 15 fixed dimensions (happy-path, boundary, invalid-input, authorization, state-transition, idempotency, concurrency, atomicity, external-failure, compatibility, security, performance, observability, recovery, forbidden-behavior) before planning. Use when: brainstorming produced requirements.json and spec is approved, but behaviors are still placeholders or only happy-path; before loom-writing-plans.
Read-only adversarial reviewer that looks for what SHOULD exist but doesn't, by cross-checking Behavior Obligations against code, tests, expected side effects, forbidden side effects, failure scenarios, and public API changes. Focuses on negative space: events that should not repeat, permissions that should not be bypassed, partial writes that should not happen, old APIs that should not change, swallowed exceptions, leaked secrets. Outputs findings.json. Use when: executing or converge needs an independent omission sweep.
Analyze user request + collect signals (file scope, keywords, worktree state, spec existence), then select pipeline steps via rule short-circuit / AI fallback / rule-based fallback. Select steps first, expose the choice to the user, and persist selected dynamic_steps only after explicit user confirmation; pipeline-plan.md is optional for manual review. Use when: user is unsure which pipeline type to pick, or wants AI to choose steps automatically.
| name | loom-index-update |
| description | Synchronize graph backend index, structured memory, and entry docs with code after verification passes. Use when: verified code changes need graph index sync, memory updates, or entry documentation refresh. |
| when_to_use | Sync graph backend, structured memory, and entry docs after verified code changes. |
| argument-hint | <spec_dir or sync scope> |
| user-invocable | true |
loom-verification-before-completion 已通过，或用户明确要求只同步图后端/记忆。git diff --name-only HEAD 确认变更文件。references/update-checklist.md 判断是否需要同步图后端或结构化记忆。先读取 .loom/graph.config.json 确认当前图后端；配置不存在时默认 codegraph（向后兼容）。
loom index # 同步当前图后端；后端不可用时跳过
loom index --check # 检查图后端状态；后端不可用时跳过
图后端可用时，AI 通过 loom 暴露的固定 MCP 工具按需查询（不直接调用后端专属工具名）：
loom_graph_status — 查询后端能力、新鲜度和可用性loom_graph_query — 统一图查询入口（capability：explore / definition / references / impact 等）loom_graph_sync — 同步或检查索引当后端是 codegraph 时，
loom_graph_*内部委派给codegraph_explore等 MCP 工具；AI 不需要也不应该直接引用codegraph_*工具名。
图后端不可用（后端为 none、marker 不存在或 freshness=unavailable）时，在报告中注明“图后端不可用，图索引同步跳过”，不中断流水线。
降级规则：
impact 时，用 references、explore 或源码搜索降级，并报告“影响范围可能不完整”。freshness 不是 fresh 时，不得直接把其结论作为阻断判断依据，需用当前源码和 git diff 校验关键结论。knowledge-base 时，不得用于精确调用链或 breaking change 影响范围判断。Memory 的单一真实来源是 .loom/memory/store.json。MEMORY.md 是 loom memory export 生成的只读视图，禁止手动编辑 MEMORY.md。
判断写入目标：
| 内容类型 | 写入方式 |
|---|---|
| 本次会话的关键结论（决策/踩坑/偏好/状态变更） | loom_add_memory 或 loom memory add --type <类型> --content "..." |
| 技术选型、架构决定，需要保留背景和原因 | type=adr，context 写背景和原因 |
| 实际遇到的坑，含根因和解决方式 | type=踩坑，content 写“问题 + 根因 + 解决方式” |
| 用户明确表达的工作习惯、风格偏好、禁止事项 | type=偏好 |
| 技术栈或当前阶段变化 | type=状态 |
| 本次会话有重要内容需要归档 | loom memory archive --slug <slug> --file <session.md> |
命令示例：
loom memory add --type 决策 --content "选择 codegraph 作为默认图后端"
loom memory export
会话归档规则：
loom memory archive --slug <feature-slug> --file <session.md> 写入归档。loom memory export。不写入的情况：
只有引入新约定、新命令、入口程序变化或开发流程调整时，才更新入口文件。一般性代码变更不更新。
报告模板见：
assets/report-graph-template.md（图后端可用，路径 A）assets/report-no-graph-template.md（图后端不可用，路径 B）freshness 不是 fresh 时以源码为准。loom index；图后端不可用时跳过，不生成任何 Markdown 索引。同步完成后输出报告；图后端不可用时必须明确注明已跳过。