traceability-matrix

Map PRD features to implementations, scenarios, and test IDs.

4|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/poz110/claude-harness --skill traceability-matrix-poz110
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: traceability-matrix
Source: https://github.com/poz110/claude-harness/tree/main/plugins/claude-harness/skills/traceability-matrix
Command: npx skills add https://github.com/poz110/claude-harness --skill traceability-matrix-poz110

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill mitigates the issue of context loss in a multi-agent collaborative development workflow, providing a live document that maps PRD features to their implementation locations, scenarios, test IDs, and completion status.

Core Features & Use Cases

  • PRD Feature Mapping: Links every Must/Should feature in PRD to its expected implementation, Gherkin scenarios, and test IDs.
  • Status Tracking: Maintains the status of completion for each PRD feature across various development stages.
  • Workflow Support: Invoked by various agents including Architects, FE/BE Developers, Reviewers, and QA at specific milestones in the development workflow.

Quick Start

Run the following command after Architect completes the ADR and safety baseline:

node scripts/workflow.js validate-doc traceability

Frequently Asked Questions about traceability-matrix

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

FAQPage Schema
How do I maintain requirement traceability across a multi-agent development workflow?

Requirement traceability across a development workflow is maintained by mapping every PRD feature to its implementation, Gherkin scenarios, and test IDs. This provides a live document tracking completion status across various development roles and milestones.

What is PRD feature mapping and how does it track development status?

PRD feature mapping links every Must and Should feature in a PRD to its expected implementation, Gherkin scenarios, and test IDs. It tracks the completion status of each feature continuously across different development lifecycle stages.

How do I validate traceability documents after completing the architecture design?

To validate traceability documents after architecture design, run the workflow validation script. This checks that PRD features are properly traced to their implementations, scenarios, and test results for continuous alignment.

Can I use Gherkin scenarios and test results for continuous requirement tracking?

Yes, Gherkin scenarios and test results are utilized for continuous requirement tracking. This ensures every PRD feature is traced to its corresponding test ID and implementation, mitigating context loss in collaborative environments.

Does this requirement tracking approach support different roles like Architects and QA?

This requirement tracking approach supports various roles including Architects, FE/BE Developers, Reviewers, and QA. It is invoked by these agents at specific milestones to ensure alignment across the entire development workflow.