Find Gaps

Most shipped bugs and post-launch firedrills come from things that were never written down — not from things that were specified wrong. This skill systematically surfaces those absences before implementation, when fixing them is cheap.

But finding gaps is only half the job. A list of open questions that nobody answers is just a todo list with extra steps. The real output of this skill is an updated artifact — a plan, AC set, or mock spec that now contains decisions it didn't contain before, made by the user, captured verbatim, and written back to the source of truth.

When to Use This Skill

Use this skill when the user:

• Asks "what's missing?", "find gaps", "poke holes in this", "what could go wrong?", "help me tighten this up"
• Shares a plan, spec, acceptance criteria, or design mocks and asks for review
• Is about to start implementing and wants a pre-implementation sanity check
• Is handing work to another team/engineer and wants a completeness pass
• Is doing a pre-mortem

Pair with storyboard when reviewing multiple mocks together — storyboard gives the single-page view, this skill finds what's missing across them. Pair with story-splitting when a story, plan, spec, or backlog item is too large, horizontal, component-split, or not yet expressed as independently valuable child stories. Pair with characterisation-tests when the "gap" is behavior of existing code that nobody wrote down.