openspec-traceabilitylisted

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.
mshegolev/gsd-openspec-integration · ★ 0 · AI & Automation · score 73

Install: claude install-skill mshegolev/gsd-openspec-integration

## 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.md`; this skill is what clears that flag. - Directly, `/openspec-traceability`, to refresh the matrix after execution without a full audit. ## Required inputs - A change-id, or "all active changes" (default). - `.planning/openspec/id-registry.json` if it exists (created on first run). ## Files read - `openspec/changes/<change_id>/specs/**/spec.md`, `openspec/specs/**/spec.md` - `openspec/changes/<change_id>/tasks.md` (OpenSpec task numbering — `1.1`, `2.3`, …) - `.planning/phases/<NN>-<slug>/<NN>-OPENSPEC-LINK.md`, `<NN>-<PP>-PLAN.md`, `<NN>-<PP>-SUMMARY.md` - `<NN>-OPENSPEC-VERIFICATION.md` (per-requirement statuses — this skill never re-derives them) - Git log/diff for the phase's commits ## Files this skill may write - `openspec/**/spec.md` — **ID comment lines only.** This is th