npx skills add https://github.com/boshu2/agentops --skill trace快速参考: 通过 CASS 会话、交接文档、git 和工件追溯设计决策。输出:
.agents/research/YYYY-MM-DD-trace-*.md
你必须执行此工作流程。不要仅仅描述它。
对于知识工件谱系(学习、模式、层级),请改用 /provenance。
CLI 依赖项: cass(会话搜索)。如果 cass 不可用,则跳过转录本搜索,依赖 git log、交接文档和 .agents/ 工件进行决策追溯。
给定 /trace <概念>:
确定要追溯何种来源:
IF 目标是文件路径(包含 "/" 或 "."):
→ 使用 /provenance(工件谱系)
IF 目标是 git 引用(sha、分支、标签):
→ 使用基于 git 的追溯(步骤 2b)
ELSE(关键词/概念):
→ 使用设计决策追溯(步骤 2a)
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
启动 4 个并行搜索代理(CASS、Handoff、Git、Research)并等待所有完成。
后端: 代理使用 Task(subagent_type="Explore"),该类型在 OpenCode 中映射到 task(subagent_type="explore")。有关共享契约,请参阅 skills/shared/SKILL.md("运行时原生衍生后端选择")。
代理定义和提示词请阅读 references/discovery-patterns.md。
基于 git 的追溯命令请阅读 references/discovery-patterns.md。
将所有来源的结果合并到一个按时间顺序排列的时间线中(最旧优先)。对同一天/同一会话的事件进行去重。每个声明都需要有来源引用。
对于时间线中的每个事件,识别:
写入位置: .agents/research/YYYY-MM-DD-trace-<概念-短名称>.md
完整报告格式和去重规则请阅读 references/report-template.md。
告知用户:
如何处理以下情况请阅读 references/edge-cases.md:无 CASS 结果、无交接文档、模糊概念(>20 个结果)以及所有来源为空的情况。一般原则:继续使用剩余来源,并在报告中注明缺失部分。
.agents/research/ 工件| 技能 | 目的 | 输入 | 输出 |
|---|---|---|---|
/provenance | 工件谱系 | 文件路径 | 层级/晋升历史 |
/trace | 设计决策 | 概念/关键词 | 演变时间线 |
使用 /provenance 用于:"这个学习成果从何而来?" 使用 /trace 用于:"我们是如何决定采用这种架构的?"
# 追溯一个设计决策
/trace "three-level architecture"
# 追溯一个角色/概念
/trace "Chiron"
# 追溯一个模式
/trace "brownian ratchet"
# 追溯一个功能
/trace "parallel wave execution"
用户说: /trace "agent team protocol"
发生的情况:
.agents/research/2026-02-13-trace-agent-team-protocol.md,包含完整时间线和引用结果: 完整的演变时间线,展示了代理团队协议在 7 个会话中如何发展,并附有来源引用。
用户说: /trace abc1234
发生的情况:
git log --grep 查找相关工作.agents/ 以查找同期研究/计划结果: 追溯报告将提交与来自周围工件的更广泛设计上下文联系起来。
| 问题 | 原因 | 解决方案 |
|---|---|---|
| CASS 无返回结果 | 会话搜索未安装或查询过于具体 | 检查 which cass。如果缺失,则跳过 CASS,依赖交接文档/git/研究。尝试更广泛的查询词。 |
| 时间线存在空白 | 并非所有决策都在可搜索的工件中记录 | 在报告中注明空白。建议采访团队成员或检查 Slack/邮件存档以获取缺失的上下文。 |
| 结果过多(>50 个匹配项) | 概念非常宽泛或高频术语 | 阅读 references/edge-cases.md 了解模糊概念的处理方法。缩小查询范围或按日期范围过滤。要求用户提供更具体的方面进行追溯。 |
| 空的追溯报告(所有来源都失败) | 概念确实未记录或拼写错误 | 验证拼写。尝试同义词。向用户报告:"未找到记录的历史。这可能是一个新概念,或者可能需要不同的搜索词。" |
每周安装次数
216
仓库
GitHub 星标数
198
首次出现
2026年2月2日
安全审计
安装于
opencode214
codex211
github-copilot210
gemini-cli210
amp207
kimi-cli207
Quick Ref: Trace design decisions through CASS sessions, handoffs, git, and artifacts. Output:
.agents/research/YYYY-MM-DD-trace-*.md
YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.
For knowledge artifact lineage (learnings, patterns, tiers), use /provenance instead.
CLI dependencies: cass (session search). If cass is unavailable, skip transcript search and rely on git log, handoff docs, and .agents/ artifacts for decision tracing.
Given /trace <concept>:
Determine what kind of provenance to trace:
IF target is a file path (contains "/" or "."):
→ Use /provenance (artifact lineage)
IF target is a git ref (sha, branch, tag):
→ Use git-based tracing (Step 2b)
ELSE (keyword/concept):
→ Use design decision tracing (Step 2a)
Launch 4 parallel search agents (CASS, Handoff, Git, Research) and wait for all to complete.
Backend: Agents use Task(subagent_type="Explore") which maps to task(subagent_type="explore") in OpenCode. See skills/shared/SKILL.md ("Runtime-Native Spawn Backend Selection") for the shared contract.
Read references/discovery-patterns.md for agent definitions and prompts.
Read references/discovery-patterns.md for git-based tracing commands.
Merge results from all sources into a single chronological timeline (oldest first). Deduplicate same-day/same-session events. Every claim needs a source citation.
For each event in timeline, identify:
Write to: .agents/research/YYYY-MM-DD-trace-<concept-slug>.md
Read references/report-template.md for the full report format and deduplication rules.
Tell the user:
Read references/edge-cases.md for handling: no CASS results, no handoffs, ambiguous concepts (>20 results), and all-sources-empty scenarios. General principle: continue with remaining sources and note gaps in the report.
.agents/research/ artifact| Skill | Purpose | Input | Output |
|---|---|---|---|
/provenance | Artifact lineage | File path | Tier/promotion history |
/trace | Design decisions | Concept/keyword | Timeline of evolution |
Use /provenance for: "Where did this learning come from?" Use /trace for: "How did we decide on this architecture?"
# Trace a design decision
/trace "three-level architecture"
# Trace a role/concept
/trace "Chiron"
# Trace a pattern
/trace "brownian ratchet"
# Trace a feature
/trace "parallel wave execution"
User says: /trace "agent team protocol"
What happens:
.agents/research/2026-02-13-trace-agent-team-protocol.md with full timeline and citationsResult: Complete evolution timeline showing how agent team protocol developed across 7 sessions with source citations.
User says: /trace abc1234
What happens:
git log --grep to find related work.agents/ for contemporary research/plansResult: Trace report links commit to broader design context from surrounding artifacts.
| Problem | Cause | Solution |
|---|---|---|
| CASS returns no results | Session search not installed or query too specific | Check which cass. If missing, skip CASS and rely on handoffs/git/research. Try broader query terms. |
| Timeline has gaps | Not all decisions documented in searchable artifacts | Note gaps in report. Suggest interviewing team members or checking Slack/email archives for missing context. |
| Too many results (>50 matches) | Very broad concept or high-frequency term | Read references/edge-cases.md for ambiguous concept handling. Narrow query or filter by date range. Ask user for more specific aspect to trace. |
| Empty trace report (all sources failed) | Concept genuinely undocumented or typo | Verify spelling. Try synonyms. Report to user: "No documented history found. This may be a new concept or may need different search terms." |
Weekly Installs
216
Repository
GitHub Stars
198
First Seen
Feb 2, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode214
codex211
github-copilot210
gemini-cli210
amp207
kimi-cli207
agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试
140,500 周安装