trace

Generate a project-wide requirements traceability matrix from pipeline artefacts.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/4797pnkkx5-gif/AI-Augmented-RE --skill trace-4797pnkkx5-gif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/4797pnkkx5-gif/AI-Augmented-RE/tree/main/skills/trace
Command: npx skills add https://github.com/4797pnkkx5-gif/AI-Augmented-RE --skill trace-4797pnkkx5-gif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents silent requirements corruption by generating a complete traceability matrix and reporting orphans, cross-artefact drift, and change impact across the entire RE pipeline.

Core Features & Use Cases

  • Forward and backward traceability: Builds SH → BUC → FR/NFR → EP → US → AC → TC → TASK and the reverse chain for impact reasoning.
  • Coverage statistics: Quantifies how much of each pipeline element is linked and test-covered.
  • Orphan detection: Flags missing or invalid links (e.g., Accepted FR not covered by an Epic, or Tasks referencing non-existent AC/TC).
  • Cross-artefact drift detection: Compares duplicated FR/NFR/AC text across artefacts and highlights exact disagreements.
  • Impact analysis: Shows which downstream elements depend on Pending or Rejected upstream items.
  • Read-only snapshot output: Rebuilds a canonical matrix file every run without modifying upstream artefacts or inventing content.

Quick Start

Run the trace skill with /trace to generate artifacts/06-traceability/traceability-matrix.md from the current pipeline state.

Frequently Asked Questions about trace

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

FAQPage Schema
How do I generate a requirements traceability matrix for my project pipeline?

Generate a requirements traceability matrix by running the trace skill to read existing pipeline artefacts and automatically link stakeholders, epics, stories, acceptance criteria, and test cases. It outputs a single regenerated snapshot file.

What is cross-artefact drift detection in requirements engineering?

Cross-artefact drift detection identifies exact text disagreements when duplicated requirements or acceptance criteria are copied across different pipeline artefacts. It performs strict checks to highlight silent corruption and mismatches between linked items.

How do I find orphaned requirements and missing test coverage in my pipeline?

Find orphaned requirements by computing coverage statistics and flagging missing links, such as Accepted functional requirements lacking an Epic or implementation tasks referencing non-existent test cases.

Can I perform impact analysis on pending or rejected requirements without modifying my upstream files?

Perform impact analysis on pending or rejected items safely because the trace skill operates read-only. It rebuilds a canonical matrix snapshot every run without modifying upstream artefacts or inventing content.

Does requirements traceability automation work for partial pipelines with incomplete artefacts?

Requirements traceability automation applies to diagnostic audits of partial or complete pipelines. It relies on explicit ID and link fields across existing artefacts to compute coverage and detect orphans accurately.

What is backward traceability and how does it help with change impact analysis?

Backward traceability builds the reverse chain from implementation tasks up through test cases, stories, and epics to business use cases. It shows which downstream elements depend on pending or rejected upstream items for impact reasoning.