Spec Gap Analysis FAQs

Question 1

Can I use this for API verification?

Accepted Answer

Yes, the skill specifically extracts API contracts, endpoint definitions, and function signatures from your documentation and verifies their existence and behavior within the source code.

Question 2

What file types does Spec Gap Analysis support?

Accepted Answer

The skill supports Markdown (.md) and text (.txt) files including dedicated specifications, blueprints, requirements documents, and Architecture Decision Records (ADRs) found in your project directories.

Question 3

Does it just search for keywords or does it understand context?

Accepted Answer

It performs context-aware verification. For example, when checking a CLI command, it looks for argument parser definitions and handler functions rather than just matching a string in a comment.

Question 4

What happens if my project doesn't have formal specification files?

Accepted Answer

If no spec documents or architectural signals are detected, the skill logs a skip message and does not penalize your audit score, making it safe for projects without formal documentation.

Question 5

How does the scoring system work?

Accepted Answer

The analysis starts at a score of 100. It deducts 15 points for Missing features (planned but not found), 7 points for Partial implementations, and 5 points for Extra features (implemented but undocumented).

Spec Gap Analysis

主要功能

使用场景

Spec Gap Analysis

主要功能

使用场景