traceability-enginelisted

# Traceability Engine Ensures that PRD == Architecture == Code == Tests. Every requirement must be traceable through implementation to validation. ## Input - PRD content (required): The requirements document - scenario-set.md (optional): From test-strategy-planner - Source code folder (optional): Project source directory - Test files folder (optional): Project test directory - $ARGUMENTS: Path to PRD or "trace current project" ## Three-Way Mapping Principle ``` PRD Requirement <---> Test Scenario <---> Source Code FR-001 <---> SCN-1-001 <---> @implements FR-001 ``` A broken link in any direction = Traceability gap. ## Gap Types | Gap Type | Description | Severity | |----------|-------------|----------| | UNTESTED_REQ | Requirement exists, no test scenario covers it | Critical (P0 req) / High (P1+) | | UNLINKED_TEST | Test exists but maps to no requirement (orphan) | Medium | | DEAD_REQ | Requirement has tests but no `@implements` annotation in code | Medium | | PARTIAL_COVERAGE | Only happy path tested, missing error/edge cases | High | | STALE_TRACE | Requirement changed since test was written | High | ## Algorithm ### Step 1: Source Analysis **Requirement Extraction:** Parse PRD for requirement identifiers (FR-XXX, NFR-XXX, or any REQ-XXX pattern). Extract: { id, description, priority, type (functional/non-functional), source_line } **Test Annotation Extraction:** Scan test files for scenario IDs matching pattern: SCN-X-XXX-[H|N|E]-XX Map each test fi