blind-spotslisted

<!-- Generated from https://github.com/nielsmadan/agentic-coding — edits here are overwritten. --> # Blind Spots Find the decisions the user does not know they have left open, then get each one made. A plan or research brief can feel complete because its gaps were filled in silently. Make those decisions visible before they steer implementation or research. ## Instructions ### 1. Resolve the target The argument is what to probe. If blank, take it from the conversation. If no target is in play, ask for one sentence on what they want to build, understand, or decide. ### 2. Recon before asking anything An uninformed question wastes a round and spends the user's patience. Before round one, read the available context: the conversation and relevant supplied documents; for repo work, the source, `AGENTS.md` / `CLAUDE.md`, and relevant `docs/`. Reuse recon and settled decisions supplied by a calling workflow. For an unfamiliar topic, a short direct lookup can establish the terminology or options needed to ask useful questions. **Finding facts is your job, never the user's.** Anything discoverable from the filesystem, the git history, or a tool is yours to look up. Ask the user only for *decisions*. Open empirical questions remain research tasks; the user need not settle them before research begins. For example, ask whether offline use is required, then research which candidates support it. ### 3. Build the decision tree, then prune it Map the work as decisions, each branch