What kind of output does the Spec-to-Code Coverage Map produce?

It generates a comprehensive Markdown file at 'docs/spec-coverage-map.md' containing ASCII diagrams, a reverse index table, coverage percentages, and gap analysis.

Where does this skill look for specification files?

The skill unconditionally checks both the '.specify/memory/specifications' and 'specs/' directories, merging and deduplicating results for a complete view.

How does the skill identify which code files belong to a spec?

It extracts file paths using a combination of section-based parsing (e.g., 'Files' or 'Implementation Status' sections) and regex patterns for backtick-wrapped paths and common file extensions.

What does the 'Risk' level in the reverse index indicate?

Risk levels are based on how many features share a file: 1 spec is LOW, 2-3 specs is MEDIUM, and 4+ specs is HIGH, signaling a critical utility where changes have broad impact.

Can this skill help me clean up my codebase?

Yes, Step 7 (Identify Gaps) specifically lists all code files not covered by specs, helping you find deprecated files to remove or business logic that needs better documentation.

Spec-to-Code Coverage Map

Name: Spec-to-Code Coverage Map
Author: jschulte

byjschulte

•

Security & Testing

Generates visual mapping and coverage statistics to track the relationship between specification files and implementation code.

The Spec-to-Code Coverage Map skill provides critical visibility into the alignment between project requirements and the actual codebase. By scanning specification directories and extracting file references, it generates a comprehensive report featuring ASCII diagrams, reverse indexes, and coverage heat maps. This skill is indispensable for developers practicing spec-driven development, as it automatically identifies 'blind spots' where code exists without documentation and highlights 'high-risk' shared files that impact multiple features. It transforms abstract documentation into an actionable technical audit, ensuring your project remains organized and fully documented as it scales.

Key Features

01Automated gap analysis identifying undocumented code files with actionable cleanup recommendations

02Automatic spec discovery from standard directories like .specify and specs/

03Visual ASCII box diagrams illustrating the file structure associated with each spec

04Comprehensive reverse index mapping implementation files back to their governing specifications

05Categorized coverage statistics with visual heat maps for Backend, Frontend, and Infrastructure

061 GitHub stars

Use Cases

01Conducting project audits to identify technical debt and undocumented legacy code

02Validating implementation progress during feature development to ensure all files are spec-aligned

03Performing impact analysis for shared utilities to understand which features are affected by changes

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jschulte/claude-plugins spec-coverage-map

For use in Claude.ai and ChatGPT

Download Skill