skills.rest
cslsoftwares
cslsoftwaresCOMMUNITY
Explore all skills by this author →
GitHub

governance-artifact-traceability

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

Updated Jan 6, 2026
Search Tags:#documentation#requirements#governance#spec#traceability#prd#audits
One-click install
npx skills add https://github.com/cslsoftwares/ParamentersORM --skill governance-artifact-traceability
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: governance-artifact-traceability
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/governance-artifact-traceability_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill governance-artifact-traceability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rastreabilidade bidirecional no Providers.2.1.0: maps each requirement in the PRD to its SPEC coverage, the code implementing it, the tests validating it, and the documentation describing it, enabling gap detection and impact analysis.

Core Features & Use Cases

  • Bidirectional mapping: PRD → SPEC → code → tests → documentation
  • Gap detection: flags missing implementations or tests
  • Audit readiness: supports release validation and impact analysis

Quick Start

Run the governance traceability workflow to produce the PRD→SPEC→code→test→doc matrix and save it to Documentation/Traceability.md.

Frequently Asked Questions about governance-artifact-traceability

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

FAQPage Schema
What is bidirectional traceability in requirements governance?▼

Bidirectional traceability maps each PRD requirement to its SPEC coverage, code implementation, tests, and documentation, enabling gap detection and impact analysis for governance audits.

How do I generate a traceability matrix from PRD to documentation?▼

Run the governance traceability workflow to read your PRD and SPEC, link requirements to implementations and tests, then output the complete matrix to Documentation/Traceability.md.

How are missing requirements or test coverage gaps flagged during audits?▼

Missing implementations, tests, or documentation are flagged as [FALTANDO] in the generated Traceability.md file, ensuring clear gap detection for release validation and audit readiness.

Can I use this traceability workflow for change impact analysis?▼

Yes, the bidirectional PRD to documentation mapping supports change impact analysis by linking requirements to code and tests, allowing you to verify SPEC coverage across the project.

Does this governance audit tool require external dependencies or components?▼

No, this traceability workflow operates without external dependencies or components, directly reading PRD and SPEC files to produce the documentation matrix natively.

Related Skills

Explore More Legal & Compliance Skills→
VSF-QC-TTSVSF-QC-TTS

common-software-requirements

Generate SRS drafts from PRD and AC documents with traceability.

Official
Intermediate
dsivovdsivov

release-validation

Automate production-release readiness assessment for development branches.

Community
Advanced
erwaenerwaen

scaffold-model

Generate Rails model scaffolds with migration, validations, associations, scopes, and RSpec specs.

Community
Advanced
nroze22nroze22
1

traceability-matrix

Generate requirements traceability matrices mapping user requirements to specifications and test cases.

Community
Advanced