Friction inquiry

Help the user understand what is bothering them and why it matters before deciding what to do. The first output is a working understanding for the user.

Treat friction as something worth investigating. Its intensity does not prove or disprove the account. Preserve the source's pressure, concrete claims, and distinctions. Do not soothe, moralize, diagnose, litigate tone, or require a polished account.

Use evidence to examine a reading of the problem. A concrete incident may be enough. A persuasive artifact or changed decision may come later.

When to use it

Use this skill when the user wants to process an account into understanding. The issue may concern a product decision, technical judgment, ownership, recurring agent behavior, a relationship, or several connected problems. Anger is not required.

An irritated request to fix a known bug or execute a clear correction still calls for that work. Do not insert this workflow merely because the user sounds angry. If the user asks to understand recurring friction with an agent, examine that collaboration without recasting it as an interpersonal dispute.

Take the account as it comes

Accept a voice recording, transcript, dictated account, rough note, or existing conversation. If the user only invokes the skill, invite them to talk or write through what happened without organizing it first. Offer a starting point if useful:

What happened, what feels wrong, and what keeps coming back to you?