gap-analysis

Compare documentation against source code to detect missing implementations and mismatches.

4|2|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/wojons/skills --skill gap-analysis-wojons
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gap-analysis
Source: https://github.com/wojons/skills/tree/main/skills/gap-analysis
Command: npx skills add https://github.com/wojons/skills --skill gap-analysis-wojons

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill systematically identifies and helps resolve discrepancies between your documented requirements and the actual code implementation, ensuring accuracy and reducing technical debt.

Core Features & Use Cases

  • Discrepancy Detection: Compares documentation (requirements, specs) against source code to find missing features, undocumented code, or behavioral mismatches.
  • Gap Classification & Prioritization: Categorizes gaps by severity and impact, helping you focus on what matters most.
  • Remediation Planning: Generates actionable steps and plans to close identified gaps.
  • Use Case: After a development sprint, use this Skill to verify that all new features documented in requirements.md have corresponding code in src/ and that their behavior matches the documentation.

Quick Start

Run the gap-analysis script to compare your documentation directory with your source code directory.

Frequently Asked Questions about gap-analysis

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

FAQPage Schema
How do I find discrepancies between documented requirements and source code implementation?

Gap analysis identifies missing implementations, undocumented features, and behavioral mismatches by systematically parsing documentation formats and analyzing source code. It classifies these discrepancies by severity and impact to prioritize remediation efforts effectively.

Why does my code have undocumented features and outdated documentation after a sprint?

Undocumented features and outdated documentation occur when implementation outpaces specification updates. A gap analysis detects these behavioral mismatches by comparing your source code against documented requirements, categorizing the severity of the gaps to help you prioritize fixes.

What is the best way to classify and prioritize technical debt from missing implementations?

The best way to classify and prioritize technical debt from missing implementations is to perform a systematic gap analysis. This categorizes discrepancies by severity and impact, allowing you to focus remediation planning on the most critical behavioral mismatches first.

Can I use gap analysis to verify code behavior matches requirements.md files?

Yes, you can use gap analysis to verify that code behavior matches requirements.md files. The Skill systematically compares your documentation directory against your source code directory to detect missing features, undocumented code, and behavioral mismatches after development.

How do I generate a remediation plan for behavioral mismatches detected in source code?

To generate a remediation plan for behavioral mismatches, run the gap analysis script to compare documentation with source code. It provides actionable steps and prioritized plans to close identified gaps and reduce technical debt.