deviation

Solid

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 344 stars 75 forks Updated 1 weeks ago Apache-2.0

Install

View on GitHub

Quality Score: 86/100

Stars 20%
85
Recency 20%
90
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
7 months ago
Last Updated
1 weeks ago
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

self-learning

MUST activate on: execution failure/error, mistake, wrong/unexpected result, expected≠actual mismatch, 2 consecutive mismatches, unhappy/upset user, user asks why something failed/didn't work.

344 Updated 1 weeks ago
griddynamics
AI & Automation Listed

underthinking-detector

Use when implementation, parking, blocking, strategy switching, or completion happens before critical understanding and evidence exist.

3 Updated 3 weeks ago
ihabkhaled
AI & Automation Listed

decision-readiness

Use when an important implementation, architecture, security, data, or delivery decision rests on unresolved critical unknowns.

3 Updated 3 weeks ago
ihabkhaled