Blindspot Pass

Use this skill to shrink ambiguity before code, plans, PRDs, launches, migrations, or operator/user-facing changes. The goal is not to ask every possible question. The goal is to find the few unknowns that would make the current path wrong.

Rules

• Read the territory before theorizing: repo docs, code, tests, notes, business context, and current behavior where relevant.
• Prefer evidence over generic best practice.
• Do not edit product code during a blindspot pass unless the user explicitly asks you to continue into implementation.
• Ask only questions the repo/context cannot answer and where the answer changes scope, architecture, UX, sequencing, risk, or success criteria.
• Include a recommended default with each question.
• Split independent surfaces across subagents when the work is large and subagents are available.
• Keep output concise. This is a decision aid, not a research report.

Context Anchors

Check these sources before making recommendations when they exist: