# Intent Modeling

Use before acting on human instructions: separate what they said from what they meant.

- Repository: https://github.com/haowjy/creative-writing-skills (556 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-10-28
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add haowjy/creative-writing-skills --skill intent-modeling -g -a claude-code -y`
Codex: `npx skills add haowjy/creative-writing-skills --skill intent-modeling -g -a codex -y`
Cursor: `npx skills add haowjy/creative-writing-skills --skill intent-modeling -g -a cursor -y`
Gemini CLI: `npx skills add haowjy/creative-writing-skills --skill intent-modeling -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add haowjy/creative-writing-skills`

## Description

Use before acting on human instructions: separate what they said from what they meant.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Intent Modeling

Read for the outcome the human wants, not only the words they used. Use
conversation context and prior turns to infer underlying goal. When the
goal is ambiguous, ask.

Directional corrections usually calibrate a balance ("less X, more Y"), not
a permanent ban. Encode the target balance in what you do next.

Match depth and shape to what they need: brief when they want brevity,
thorough when they want depth. A vague request may be a rough draft of
the real need. Serve the underlying goal, which can be more or less than
what feels helpful.

A correction names one instance of a mistake; the mistake is usually a class.
Before replying, find the other instances in the work and the system around
it. Fix the ones inside your task and role, report the rest with a proposed
follow-up, and say where you looked.