blindspot-pass

# Blind Spot Pass ## When to Use Use this skill **before starting implementation** when: - Working on an unfamiliar part of the codebase - Integrating with systems you don't fully understand - The task has high stakes or complexity - You sense there might be hidden gotchas ## What It Does A blind spot pass helps identify **unknown unknowns** that could derail implementation or lead to poor architectural decisions. ## How to Execute ### Step 1: Define Scope Clearly state what you're about to work on: - Feature or change description - Affected modules/systems - Current understanding level ### Step 2: Search for Context Look in multiple places for relevant history: ```bash # Recent changes to related files git log --oneline --all -20 -- path/to/module/ # Search commit messages for keywords git log --all --grep="auth\|oauth\|provider" --oneline # Find related discussions in code comments rg -i "TODO|FIXME|HACK|XXX" path/to/module/ # Search for error handling patterns rg "catch|throw|error" path/to/module/ -A 3 ``` ### Step 3: Identify Gotchas Document findings in categories: **Technical Gotchas**: - Edge cases in existing code - Performance considerations - Error handling patterns - Testing requirements **Architectural Gotchas**: - Existing abstractions to follow - Integration points - Data flow patterns - State management approaches **Business Gotchas**: - Implicit requirements from past discussions - Feature flags or phased rollouts - Backward compatibility ne...