Can it detect features that are not in the specification?

Yes, the Extra Feature Discovery capability identifies significant code sections, routes, or UI components that have no corresponding requirement in your documentation, flagging them as 'extras'.

How does Gap Analyzer map requirements to code?

It uses a combination of keyword matching, file structure analysis, and semantic similarity via vector embeddings to link specification items to specific functions, classes, and file paths.

Does it require specific tools to run semantic matching?

While it functions standalone using keyword matching, it leverages siftcoder-mcp for advanced vector search and higher-confidence semantic analysis.

How does it prioritize identified gaps?

Gaps are classified by severity from Critical (P0) to Low (P3) based on the nature of the requirement, prioritizing security features and core business logic over minor enhancements.

What file formats are supported for specifications?

Gap Analyzer can parse structured requirements from Markdown sections, JSON schemas, and YAML configuration files.

Gap Analyzer

Name: Gap Analyzer
Author: ialameh

byialameh

安全与测试

Identifies discrepancies between project specifications and actual code implementations while discovering undocumented features.

关于

The Gap Analyzer skill automates the process of reconciling technical specifications with the codebase to ensure feature completeness and documentation accuracy. It extracts structured requirements from spec files, maps them to specific code locations using semantic matching or keywords, and classifies gaps based on severity. It also acts as a discovery tool by highlighting 'extra' features present in the code that are missing from the documentation, providing a comprehensive report for maintaining software integrity and architectural alignment.

主要功能

Semantic mapping of requirements to source code using vector embeddings and keywords
Detailed report generation with actionable insights and implementation recommendations
0 GitHub stars
Automated requirement extraction from Markdown, JSON, and YAML specifications
Discovery of undocumented 'extra' features and hidden UI components within the codebase
Comprehensive gap classification by severity (Critical to Low) and implementation status

使用场景

Technical auditing before a release to ensure all specified requirements are fully implemented
Generating documentation for legacy codebases by identifying existing but undocumented functionality
Identifying implementation drift where the code logic has diverged from the original design specifications

关于

主要功能

Semantic mapping of requirements to source code using vector embeddings and keywords
Detailed report generation with actionable insights and implementation recommendations
0 GitHub stars
Automated requirement extraction from Markdown, JSON, and YAML specifications
Discovery of undocumented 'extra' features and hidden UI components within the codebase
Comprehensive gap classification by severity (Critical to Low) and implementation status

使用场景

Technical auditing before a release to ensure all specified requirements are fully implemented
Generating documentation for legacy codebases by identifying existing but undocumented functionality
Identifying implementation drift where the code logic has diverged from the original design specifications