Meta-YGN

Synchronize the Obsidian vault (Meta-YGN/) with the current codebase state. Use after releases, major changes, or when vault docs may be stale.

Run a minimal metacognitive evaluation pass over the current task or repository change. Use to assess quality, calibration, and overhead.

Pressure-test the current plan or conclusion. Use when reasoning may be too linear, confidence seems too high, or there are plausible counter-hypotheses.

Compact the session into goal, verified facts, dead ends, open risks, and next actions. Use before long sessions, handoffs, context limits, or after repeated failed attempts.

Escalate when uncertainty is too high, risk exceeds agent capability, or human judgment is required. Use when verification fails, threats are found, or the agent is stuck.

Classify the task, identify risk, choose a strategy, and set a proof plan before non-trivial work. Use for architecture, migrations, auth, billing, concurrency, large refactors, or whenever failure would be costly.

Build a proof packet before finalizing work. Use for risky edits, architecture claims, dependency changes, security-sensitive work, and any answer that could mislead a reviewer.

Review a task for prompt-injection, exfiltration, secrets, approval, and trust-boundary risks. Use before networked tools, MCP, auth flows, production actions, or security-sensitive edits.

Decide whether tool use is necessary, excessive, or unsafe. Use before reaching for MCP, networked tools, or repetitive tool loops.