What problem does it solve? Written artifacts like plans, acceptance criteria, and design mocks often ship with silent omissions — missing error states, unverifiable criteria, unstated assumptions — that turn into bugs and rework after implementation begins. This Skill adversarially reviews an existing artifact and closes those gaps before coding starts. ## Core Features & Use Cases - Checklist-driven gap discovery: Walks dedicated checklists for plans, acceptance criteria, and design mocks covering failure modes, edge cases, roles, accessibility, i18n, and observability. - Interactive gap-closing loop: Triages findings into Blocker / Should-address / Nice-to-have, then asks one question at a time and writes each confirmed answer back into the artifact as a new acceptance criterion, plan section, or mock state spec. - Resolution log output: Produces a session log of resolved and parked gaps with named owners, suitable for PR descriptions or release notes. - Use Case: Before handing a feature spec to engineers, run this Skill to catch that the contacts list has no empty state, the migration has no rollback path, and the 'fast' criterion has no measurable target — then capture the decisions directly into the document. ## Quick Start Ask the assistant to use the find-gaps skill to poke holes in your current plan, acceptance criteria, or design mock and write the confirmed decisions back into the document.
