tribal-knowledge
by TenexTony
Dig undocumented institutional knowledge out of a company's record — Slack, email, docs, tickets, CRM, code, meeting notes — and return an answer where every claim carries a link back to where it came from. Opens by inventorying which sources are actually connected, then interviewing for the outcome. Use this whenever someone asks why their org does something a particular way, what was decided about something and why, what a new hire or a handoff needs to know, what only lives in one person's head, whether something is written down anywhere, or wants to surface a precedent, pattern, or story out of company history. Also use it when someone says "search our Slack/Notion/email for X" but what they actually need is a sourced answer rather than a pile of search hits.