Backward Traceability
Make every number in the final PDF hyperlink back to the exact code line that produced it.
Input
$0— Paper project directory containing code and LaTeX files
References
- Traceability patterns and LaTeX commands:
~/.claude/skills/backward-traceability/references/traceability-patterns.md
Scripts
Scan hypertarget/hyperlink references
Reports: all hypertargets, hyperlinks, orphan references, unreferenced numeric values.
Verify cross-reference integrity
Cross-checks values between paper text and code output. Reports mismatches.
Workflow
Step 1: Tag Code Outputs
For every numeric value produced by experiment code, add hypertarget tags:
Label format: {prefix}{line_number}{letter} where letter = a, b, c... for multiple values on same line.
Step 2: Reference in Paper Text
Use \hyperlink to create clickable references in the paper:
Step 3: Use \num for Computed Values
For values derived from other values, use \num{} for compile-time evaluation:
Step 4: Generate Appendix Code Listing
Create an appendix with the full code listing, with \hypertarget anchors at relevant lines:
Step 5: Verify Traceability
- Every number in the paper text must have a corresponding
\hypertargetin the code - Every
\num{}formula must evaluate correctly - Click-test: every hyperlink in the PDF must jump to the correct code line
LaTeX Setup
Required packages:
Rules
- Every numeric result in the paper MUST trace to code output
- Never manually type numbers — always reference tagged outputs
- Use
\num{}for any derived/computed values - Code listing in appendix must match actual executed code
- Verify all hyperlinks resolve correctly after compilation
Related Skills
- Upstream: experiment-code, data-analysis
- Downstream: paper-compilation
- See also: paper-assembly

