traceability

To check PRD alignment, you analyze cross-references between Business Rules and Shared Requirements in a PRD and their usage in feature specifications. This detects dangling references, orphan rules, and coverage gaps to ensure all specified rules are accounted for.

Requirement traceability is the mechanism of tracking Business Rules and Shared Requirements from a PRD to their specific implementation in feature specs. It works by parsing rule IDs and feature IDs to build a traceability matrix, preventing orphan requirements and ensuring full specification coverage.

You find dangling references by parsing PRD section 4 and .specs/*.md files to extract rule IDs and feature IDs. Comparing these IDs builds a traceability matrix that flags any feature spec referencing a non-existent Business Rule or Shared Requirement.

Yes, you can detect orphan business rules by analyzing cross-references between your PRD and feature specification files. The analysis identifies any defined Business Rules or Shared Requirements that are not referenced by any feature spec, highlighting coverage gaps.

You identify potentially stale feature specs by checking modification timestamps. The staleness check flags feature specifications that were modified before the PRD itself, suggesting the spec may be outdated and require review against current requirements.

Yes, this traceability analysis requires parsing PRD section 4 for Business Rules and Shared Requirements, alongside .specs/*.md files for feature specifications. Your documents must use consistent rule IDs and feature IDs to successfully build the traceability matrix.