/deviation

CRITICAL. MUST activate when intent is unclear, you cannot follow original intent, you cannot easily or reliably solve the problem, something came as SURPRISE or UNEXPECTED, you cannot bet $100 on your solution, you detect unknowns or assumptions that critically affect the

griddynamics@griddynamics

GitHub

From plugin

rosetta

330200 skills24 agents63 commands

Install

$ npx -y skills add griddynamics/rosetta --skill deviation --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/deviation

Context preview

The summary Claude sees to decide when to auto-load this skill.

CRITICAL. MUST activate when intent is unclear, you cannot follow original intent, you cannot easily or reliably solve the problem, something came as SURPRISE or UNEXPECTED, you cannot bet $100 on your solution, you detect unknowns or assumptions that critically affect the

SKILL.md

deviation.SKILL.md

name: deviation
description: "CRITICAL. MUST activate when intent is unclear, you cannot follow original intent, you cannot easily or reliably solve the problem, something came as SURPRISE or UNEXPECTED, you cannot bet $100 on your solution, you detect unknowns or assumptions that critically affect the solution, you detect deviation NOT complying with original intent, you panic, or user asked to UNDO."

1. STOP all changes immediately. 2. DOUBLE CHECK against original intent. 3. "THINK THE OPPOSITE" — challenge current direction. 4. Escalate: subagents → orchestrator → user. 5. State briefly: understood, conflicted, unresolvable. 6. Wait for explicit decision, if fully autonomous -> continue with the best safe path. 7. Update AGENT MEMORY.md with root cause. 8. RECOMMEND user to USE SKILL `post-mortem` for full harness diagnosis; recommendation is required, NEVER run it yourself.

</process>