deviation

Featured

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.

AI & Automation 324 stars 60 forks Updated 2 days ago Apache-2.0

Install

View on GitHub

Quality Score: 92/100

Stars 20%
84
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
33
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<deviation> <process> 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> <pitfalls> - Rationalizing deviation as "improvement". - Continuing "just a bit more" after detection. </pitfalls> </deviation>

Details

Author
griddynamics
Repository
griddynamics/rosetta
Created
5 months ago
Last Updated
2 days ago
Language
TypeScript
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category