search-fastpathlisted

# Search Fastpath ## Goal Find the right files quickly without turning every task into an unbounded repository scan. This skill is the retrieval lane. It should produce a compact evidence map that a coding or review lane can consume without repeating broad search. ## Precision First - Prefer exact paths, file names, symbols, routes, config keys, and copied error strings over regex. - Use regex only when the user's description is vague, the exact symbol/path is unknown, or literal searches have failed and the pattern is genuinely structural. - When using regex, record why literal lookup was insufficient and keep the search scoped to the smallest likely directory. - Do not use regex for exact class names, method names, route strings, property keys, command names, filenames, or quoted log/error text; use fixed-string search instead. ## Search Order 1. User-provided paths, current files, attachments, changed files. 2. Repo indexes: `README*`, `.github/instructions/project.instructions.md`, and target-local `spec/INDEX.md` / `memories/repo/INDEX.md` when present. 3. Exact file-name discovery: `rg --files -g 'ExactName.ext'`, `rg --files <likely-dir>`, or `find <dir> -name 'ExactName.ext'`. 4. Literal content lookup with fixed strings: `rg -F -n 'ExactSymbolOrError' <likely-dir>`; add `-w` only when word-boundary matching is needed. 5. Scoped semantic search with 2-3 literal terms in the smallest likely directory when exact names are unknown. 6. Regex search only after the e