skills.rest
loiane
loianeCOMMUNITY
Explore all skills by this author →
Website𝕏@loianeGitHub

requirements-traceability

Map AC-NNN requirements to tasks, tests, and production symbols in a traceability matrix.

50|7|Updated Apr 18, 2026
Search Tags:#requirements#validation#tasks#traceability#tests#ac-coverage#code-symbols
One-click install
npx skills add https://github.com/loiane/specs-driven-development-spring-angular --skill requirements-traceability-loiane
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-traceability
Source: https://github.com/loiane/specs-driven-development-spring-angular/tree/main/.windsurf/skills/requirements-traceability
Command: npx skills add https://github.com/loiane/specs-driven-development-spring-angular --skill requirements-traceability-loiane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build and verify the AC ↔ tasks ↔ tests ↔ code symbols ↔ gates traceability matrix to ensure no coverage gaps and to detect orphan tests or code.

Core Features & Use Cases

  • Trace ACs to corresponding tasks (T-NNN), tests (with AC tags), and production symbols.
  • Generate and validate a central traceability matrix (07a-traceability.md) for audits and code reviews.
  • Use during validation phase to enforce alignment between requirements and implementation across the repo.

Quick Start

Run the traceability validator to generate the AC↔tasks↔tests↔symbols matrix for your project and review the resulting 07a-traceability.md.

Frequently Asked Questions about requirements-traceability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure full traceability between acceptance criteria, tests, and production code symbols?▼

To ensure traceability, map every AC-NNN to corresponding tasks, tests, and production symbols. This validates full coverage and detects orphan tests or code by enforcing mappings across requirements and implementation.

What is a traceability matrix and when do I need to generate one for code reviews?▼

A traceability matrix maps ACs to tasks, tests, and code symbols to verify alignment. Generate one during the validation phase or code reviews to detect coverage gaps and ensure no orphan tests exist in the repository.

How do I validate that every acceptance criteria is covered by tasks and tests?▼

Validate acceptance criteria coverage by applying a traceability validator during the Validate phase. It enforces mappings between AC-NNN identifiers, tasks, tests, and harness gates to confirm every requirement has corresponding implementation.

How do I detect orphan tests or production code without coverage gaps?▼

Detect orphan tests and coverage gaps by building an AC ↔ tasks ↔ tests ↔ code symbols ↔ gates matrix. This traceability validation identifies unlinked production symbols and tests lacking corresponding acceptance criteria.

Can I use a traceability matrix for audits and enforce alignment across my repo?▼

Yes, a central traceability matrix like 07a-traceability.md enforces alignment between requirements and implementation across the repo. It produces a validated matrix suitable for audits and code reviews to verify complete coverage.

Related Skills

Explore More Software Engineering Skills→
adolfoaranaes12adolfoaranaes12
2

trace-requirements

Generate bidirectional traceability matrices mapping acceptance criteria to implementation evidence and tests.

Community
Advanced
cslsoftwarescslsoftwares

governance-artifact-traceability

Map PRD requirements to SPEC, code, tests, and documentation in a bidirectional matrix.

Community
Advanced
Nickalus12Nickalus12
2

validation

Coordinate cross-phase validation pipelines with Pass/Fail/Warn strictness.

Community
Advanced
aidottersaidotters

acceptance-test

Extract acceptance criteria from documentation and verify code, configuration, and behavior.

Community
Intermediate