propagate-req-keys

Tag implementation files with # Implements: REQ-* and test or feature files with # Validates: REQ-* placed immediately above function, class definitions, or at file top. Each artifact can have multiple REQ-* keys, enabling bidirectional traceability between requirements, code, and tests.

Implementation files in src/ receive # Implements: REQ-* tags to mark what requirement they fulfill. Test and feature files receive # Validates: REQ-* tags to mark which requirements they verify. This distinction maintains clear traceability across the development lifecycle.

Yes, code, test, and feature files can each carry multiple REQ-* tags. This flexibility allows a single function or test to address multiple requirements while maintaining full traceability across all linked artifacts.

Yes, valid REQ-* keys must exist and be validated before tagging artifacts. This prevents orphaned references and ensures every tag points to an actual requirement, preserving traceability integrity.

Including REQ-* keys in commit messages links code changes directly to requirements. Combined with tags in implementation and test files, this creates end-to-end traceability from requirement through commits to tests.