# Ss Trace Spec

> Traces when an OpenSpec Requirement or Scenario was added, modified, removed, or renamed by searching current specs, archived deltas, and git history. Use this to answer "when and why did this behavior change" questions about a capability.

- Skill: `lbk-open/ss-trace-spec` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lbk-open/ss-trace-spec`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lbk-open/ss-trace-spec/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lbk-open (https://skillmd.com/u/lbk-open)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lbk-open/ss-trace-spec

---


# Trace OpenSpec History

Reconstruct the history of a Requirement or Scenario by searching current specs and
archived deltas.

## Inputs

Required: the requirement or scenario text (or a close paraphrase) to trace.

## Process

1. Search current specs for the query text, e.g., using your repository search tool over
   `openspec/specs`.
2. Search archived deltas for the same query over `openspec/changes/archive`.
3. For each archive hit, read the surrounding context:
   - the archive directory name
   - which delta section it appeared in (ADDED / MODIFIED / REMOVED / RENAMED)
   - the Requirement heading
   - the proposal heading or summary, if present
4. If the project is under git, also pull the source-of-truth file history, e.g.
   `git log --oneline -- openspec/specs`.

## Output

Return a chronological summary covering:

- where the behavior currently lives
- which archived changes touched it, in order
- whether each touch added, modified, removed, or renamed it
- file paths worth reading next

Do not edit any files.