gap-scan

Compare implemented features against prd-structure.yaml to classify gaps as implemented, partial, or missing.

1|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ezagent42/prd2impl --skill gap-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gap-scan
Source: https://github.com/ezagent42/prd2impl/tree/main/skills/skill-2-gap-scan
Command: npx skills add https://github.com/ezagent42/prd2impl --skill gap-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically scans the codebase to reveal gaps between PRD requirements and implemented features, helping teams align delivery with the planned scope.

Core Features & Use Cases

  • Per-module gap discovery by comparing the current codebase against the generated prd-structure.yaml
  • Generates a structured gap report that classifies items as implemented, partial, or missing
  • Supports validating coverage after /prd-analyze and informs next steps for gap closure

Quick Start

Run /gap-scan after /prd-analyze to generate a gap report for your project.

Frequently Asked Questions about gap-scan

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

FAQPage Schema
How do I identify gaps between PRD requirements and my codebase?

Gap scanning compares your current codebase against a generated prd-structure.yaml to classify items as implemented, partial, or missing. It performs per-module coverage checks to flag unimplemented NFR relevance and planned features.

What is the best way to check codebase coverage against a PRD?

Run a per-module gap analysis that compares your current codebase against a generated prd-structure.yaml. This validates coverage and outputs a structured gap report classifying items as implemented, partial, or missing.

Do I need an existing PRD structure to perform a codebase gap analysis?

Yes, gap analysis requires an existing PRD-derived structure and codebase. The scanner parses prd-structure specifications and plans directory outputs to evaluate module-wise coverage and NFR relevance accurately.

How do I generate a structured gap report for missing PRD features?

Scan the codebase per module against PRD specifications to flag implemented, partial, or missing items. This generates a structured gap report ready for the generation of gap-analysis YAML.

Can I validate non-functional requirement coverage in my codebase?

Yes, scanning the codebase against PRD specifications validates non-functional requirement (NFR) coverage. The analysis checks NFR relevance per module and flags whether each requirement is implemented, partial, or missing.