start-gap-finder

Find conceptual gaps in plan/spec documents. Use when user explicitly asks start-gap-finder.

⭐1stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026⬇️1downloads

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.
namestart-gap-finder
descriptionFind 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

  1. Invoke gap-finder-1 skill on the document
  2. Invoke gap-finder-2 skill (uses Step 1 output from conversation)
  3. Invoke gap-finder-3 skill (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.