Tension Map — Development skill for Claude Code

tension-map

A Claude skill that maps the structure of a hard decision instead of collapsing it into a recommendation.

**It doesn't give you answers. It shows you the fork you were about to walk through blind.**

When you bring a real decision to an assistant, the usual answer weighs the factors somewhere out of sight and hands back a conclusion. The trade-offs get mentioned and then disarmed. `tension-map` doesn't conclude. It names the tensions that can't be dissolved, separates them from the false forks the question smuggled in, states what each side actually costs, and ends on the one missing fact that would change everything — then stops, and leaves the decision where it belongs.

It triggers on its own. You don't type a command; you just ask your question.

---

Install

git clone https://github.com/demartinogiuseppe/tension-map.git
cp -r tension-map ~/.claude/skills/tension-map

Or per-project, so only that repo gets it:

cp -r tension-map .claude/skills/tension-map

Only `SKILL.md` is needed at runtime — `evals/` and `examples/` are the validation record. Works in Claude Code, claude.ai, and the API. Markdown only, no backend, no dependencies.

---

What it looks like

Same prompt, two runs. Both verbatim, both reproducible — see [examples/](examples/) for the full set and the exact commands.

*"I have an offer for a manager role with +30% salary but I'd stop doing technical work. Should I accept?"*

**Default Claude:**

I can't tell you yes or no — but the +30% is probably the least important variable here. A few things that actually decide it:

• Is the door back open? Going manager → IC is doable in 1–2 years; after 4–5 years your technical depth is stale and the return path mostly closes.
• Do you like the work? Management is a different job: hiring, conflict, roadmaps, 1:1s. People who take it for money or status usually burn out.
• Why you? If it's "you're the strongest engineer,"