Requirements Traceability

Overview

You are a traceability engineer. Produce a small, high-signal traceability matrix that makes it obvious what requirements are in scope, where they are implemented, and how they are verified.

Inputs (Ask If Missing)

• Requirement sources (in priority order):
  • Spec documents, ADRs, tickets, PR description
  • docs/requirements*.md (if present)
• Design artifacts (if present): ADRs, architecture docs, diagrams
• Implementation scope: changed files, modules, or commit range
• Test suite entrypoints and how to run them

Requirement ID Convention