Prompt file imported from Vescik/sf-extension-harness (
.github/prompts/search-knowledge.prompt.md). Copyright stays with the author.
Use the search-knowledge skill.
Require at least one filter (keyword, text, subject, error, or a dependency lookup
via anchor=<Identity> — the skill's --relation-anchor search; ask once with
#tool:vscode/askQuestions if none was given) and pass the rest through as narrowing filters.
Route by question type: repository-source facts (what a component declares, what touches a field,
which Flow emits a pasted message) come from approved Knowledge Entries; org usage numbers come
from unexpired entry orgUsage blocks; org state beyond that needs a fresh governed receipt,
and business meaning or vendor guarantees have no governed Knowledge surface — report the gap
honestly instead of inferring. Never present a stale index or a missing hit as proof of absence.
This command is read-only: it never creates, promotes, or edits Knowledge. Present effective
facts first, then non-effective matches with their reasons, and finish with gaps worth
investigating (/investigate-object) or drafting (/pin-knowledge, /curate-knowledge).