Can I use this for non-functional requirements?

Yes, the skill includes specific patterns for performance (PERF), security (SEC), scalability (SCALE), availability (AVAIL), and maintainability (MAINT).

How does this skill improve code quality?

By establishing a clear mapping between code and requirements, it ensures every feature is documented, simplifies audits, and makes it easier to identify gaps in test coverage.

Does it support complex business logic?

Yes, it provides dedicated patterns for Business Rules (REQ-BR) and nested formulas (F-*) to define precise calculations and logic for code generation.

What is a REQ-* key pattern?

It is a standardized identifier, such as REQ-F-AUTH-001, used to uniquely identify and track specific functional or non-functional requirements across the development lifecycle.

Where should I place the requirement tags?

Requirement tags like '# Implements: REQ-KEY' should be included in code comments, test validation files, and commit messages to maintain forward and backward traceability.

Requirement Traceability & SDLC Mapping

Name: Requirement Traceability & SDLC Mapping
Author: foolishimp

byfoolishimp

Security & Testing

Standardizes requirement tracking across the software development lifecycle using structured REQ-* key patterns and validation rules.

About

This foundation skill serves as the source of truth for requirement traceability within the AI SDLC framework. It establishes canonical naming conventions for functional, non-functional, data-driven, and business rule requirements, ensuring that every line of code can be mapped back to its original intent. By providing validation regex and traceability workflows—from initial intent to runtime telemetry—it enables Claude to maintain high-integrity documentation and rigorous compliance throughout the development process, making it essential for teams requiring strict audit trails and architectural consistency.

Key Features

Support for nested business rules, constraints, and calculation formulas
Traceability mapping from high-level intent to production code and tests
0 GitHub stars
Automated validation using predefined regex for requirement keys
Standardized REQ-* naming patterns for functional and non-functional requirements
Tagging conventions for code implementation, testing, and telemetry

Use Cases

Validating requirement IDs in code comments and technical documentation
Mapping new feature requests to specific functional requirement keys
Ensuring consistency between requirements, test cases, and monitoring logs

About

Key Features

Support for nested business rules, constraints, and calculation formulas
Traceability mapping from high-level intent to production code and tests
0 GitHub stars
Automated validation using predefined regex for requirement keys
Standardized REQ-* naming patterns for functional and non-functional requirements
Tagging conventions for code implementation, testing, and telemetry

Use Cases

Validating requirement IDs in code comments and technical documentation
Mapping new feature requests to specific functional requirement keys
Ensuring consistency between requirements, test cases, and monitoring logs