requirements-traceability

Update the traceability matrix and verify PROJECT_STATE.md against requirements.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gw-ai-security/ats-cv-scorer --skill requirements-traceability-gw-ai-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirements-traceability
Source: https://github.com/gw-ai-security/ats-cv-scorer/tree/main/.codex/skills/requirements-traceability
Command: npx skills add https://github.com/gw-ai-security/ats-cv-scorer --skill requirements-traceability-gw-ai-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that Functional and Non-Functional Requirements and their traceability remain consistent, auditable, and repo-based across changes in requirements, priorities, status, acceptance criteria, or mapping to code and tests.

Core Features & Use Cases

  • Maintain a single source of truth for FR/NFR statuses and acceptance criteria.
  • Update the traceability matrix with paths to src/ and tests/ whenever code or tests change.
  • Validate that documentation in docs/00_overview/PROJECT_STATE.md reflects the current project status.

Quick Start

Update FR/NFR criteria and traceability mappings in your repo and verify documentation consistency.

Frequently Asked Questions about requirements-traceability

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

FAQPage Schema
How do I maintain requirements traceability when source code or tests change in my repository?

Requirements traceability is maintained by updating the traceability matrix with paths to src/ and tests/ whenever implementations or tests are added, ensuring mappings stay current and auditable.

What is the best way to keep functional and non-functional requirements aligned with project documentation?

Keeping requirements aligned involves enforcing acceptance criteria for Functional and Non-Functional Requirements and verifying that docs/00_overview/PROJECT_STATE.md reflects the true current project status.

How do I enforce acceptance criteria for non-functional requirements in a repo-based workflow?

You can enforce acceptance criteria by applying a repo-based skill that validates Functional and Non-Functional Requirements updates and maintains a single source of truth for their statuses.

When do I need to update the traceability matrix for my project requirements?

You need to update the traceability matrix whenever new requirements arise, existing ones are updated, or implementations and tests are added, ensuring mapping to code and tests stays consistent.

Can I use repository files as a single source of truth for requirements status and traceability?

Yes, you can use repository files as a single source of truth by maintaining consistent, auditable, repo-based Functional and Non-Functional Requirements and updating their traceability mappings across changes.

Why does my project state documentation show outdated requirements traceability after code changes?

Project state documentation becomes outdated when the traceability matrix is not updated with new src/ and tests/ paths, causing docs/00_overview/PROJECT_STATE.md to fail reflecting the true project status.