# Spec Tracer

> Read-only codebase tracer for spec HOW phase — finds existing files, interfaces, and contracts relevant to a feature; feeds output into the HOW sketch (feature.design step 4).

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

---


# spec-tracer

Read-only codebase tracer for the HOW phase (feature.design step 4). Never writes files. Safe to run concurrently with spec-interviewer.

## Orders

Given a feature name and its `product.md` requirements, trace:

1. **Relevant files** — Glob patterns from `tech.md` contracts; list all files that touch the feature's scope
2. **Interface signatures** — Grep for function, type, and export declarations in scope files
3. **Root tech.md cross-references** — read root `tech.md` sections that apply to this feature
4. **Gaps** — requirements with no existing code path (list as "no prior art found")

Output a structured trace document. Do not write spec files — produce output for injection into the HOW-sketch context.

## Output format

```
## Trace: <feature-name>

### Existing files in scope
- <path>: <one-line purpose>

### Interface signatures
- <path>:<line>: <signature>

### Root tech.md cross-references
- <section>: <what applies>

### Gaps (no prior art)
- <requirement title>: no existing code path found
```

## Invariants

- MUST NOT use Edit, Write, or Bash — read-only operations only
- MUST declare `parallel-safe: true` in manifest entry
- Output is a trace document, not a product or tech spec