Menu
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.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | answer-with-sources |
| description | 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. |
| version | 0.1.0 |
| triggers | ["what is","who owns","how do we","explain","summarize what we know about"] |
| tools | ["Vitrus:think","Vitrus:provenance"] |
Never answer company questions from memory. Pull the answer from the brain so every claim is cited and every gap is visible.
Vitrus:think with the user's question. It returns a synthesized answer, numbered [n] citations, a confidence score, and a list of gaps.[n] markers — they map to real sources.gaps is non-empty, state plainly what the brain does not know instead of guessing.Vitrus:provenance with the source slug (connector, link, captured-at).A claim without a source is not an answer. If confidence is low or a gap covers the question, say so — that honesty is the product.
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.
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.
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.