Menu
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.
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.
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.
| name | capture-decision |
| description | 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. |
| version | 0.1.0 |
| triggers | ["we decided","the decision is","record this decision","going forward we will"] |
| tools | ["Vitrus:record_decision"] |
The brain stays live only if decisions are written back. Do it the moment a decision is reached.
Vitrus:record_decision with: the decision (one line), the rationale, any source slugs/URLs, and supersedes/contradicts if it replaces or conflicts with prior knowledge.Write the reasoning, not just the outcome. A decision without its "why" cannot be re-evaluated later.