gap-analyzer

Map Markdown, JSON, or YAML requirements to code and generate gap reports.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/ialameh/sift-coder --skill gap-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gap-analyzer
Source: https://github.com/ialameh/sift-coder/tree/main/skills/gap-analyzer
Command: npx skills add https://github.com/ialameh/sift-coder --skill gap-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect gaps between specifications and their implementations, and identify undocumented features to improve traceability and quality.

Core Features & Use Cases

  • Requirement Extraction: pull structured requirements from specification files (markdown, JSON, YAML)
  • Crawl Plan Generation: create focused exploration plans based on requirements and code layout
  • Implementation Detection: assess area-by-area whether requirements are implemented, partial, or missing, with evidence
  • Extra Feature Discovery: identify significant features not described in the specification
  • Gap Classification: categorize gaps by type and severity to prioritize fixes
  • Report Generation: deliver a comprehensive, actionable gap report with recommendations

Quick Start

Run gap-analyzer on your repository to detect specification-implementation gaps and generate a structured gap report

Frequently Asked Questions about gap-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find gaps between software specifications and code implementations?

A gap analyzer maps requirements from Markdown, JSON, or YAML files to corresponding code areas to detect missing or partial implementations. It generates a structured status report with evidence and recommended fixes.

What is the best way to check if code matches requirements in a software project?

Checking if code matches requirements involves generating a focused crawl plan based on your code layout. It assesses area-by-area whether each requirement is implemented, partial, or missing, classifying gaps by type and severity.

Can I identify undocumented features in my codebase using a gap analysis tool?

Yes, gap analysis can identify significant undocumented features by discovering code functionality not described in the specification. This extra feature discovery improves traceability and overall project quality.

How do I extract requirements from Markdown or YAML for traceability?

You can extract requirements from Markdown or YAML by pulling structured data from specification files. This allows you to map them directly to code areas for implementation detection and traceability.

Does gap analysis work with JSON specification files?

Gap analysis works with JSON specification files by pulling structured requirements to map against your code. It assesses whether each JSON-defined requirement is implemented, partial, or missing, providing evidence for each status.

Why should I classify gaps by severity when comparing specs to code?

Classifying gaps by severity when comparing specs to code helps prioritize fixes for missing or partial implementations. It categorizes discrepancies by type and severity, delivering an actionable gap report with targeted recommendations.