菜单
Surfaces sources that disagree and resolves the conflict by keeping one side and marking the other superseded and stale. Use when two documents or decisions contradict each other.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | resolve-conflicts |
| description | Surfaces sources that disagree and resolves the conflict by keeping one side and marking the other superseded and stale. Use when two documents or decisions contradict each other. |
| version | 0.1.0 |
| triggers | ["these disagree","which is correct","conflict","contradiction"] |
| tools | ["Vitrus:conflicts","Vitrus:resolve_conflict"] |
When sources disagree, surface both sides — then resolve cleanly without silent overwrites.
Vitrus:conflicts to list contradictions with both sides (slug + title) and whether each is open or resolved.Vitrus:resolve_conflict with keep = winning slug and supersede = losing slug, plus a reason. The loser is marked stale and the conflict resolved in the markdown source.Never overwrite the loser silently. Supersede leaves an auditable trail of what changed and why.