blindspotlisted

# Blindspot Pass — Blind-Spot Investigation Before implementation, find the **gap between the map (plan/prompt) and the territory (actual codebase, domain, constraints)**. Origin: Blindspot Pass — see skills/loop/references/talk-source.md ## Iron Rules 1. **Do not implement yet.** No code changes while this skill is active. 2. End goal of the investigation: help the user **write a better prompt**. ## Procedure 1. Parse task description and context sources from `$ARGUMENTS`. Empty → the task currently under discussion; if there is none, ask one question first. If sources are given (git history, docs, specific modules, etc.), investigate those first. 2. Scope codebase-wide or large → spawn the `unknowns:unknowns-scout` agent with the Agent tool. Hand it a packet: the user's original prompt verbatim, the context sources, the target area and its entry points, and what to return (finding table + improved prompt draft); map its rows onto the card kinds below. Scope is a few files → investigate directly with Read/Grep/Glob. 3. Compile findings, each tagged with a kind: - **Landmine** — touching this breaks something non-obvious (regression risk, fragile or missing tests, a module mid-migration) - **Convention** — an unwritten rule the codebase enforces - **Missing concept** — a mechanism the user's prompt has no word for - **History** — an earlier or reverted attempt at this exact task Also collect the **questions to answer** and the **info