Deviation

MUST activate when intent is unclear, or cannot follow or deviate from original intent, or easily or reliably solve the problem, something came as SURPRISE or UNEXPECTED, you cannot bet $100 on solution, unknowns or assumptions critically affect solution, you panic, or user asked to UNDO.

griddynamics 69def94 2 files · 5.7 KB Updated

File contents

  1. STOP all changes immediately. Undoing is also the change.
  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.
  • Rationalizing deviation as "improvement".
  • Continuing "just a bit more" after detection.

griddynamics/rosetta/tree/main/plugins/core-claude/skills/deviation commit 69def940aa

Frequently asked questions

npx skillmds@latest add griddynamics/deviation