requirements-traceability

A requirements-tracking tool that connects each acceptance criterion to its tasks, tests, changed code, and verification checks. Acceptance criteria are the specific conditions a feature must meet.

In plain words
What is it for?
Use it to build a traceability report, check whether every requirement is covered, find orphaned tests or code, and record which verification checks ran.
Why use it?
It reveals requirements that have no implementation or test, tests that do not trace back to a requirement, and changed code that lacks test coverage.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/loiane/specs-driven-development-spring-angular/requirements-traceability
Any agent
npx skills add loiane/specs-driven-development-spring-angular --skill requirements-traceability
Clone the repo
git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: Claude Code, Codex.

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 881 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00050 $0.00881
Opus 5 $0.00025 $0.00441
Sonnet 5 $0.00010 $0.00176
Haiku 4.5 $0.00005 $0.00088

Measured 3d ago against content hash 4061e631c1d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

requirements-traceability scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/requirements-traceability/SKILL.md · 95 lines

How it starts

The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Requirements traceability

What gets traced

For each AC-NNN from 01-spec.md:

  • The list of T-NNN tasks that implement it (04-tasks.md).
  • The list of test methods that assert it (@Tag("AC-NNN") or @DisplayName("AC-NNN: …")).
  • The list of production code symbols (FQ method names) touched by those tasks' diffs.
  • The list of harness gates that ran on those symbols.

For each test method:

  • The AC it claims to assert.
  • The task that introduced it.

For each production symbol changed in the diff:

  • At least one test that covers it (else flagged "orphan code").

Building the matrix

spring-validator runs .github/scripts/traceability.sh which:

  1. Greps 01-spec.md for **AC-NNN** headers → AC list.
  2. Greps 04-tasks.md for task entries with **AC-IDs:** → AC↔task mapping.
  3. Scans src/test/java/**/*.java for @Tag("AC-NNN") and @DisplayName("AC-NNN: …") → AC↔test mapping.
  4. Reads git diff --name-only origin/main...HEAD → changed files; intersects with JaCoCo's per-method coverage data → covered/uncovered symbols.
  5. Reads harness-summary.json → gates that ran.
  6. Emits 07a-traceability.md.

Required checks (all must pass)

  • No uncovered AC. Every AC-NNN appears in ≥1 test's @Tag or @DisplayName.
  • No orphan test. Every test method tagged AC-NNN references a real AC.
  • No orphan code. Every changed production method has ≥1 covering test.
  • No untraced task. Every T-NNN marked done in 04-tasks.md has a commit recorded.

Failures of any check → validator returns ❌.

Sample output (truncated)

## Coverage

| AC-ID | Tasks | Tests | Status |
|-------|-------|-------|--------|
| AC-001 | T-001, T-002 | ApplyGiftCardRequestTest#rejectsBlankCode, CheckoutControllerTest#happyPath | ✅ |
| AC-002 | T-003 | CheckoutServiceTest#redeemedCardRejected, CheckoutControllerIT#redeemed409 | ✅ |
| AC-003 | T-002 | CheckoutControllerTest#unknownCode404 | ✅ |
| AC-004 | T-004 | GiftCardRepositoryIT#balanceAcrossOrders | ✅ |

## Orphan tests

_None._

## Orphan code

_None._

## Verdict

✅ All ACs covered. No orphans.

Read the full file on GitHub · 95 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 95 lines · 50 tokens per session scan A 4061e631c1d3

Subscribe to this mod's changes

requirements-traceability is a skill published in the GitHub repository loiane/specs-driven-development-spring-angular (58 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 881 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

spec-kitty-charter-doctrine

Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…

Priivacy-ai/spec-kitty · 135 tokens

spec-kitty-implement-review

Orchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state transitions, rejection cycles, arbiter escalation, and dependency-aware sequencing across all 13 supported coding agents. Triggers: "implement and review WPs", "run the implement-review loop"…

Priivacy-ai/spec-kitty · 120 tokens

spec-kitty-mission-review

Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift, risks, and security. Triggers: "review the merged mission", "post-merge mission review", "verify the completed mission", "audit the mission implementation", "mission-level acceptance review"…

Priivacy-ai/spec-kitty · 155 tokens

spec-kitty-program-orchestrate

Orchestrate a multi-repo, multi-mission Spec Kitty program end-to-end: run specify → plan → tasks → implement → review → merge → mission-review → post-merge fixes across several repositories in a defined dependency order, using background sub-agents for parallel work and a pulse-heartbeat safety net for long…

Priivacy-ai/spec-kitty · 188 tokens

spec-kitty-runtime-next

Drive the canonical spec-kitty next --mission control loop for mission advancement. Load agent profiles at init, apply action-scoped doctrine context at each step boundary, and pull specific tactics/directives on demand. Triggers: "run the next step", "what should runtime do next", "advance the mission", "what is the…

Priivacy-ai/spec-kitty · 110 tokens

spec-kitty-bulk-edit-classification

Recognize when a mission is a bulk edit and drive the occurrence-classification guardrail on the user's behalf. Triggers: user says any variant of "rename X to Y", "change the terminology", "migrate all occurrences", "replace across the codebase", "the X feature is now the Y feature", "sed everywhere", or any request…

Priivacy-ai/spec-kitty · 157 tokens