Find Gaps

Surface what an in-progress artifact is missing — many parallel lenses, scored findings, walked one at a time.

When to use

You have a draft, answer, or code and want to surface what you missed — blind spots, risks, overlooked angles.

• NOT this if you want one synthesized answer → best-answer.
• NOT this if you want a yes/no trust signal on an answer you have → validate-answer.
• NOT this if you're grading one concrete proposal → second-opinion.

Steps

Step 1 — Frame and derive lenses

• Derive lenses from the artifact's risk surface — orthogonal angles that together cover what could be wrong or improvable (for a skill: resumability, failure-modes, coherence-with-siblings, UX; for a spec: scope, architecture, edge cases). One lens per subagent; merge near-duplicates — overlap re-raises one finding and wastes the fan-out. Every run also carries one standing lens: unstated assumptions — what the artifact treats as settled but never justifies.
• Count: default 3–5 lenses; scale up only for a broad audit. If the user named the exact lenses, honor them and skip the checkpoint; if partial, honor those and fill any gap.
• Checkpoint: print the lens list (one line each) and confirm via AskUserQuestion ("Run these" / "Adjust").