spec-coverage-map

Spec-to-code coverage mapping reveals which code files each specification covers by parsing specs, extracting file references, and generating ASCII diagrams with reverse indexes. Run the Skill after Gear 6 implementation to produce docs/spec-coverage-map.md showing coverage across backend, frontend, and infrastructure.

Gap analysis detects code not covered by specifications. The Skill computes coverage statistics and highlights gaps in the generated ASCII diagrams and reverse index, helping teams spot undocumented or orphaned files across all layers.

Generate a comprehensive spec-to-code coverage map that produces ASCII diagrams, reverse indexes mapping files back to specs, and categorized coverage statistics. This creates human-friendly documentation suitable for cleanup phases and knowledge transfer.

The reverse index component maps individual files to all specifications covering them. Query the generated coverage map to see dependencies, shared ownership, and spec-to-file relationships for any code file across your architecture.

Run spec-coverage-map after Gear 6 implementation or during cleanup and documentation phases. It requires parsed specifications with file references already in place; use it when you're ready to audit coverage and identify gaps.

Yes. The Skill highlights shared files covered by multiple specs and categorizes them by backend, frontend, and infrastructure. This reveals overlapping coverage and helps surface coordination opportunities or potential conflicts.