How does it know which files belong to which specification?

It parses spec files for file paths, directory references, and component names mentioned in implementation status or file structure sections.

What output format does the coverage map use?

The skill generates a comprehensive Markdown file located at docs/spec-coverage-map.md, featuring ASCII art diagrams, tables, and heat maps.

Is this specific to the Stackshift toolkit?

While optimized for Stackshift 'Gear 6' workflows, it can be used in any project that maintains Markdown-based specifications in a dedicated folder.

Can this skill help reduce technical debt?

Yes, by identifying 'Shared Files' (those referenced by 4+ specs) and 'Coverage Gaps' (files with no specs), it highlights areas that require extra testing or refactoring.

Spec-to-Code Coverage Map

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

byjschulte

•

Learning & Documentation

Generates comprehensive visual maps and statistics showing the relationship between project specifications and implementation files.

The Spec-to-Code Coverage Map skill automates the process of auditing a codebase against its defining specifications, specifically designed for spec-driven development workflows. It analyzes specification files to extract file references, categorizes implementations into domains like backend or frontend, and produces a detailed Markdown report. This report includes ASCII visual diagrams, a reverse index to identify 'hot' files shared across multiple specs, and a gap analysis to highlight unimplemented or deprecated code, ensuring full alignment between project requirements and the actual codebase.

Key Features

01Performs gap analysis to identify files missing from specifications or potential dead code

02Provides risk assessment for shared files to highlight high-impact areas during refactoring

03Generates visual ASCII box diagrams mapping specifications to specific implementation files

04Calculates category-specific coverage percentages for backend, frontend, and infrastructure

051 GitHub stars

06Creates a reverse index to identify critical files referenced by multiple specs

Use Cases

01Assessing architectural complexity by tracking 'hot' files that impact multiple functional areas

02Validating implementation completion after finishing feature development

03Identifying deprecated or orphaned files during codebase cleanup and documentation phases

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jschulte/stackshift spec-coverage-map

For use in Claude.ai and ChatGPT

Download Skill