propagate-req-keys

Name: propagate-req-keys
Availability: InStock
Author: foolishimp

Tag code, tests, and commits with REQ-* keys for traceability.

Updated Aug 27, 2026

Search Tags:#requirements #traceability #tagging #tests tagging #code tagging

Ready to run

npx skills add https://github.com/foolishimp/ai_sdlc_method --skill propagate-req-keys

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: propagate-req-keys
Source: https://github.com/foolishimp/ai_sdlc_method/tree/main/gemini-code/plugins/aisdlc-core/skills/propagate-req-keys
Command: npx skills add https://github.com/foolishimp/ai_sdlc_method --skill propagate-req-keys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Actuator ensures all artifacts are tagged with REQ-* keys for bidirectional traceability, so every implementation, test, and commit can be traced back to a requirement.

Core Features & Use Cases

Tag Implementation: Adds # Implements: REQ-* to source files.
Tag Tests: Adds # Validates: REQ-* to tests and feature files.
Tag Commits: Encourages including REQ-* keys in commit messages for traceability.

Quick Start

Tag a Python module implementing REQ-USER-LOGIN-001 with # Implements: REQ-USER-LOGIN-001.

Frequently Asked Questions about propagate-req-keys

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

FAQPage Schema

How do I tag code and tests with requirement keys for traceability?▼

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.

What's the difference between tagging implementation files versus test files?▼

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.

Can I tag multiple requirements on a single code artifact?▼

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.

Do I need to validate REQ-* keys exist before tagging?▼

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.

How do requirement tags in commits improve traceability?▼

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.