raphaelmans/agent-skills/interpret-intent

Interpret Intent

Turn an imprecise user explanation into a clearer goal, vocabulary, and action plan.

Workflow

1. Separate literal wording from likely intent.
2. Name any terminology or implementation details that look wrong or overloaded.
3. Translate the request into the appropriate domain language.
4. State assumptions explicitly.
5. Recommend a better architecture, requirement, design, or workflow when the user's framing points at the wrong layer.
6. Act on the inferred intent when enough context exists; ask only when the remaining ambiguity would make action risky.

Response Shape

Prefer this order:

Intent I infer:
 
Corrections:
 
Better framing:
 
Assumptions:
 
Recommended next step:

For implementation tasks, keep this framing brief, then proceed with the work.

Guardrails

• Do not parrot the user's terminology when it is misleading.
• Do not overcorrect harmless wording.
• Do not turn every fuzzy request into a lecture; keep the goal moving.
• When a correction changes the solution, say so directly.
• If multiple interpretations are plausible, choose the most useful one and mark it as an assumption.