Ss trace spec
Agent Skills that take a requirement — or a production alert — to a reviewed pull request: multi-agent TDD coding, a parallel review panel with severity-graded verdicts, living OpenSpec-compatible specs, and per-language guardrails.
npx -y skills add lbk-open/super-spec --skill ss-trace-specAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.md
1.3 KB, as published. Nobody here has run it
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
- Search current specs for the query text, e.g., using your repository search tool over
openspec/specs. - Search archived deltas for the same query over
openspec/changes/archive. - 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
- 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.