id-trace

Identify and visualize bidirectional traceability across artifacts and detect missing mappings.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/bs-koo/gx-pm --skill id-trace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: id-trace
Source: https://github.com/bs-koo/gx-pm/tree/main/plugins/gx-pm/skills/id-trace
Command: npx skills add https://github.com/bs-koo/gx-pm --skill id-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

임의의 산출물 ID를 입력받아 해당 ID와 연결된 전체 추적 체인을 양방향으로 조회하고, 누락된 매핑을 탐지한다. 단건 추적과 전체 교차 검증 두 가지 모드를 제공한다.

Core Features & Use Cases

  • 요구사항↔화면↔프로그램↔테스트 체인 전체를 시각화하고 추적 상태를 한 눈에 파악합니다.
  • 단건 추적과 전체 교차 검증 모드에서 누락 매핑을 자동으로 식별하고 리포트를 생성합니다.
  • 실무 예시: 특정 요구사항(B-RE-003)에서 시작해 화면, 프로그램, 테스트 ID를 계층적으로 확인하고 누락된 요소를 표시합니다.

Quick Start

Enter a target ID to view its complete bidirectional trace tree and highlighted missing mappings.

Frequently Asked Questions about id-trace

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

FAQPage Schema
How do I trace a requirement ID across screens, programs, and tests?

To trace a requirement ID, enter the target ID to automatically generate a hierarchical bidirectional trace tree spanning screens, programs, and tests while highlighting any missing mappings.

What is bidirectional traceability and how does it detect missing mappings?

Bidirectional traceability links artifacts upstream and downstream. It detects four specific missing-mapping types by enforcing ID-type recognition and calculating completion rates across the full trace path.

Can I perform full cross-verification for all project artifacts instead of single-ID tracing?

Yes, you can perform full cross-verification across all requirements, screens, programs, and tests to produce comprehensive missing-item reports and completion-rate calculations for auditing.

Do I need any specific tools or dependencies to visualize the trace tree?

No specific tools or dependencies are required. The Skill internally processes the entered artifact IDs to visualize the trace tree and structured outputs without external component integrations.

What is the best way to identify orphaned tests and requirements during validation?

The best way to identify orphaned artifacts is running the full cross-verification mode, which automatically detects and reports the four missing-mapping types across the entire requirements, screens, programs, and tests chain.