start-gap-finder
Find conceptual gaps in plan/spec documents. Use when user explicitly asks start-gap-finder.
When & Why to Use This Skill
The Plan Gap Finder is a specialized Claude skill designed to identify conceptual gaps and logical inconsistencies in project plans and technical specifications. By executing a rigorous, three-step automated analysis, it helps developers and product managers ensure that their documentation is comprehensive, robust, and free of overlooked requirements before implementation begins.
Use Cases
- Technical Specification Review: Automatically scan system design documents to find missing architectural details or unaddressed edge cases that could impact system stability.
- Product Requirement Validation: Analyze PRDs (Product Requirement Documents) to identify logical gaps in user flows or conflicting requirements that might lead to development bottlenecks.
- Project Roadmap Auditing: Evaluate high-level project plans to ensure all dependencies, resource constraints, and potential risks are conceptually accounted for in the documentation.
| name | start-gap-finder |
|---|---|
| description | Find conceptual gaps in plan/spec documents. Use when user explicitly asks start-gap-finder. |
Plan Gap Finder
Find conceptual gaps by running three steps in sequence. Each step is a separate skill invocation.
Procedure
- Invoke
gap-finder-1skill on the document - Invoke
gap-finder-2skill (uses Step 1 output from conversation) - Invoke
gap-finder-3skill (uses Step 2 output from conversation)
IMPORTANT: Do NOT stop between steps. Output what each step requires, then immediately continue to the next skill. Run all three steps in a single turn.