find-gaps

Analyze software specifications and mockups to surface missing states and edge cases.

3|Updated May 3, 2026
One-click install
npx skills add https://github.com/chloebrett/slay --skill find-gaps-chloebrett
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-gaps
Source: https://github.com/chloebrett/slay/tree/main/.claude/skills/find-gaps
Command: npx skills add https://github.com/chloebrett/slay --skill find-gaps-chloebrett

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps teams systematically uncover overlooked states, assumptions, and edge cases in their plans, acceptance criteria, or mockups, reducing bugs and rework.

Core Features & Use Cases

  • Systematic Gap Analysis: Review artifacts for completeness across categories like scope, failure handling, observability, and UI states.
  • Interactive Resolution: Engage in a conversational loop to clarify gaps and produce traceable updates to documentation.
  • Use Case: Use this skill to preemptively find missing acceptance criteria or edge cases before implementation begins, ensuring robustness.

Quick Start

Share your project plan or mock documentation and ask the skill to identify and resolve gaps interactively.

Frequently Asked Questions about find-gaps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify missing edge cases in software requirements before implementation?

To identify missing edge cases in software requirements, analyze specifications and mockups against categories like scope, failure handling, and UI states. This systematic gap analysis surfaces hidden assumptions and prevents post-launch bugs.

What is the best way to perform gap analysis on acceptance criteria?

The best way to perform gap analysis on acceptance criteria is through an interactive, conversational review process. This approach clarifies ambiguities and produces traceable documentation updates for requirements completeness.

How do I find missing UI states and internationalization issues in my mockups?

Finding missing UI states and internationalization issues requires reviewing mockups to surface overlooked states and assumptions. Analyzing these artifacts ensures robustness across diverse user contexts before coding starts.

Can I use spec review to uncover failure modes and observability gaps?

Yes, you can use spec review to uncover failure modes and observability gaps. By systematically analyzing plans for completeness, teams can preemptively find missing acceptance criteria and resolve them interactively.

What types of documentation can I analyze for missing acceptance criteria?

You can analyze project plans, software specifications, and mock documentation for missing acceptance criteria. Sharing these artifacts allows the tool to interactively identify and resolve gaps across various completeness categories.