Menu
Finds who owns or is responsible for a service, decision or area by traversing the typed knowledge graph and entity index. Use when someone needs to know who to talk to about X.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Answers a question from the company brain with cited sources and an honest list of what is not documented yet. Use when someone asks a factual question about the company, its systems, people, decisions or incidents.
Records a decision and its rationale back into the company brain after it is made, with sources, and detects supersede and contradiction effects. Use immediately after an architectural or process decision is reached.
Triages what needs human attention now: stale durable knowledge, unresolved incidents and aging gaps, ranked by severity and age. Use at the start of a work session or on-call shift.
Helps a newcomer learn an unfamiliar area of the company or codebase by mapping its key entities, owners and decisions from the brain. Use in the first days on a new team, service or domain.
Reviews the company as a system and flags operational risks: unowned services, single-person bus-factor, bottlenecks, broken handoffs and redundant tools, each citing the real nodes behind it. Use for a health check or before reorganizing.
Captures an ad-hoc note, idea or piece of context into the company brain in one step. Use when something worth remembering surfaces mid-task and should not be lost.
| name | find-the-owner |
| description | Finds who owns or is responsible for a service, decision or area by traversing the typed knowledge graph and entity index. Use when someone needs to know who to talk to about X. |
| version | 0.1.0 |
| triggers | ["who owns","who is responsible for","who do I ask about","who runs"] |
| tools | ["Vitrus:graph_query","Vitrus:entities","Vitrus:search"] |
The graph already encodes ownership — read it instead of guessing.
Vitrus:search for the service/decision to get its slug.Vitrus:graph_query with that slug and edgeType owns (or reports_to for people, depends_on for systems).Vitrus:entities lists people/teams by mention frequency.If no owner edge exists, that is an unowned finding — report the gap and suggest assigning an owner, do not invent one.