spec-discovery

To extract spec IDs and traceability data across multiple repositories, you can parse markdown headings matching patterns like REQ-XYZ to capture associated spec titles, repository paths, and SHA-256 hashes. This generates a structured manifest organized by repository and path for cross-repo governance and auditing.

The best way to generate a spec manifest with provenance hashes for auditing is to compute SHA-256 hashes for each spec file while recording its source repository and path. This produces a structured JSON or TOON manifest with normalized anchors to support compliance tracking.

Yes, you can output traceability metadata in JSON format with normalized anchors. The extraction process locates specs across repositories, captures IDs and titles, and emits a structured manifest organized by repository and path in either JSON or TOON format.

Cross-repo spec governance tools handle duplicate spec files by applying optional de-duplication and validation during manifest generation. This ensures the final JSON or TOON output accurately reflects unique spec instances while maintaining their source repository, path, and SHA-256 hash metadata.

Yes, spec-discovery works with markdown files to detect REQ-XYZ heading patterns. It parses these headings to extract associated spec titles and computes traceability metadata including the source repository, file path, and SHA-256 hash for each matched file.

You need to compute SHA-256 hashes for spec files when you require provenance tracking and cross-repo governance. Computing these hashes creates a verifiable traceability manifest that records the source repository and path to support auditing and compliance validation.