Does Gap Finder fix the issues it finds?

No, the skill is designed to flag gaps without attempting to fix them, providing a raw list that allows you to address the issues manually.

What does the Gap Finder skill do?

It identifies conceptual blind spots in your project plans or documentation, such as undefined terms, unexplained claims, or unjustified assertions.

Can I use this for implementation details?

Gap Finder is intended for approach-level conceptual analysis rather than specific code implementation or syntax checking.

How do I trigger this skill in Claude Code?

You can initiate the analysis by using the trigger phrase 'start-gap-finder' within your Claude Code environment.

What is the maximum number of gaps identified?

The skill is configured to identify a maximum of 20 raw gaps per session to ensure the output remains focused and actionable.

Gap Finder

Name: Gap Finder
Author: OhadRubin

byOhadRubin

•

Productivity & Workflow

Identifies conceptual gaps, undefined terms, and unjustified assertions within technical plans or documentation.

About

Gap Finder is a specialized Claude Code Skill designed to perform a rigorous audit of plans, proposals, and project documents. It systematically scans for logical inconsistencies, undefined terminology, and baseless assertions, providing a raw list of areas that require further clarification. By strictly flagging gaps without attempting to fix them or provide commentary, it allows developers and architects to quickly identify blind spots in their strategy or implementation logic, ensuring that projects are built on a solid, well-defined foundation.

Key Features

Flags unjustified assertions and unproven claims
Provides a concise, one-line per gap output format
Focuses on high-level approach gaps rather than minor implementation details
Enforces strict anti-patterns to eliminate analytical noise and fluff
Detects undefined terms and jargon lacking context
1 GitHub stars

Use Cases

Auditing technical documentation to identify terms that require clearer definitions
Reviewing project specifications for logical holes before beginning development
Validating architectural proposals to ensure every technical claim is justified

About

Key Features

Flags unjustified assertions and unproven claims
Provides a concise, one-line per gap output format
Focuses on high-level approach gaps rather than minor implementation details
Enforces strict anti-patterns to eliminate analytical noise and fluff
Detects undefined terms and jargon lacking context
1 GitHub stars

Use Cases

Auditing technical documentation to identify terms that require clearer definitions
Reviewing project specifications for logical holes before beginning development
Validating architectural proposals to ensure every technical claim is justified