Build Traceability

Name: Build Traceability
Availability: InStock
Author: beekeeper-lab

Generate traceability matrices mapping user stories and acceptance criteria to test cases.

Updated Feb 14, 2026

Search Tags:#quality assurance #gap analysis #test coverage #traceability #requirements management #test planning

Ready to run

npx skills add https://github.com/beekeeper-lab/repomirrorkit --skill build-traceability

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Build Traceability
Source: https://github.com/beekeeper-lab/repomirrorkit/tree/main/.claude/skills/build-traceability
Command: npx skills add https://github.com/beekeeper-lab/repomirrorkit --skill build-traceability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all requirements (user stories and their acceptance criteria) are adequately covered by test cases, and that all test cases serve a defined purpose. It identifies gaps in testing and highlights redundant or unnecessary tests.

Core Features & Use Cases

Traceability Matrix Generation: Creates a clear mapping between acceptance criteria and test cases.
Gap Analysis: Identifies acceptance criteria that lack any test coverage.
Orphaned Test Identification: Flags test cases that do not map back to any requirement.
Use Case: After a new set of user stories is defined, use this Skill to automatically verify that each acceptance criterion has at least one corresponding test case written for it, and that all existing test cases are still relevant to current requirements.

Quick Start

Use the build-traceability skill with stories from '/path/to/stories' and tests from '/path/to/tests'.

Frequently Asked Questions about Build Traceability

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

FAQPage Schema

How do I map user stories to test cases for requirements traceability?▼

Requirements traceability maps user stories and acceptance criteria to test cases. This Skill generates a traceability matrix by parsing markdown files to build bidirectional links, ensuring every requirement has corresponding test coverage.

How do I find orphaned test cases and coverage gaps in my test suite?▼

Gap analysis identifies acceptance criteria lacking test coverage and flags orphaned tests that map to no requirement. Parsing story and test case directories reveals these gaps and redundant tests during your test planning process.

Can I use markdown files to generate a traceability matrix?▼

Yes, traceability matrix generation operates directly on markdown files within specified directories. You provide the paths to your stories and tests, and it parses those files to build forward and reverse trace links.

What is the best way to automate gap analysis for acceptance criteria?▼

Automating gap analysis requires parsing story and test case files to map acceptance criteria to tests. Using this Skill on your markdown directories verifies that each criterion has at least one test case and highlights unnecessary tests.

How does bidirectional requirement-to-test coverage work?▼

Bidirectional requirement-to-test coverage establishes forward and reverse trace links between stories and tests. This ensures all acceptance criteria have mapped test cases while simultaneously identifying orphaned test cases that serve no defined requirement.