gap-finder-1
Triggered by start-gap-finder.
When & Why to Use This Skill
The Plan Gap Identifier is a specialized Claude skill designed to audit documents and proposals for conceptual inconsistencies. It systematically flags undefined terms, unjustified assertions, and unexplained claims that create ambiguity. By generating a structured, raw list of these 'gaps,' it enables writers and project leads to strengthen their logic and ensure maximum clarity in technical, business, or academic planning.
Use Cases
- Technical Documentation Audit: Identify undefined technical jargon or unexplained system behaviors in design specifications to ensure developer alignment.
- Business Proposal Review: Flag unsupported claims and unjustified assumptions in strategic plans or investment pitches to improve persuasiveness.
- Project Planning: Detect vague milestones and unexplained dependencies in complex project roadmaps to prevent execution errors and misunderstandings.
- Academic and Research Writing: Highlight conceptual gaps and asserted statements that require further evidence or clarification before peer review or publication.
| name | gap-finder-1 |
|---|---|
| description | Triggered by start-gap-finder. |
Plan Gap Identifier
Generate a raw list of potential conceptual gaps. Don't filter yet.
What to look for
Terms or claims used but never defined/justified — things that block understanding.
Rules
- One line per gap — no sub-bullets
- Approach-level, not implementation
- Flag, don't fix — just name the term
- Max 20 items
Output format
# Step 1: Raw Gaps
- [Line 42] "foo" - undefined
- [Line 87] "X enables Y" - asserted
- [Line 103] "threshold" - unjustified
Tags: undefined | unexplained | asserted | unjustified | unclear
Anti-patterns
- No question marks
- No "vs" comparisons
- No analysis of WHY it's a gap
- No parenthetical elaboration