gap

Detect specification-vs-code, wiring, and correctness gaps in software projects.

54|3|Updated Feb 4, 2026

Search Tags:#verification #gap analysis #dead code #specs #wiring #code correctness

Ready to run

npx skills add https://github.com/arcasilesgroup/ai-engineering --skill gap-arcasilesgroup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gap
Source: https://github.com/arcasilesgroup/ai-engineering/tree/main/.agents/skills/gap
Command: npx skills add https://github.com/arcasilesgroup/ai-engineering --skill gap-arcasilesgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies discrepancies between your software specifications and the actual code implementation, as well as issues with how code is connected and whether it behaves as claimed.

Core Features & Use Cases

Feature Gap Detection: Uncovers unimplemented features and missing test coverage for acceptance criteria.
Wiring Gap Analysis: Detects code that is implemented but not integrated or exposed correctly.
Correctness Verification: Compares stated behavior (from PRs or specs) against actual code to ensure delivery matches claims.
Use Case: Before a release, run this skill to ensure all documented features are implemented, wired into the system, and behave as described in the pull request.

Quick Start

Run the gap skill to verify all feature requirements against the codebase.

Frequently Asked Questions about gap

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

FAQPage Schema

How do I find mismatches between software specs and code implementation?▼

Spec vs. code mismatch detection analyzes your requirements against the codebase to identify unimplemented features, missing test coverage for acceptance criteria, and dead specifications. It flags disconnected or incorrectly implemented code segments to ensure delivery matches claims.

What is wiring gap analysis and how does it find dead code?▼

Wiring gap analysis detects code that is implemented but not integrated or exposed correctly within the system. It maps test coverage and identifies dead specifications, flagging disconnected code segments that exist in the codebase but fail to connect to the broader project architecture.

How do I verify claimed pull request behavior against actual code correctness?▼

Claimed behavior verification compares stated behavior from PRs or specs against actual code implementation. It ensures delivery matches claims by analyzing requirements, mapping test coverage, and verifying that documented features behave exactly as described before a release.

Can I check feature requirements against the codebase before a release?▼

Yes, running a pre-release gap analysis verifies all documented feature requirements against the codebase. It ensures features are fully implemented, correctly wired into the system, and behave as described in the pull request, preventing unverified code from reaching production.

What's the best way to detect unimplemented features and missing test coverage?▼

Feature gap detection uncovers unimplemented features and missing test coverage for acceptance criteria by analyzing requirements against codebase implementations. It maps test coverage to identify dead specifications and flags incorrectly implemented code segments.