openspec-traceability

仓库创建 2026年7月28日最近提交 7 小时前SkillHot 收录 1 小时前

▸ 精选理由

为跨文档追踪提供稳定键，弥补 OpenSpec 缺失的持久标识。

▸ 风险提示

会在仓库中写入 ID 注释与追溯文件，需写入权限。

这个 Skill 做什么

为要求分配稳定 ID，生成可追溯矩阵和机器可读证据日志。

为没有持久 ID 的 OpenSpec 需求分配稳定标识，生成 TRACEABILITY.md 的可追溯矩阵并产出机器可读的 EVIDENCE.json 日志。通常在需要把 OpenSpec 规范、GSD 计划、Git 等多类工件串起来做追踪或审计时用到。它唯一被允许写入 openspec/，但只会加一行不可见的 HTML 注释 ID，绝不改动需求正文。

▸ 展开 SKILL.md 英文原文

Assigns and maintains stable requirement/scenario IDs that OpenSpec has no native concept of, then generates the TRACEABILITY.md matrix and the machine-readable EVIDENCE.json log. The one skill in this capability permitted to write inside openspec/ — and only ever to add an inert HTML-comment ID line, never to touch requirement text.

开发编程可追溯性ID分配证据记录通用

Stars

Forks

仓库内 Skill

积累中

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/mshegolev/gsd-openspec-integration/main/capabilities/openspec/skills/openspec-traceability/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/mshegolev/gsd-openspec-integration/main/capabilities/openspec/skills/openspec-traceability/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

## Purpose

Everything else in this capability keys off stable IDs, and OpenSpec identifies requirements only by heading text (verified: `openspec show`/`validate --json` expose `requirementCount` and `requirements[]`, but no persistent identifier). This skill supplies that missing layer additively, then uses it to join five otherwise-disconnected artifact families — OpenSpec specs, GSD plans, git diffs, tests, evidence — into one matrix.

## Invocation conditions

- Automatically as part of `openspec-audit` in `standard` mode and above.
- Automatically at `discuss:post` time, indirectly: the `discuss-post` fragment refuses to invent IDs itself and flags `ids_pending: true` in `OPENSPEC-LINK

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有