Menü
Surfaces what the company brain does not know: missing, stale, contradicted, single-point and uncited knowledge. Use before relying on the brain for a high-stakes task.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | surface-gaps |
| description | Surfaces what the company brain does not know: missing, stale, contradicted, single-point and uncited knowledge. Use before relying on the brain for a high-stakes task. |
| version | 0.1.0 |
| triggers | ["what don't we know","what's missing","gaps","blind spots"] |
| tools | ["Vitrus:gap_report"] |
The brain's honesty is its edge: it states what it does not know, deterministically.
Vitrus:gap_report. It returns gaps by kind:
A gap is not a failure — it is a to-do. Reporting it beats silently guessing.
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.
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.