surveying-blind-spots

Run a blind-spot pass that explores the target area's entry points, config surface, and core files, then mines git history for fix, revert, and workaround commits. The result is a briefing of unknown unknowns, gotchas with evidence, and vocabulary for better prompting.

A blind-spot survey is a one-shot briefing that surfaces what you do not know, without testing or gating on mastery. Quizzing is a tutoring loop that teaches and verifies understanding; use it after the survey if you want to confirm comprehension.

Yes. For domains rather than code, the pass maps core concepts, search vocabulary, standard tools, and classic beginner traps from existing knowledge, then verifies version-sensitive or time-sensitive claims with web search.

Skip it when you want to be taught to mastery, when you are ready to converge a design through Q and A, or when you need a cited multi-source research report. Those cases call for tutoring, brainstorming, or research skills instead.

Reviewing recent commits for messages containing fix, revert, workaround, or hack reveals where previous developers hit dead ends. Repeated churn on one file marks a problem area, and TODO, FIXME, and HACK comments record gotchas the authors pinned deliberately.