skills.rest
Jose-Polanco-Oxte
Jose-Polanco-OxteCOMMUNITY
Explore all skills by this author →
GitHub

req-traceability

Updates requirement specification documents and generates structured traceability reports for specification changes.

3|Updated Aug 8, 2026
Search Tags:#documentation#specification#requirements#report generation#acceptance criteria#traceability
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill req-traceability-jose-polanco-oxte
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: req-traceability
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/req-traceability
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill req-traceability-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping requirement specifications synchronized with code changes is error-prone, and teams often lose track of which requirements map to which implementations. This Skill updates the central requirements specification file and produces a dated traceability report linking each requirement to its implementation and verification. ## Core Features & Use Cases - Specification Updates: Edits or appends requirement entries in docs/public/spec/requirements-spec.md with IDs, formulas, ranges, and acceptance criteria. - Traceability Report Generation: Creates dated reports in docs/public/traceability/ following a strict template covering normative sources, implementation mapping, verification, and deviations. - Use Case: When a stakeholder changes an audio calibration formula (e.g., LUFS target), the Skill updates the spec section, records the requirement ID, and generates a report mapping the formula to the implementing file, symbol, and test procedure. ## Quick Start Update the requirements specification for the new frequency range change and generate a traceability report for it.

Frequently Asked Questions about req-traceability

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

FAQPage Schema
How do I keep requirement specifications in sync with code changes?▼

Update the requirement entry in docs/public/spec/requirements-spec.md with the new ID, formula, and acceptance criteria, then generate a traceability report mapping that requirement to the implementing file and symbol. This keeps the spec and implementation linked.

What is a requirements traceability report and what should it contain?▼

A traceability report links each requirement to its normative source, implementation location, and verification method. This Skill's template includes tables for normative source, implementation mapping, verification results, and a section for deviations or design decisions.

How are traceability report files named and organized?▼

Reports are stored in docs/public/traceability/ using the naming format traceability-report-<YYYYMMDD>-<feature-name>.md. Each report covers one feature or increment and records date, responsible author, and implementation status.

When should I not use a formal traceability report workflow?▼

For trivial changes like typo fixes or cosmetic edits with no requirement impact, generating a full traceability report adds overhead without value. Reserve it for changes affecting requirement IDs, formulas, ranges, or acceptance criteria.

Related Skills

Explore More Software Engineering Skills→
rolopez23rolopez23

problem-spec

Define problem statements with boundaries and success criteria.

Community
Intermediate
paxlabs-incpaxlabs-inc
7

documentation-sync

Synchronize documentation files with current source code and verify accuracy.

Community
Advanced
usetheodevusetheodev

review-community-standard-componentization-cross-validation-knowledge

Automates cross-validation of plan-to-commit mappings and DoD verification.

Community
Advanced
wattdatawattdata
5

audience-activate

Export built audiences into platform-ready files for Meta, Google, or Reddit.

Official
Advanced