The four pillars separate people from the problem, distinguish positions and interests, generate possible mutual-gain options before evaluating them, and use relevant objective criteria. Criteria need sources, dates, comparability and limits; they support a discussion without eliminating judgement or power differences. BATNA and ZOPA keep alternatives and acceptable terms explicit.
The seven instructions begin with a diagnosis and both parties’ positions and interests. They distinguish a feasible fallback from a prospect, and rate BATNA strength only to the extent supported; unknown is a valid outcome. The other party’s possible alternatives remain labelled assumptions, followed by a proposed preparation action.
The instructions distinguish confirmed, hypothetical and unknown ZOPA, using the appropriate buyer or seller role. At least five proposed packages use variables beyond price; a price adjustment can be tied to duration, scope or another term. Each shows what is offered and requested, the period and relevant unknown costs. The opening asks about unconfirmed interests rather than pretending they were disclosed.
Before anything gets worked out, the skill runs through a mandatory input checklist: what is being negotiated and what is currently on the table, who the counterparty is and what role that person has within their own organisation, your goal in a number or a concrete condition, what you actually do if the deal falls through, your floor and whether that is yours or someone else's in your business, what you already know about the pressure the counterparty is under, and whether the relationship continues after this deal or is a one-off.
Ask for missing essentials together where practical, then produce a provisional analysis with explicit unknowns. Follow up if missing information would change a commitment. Do not guess the user’s authority, minimum or a confirmed offer simply to complete the template.
The eight output blocks remain: situation diagnosis, positions and interests, BATNA analysis, ZOPA and walk-away point, five or more proposed packages, objective criteria, opening and objections, and source and rationale. Packages identify offered and requested terms, price periods, calculable revenue differences and unknown costs. A discount is not automatically a profit calculation.
Here too, remarkably many rules are about language. The file requires the you-form, forbids dashes in running text, forbids rule-of-three lists, and keeps a list of AI words that may not be used. There is one more rule specific to this skill that makes the difference: conversation lines are written as spoken language, because you need to be able to say them out loud without cringing. You can hear that in the opening line in FIG.01, which sounds like someone talking, not someone reading aloud.
Finally, the file has a separate mode for reviewing existing work. Hand it a proposal, an email exchange or a planned approach, and you get five things back: a diagnosis of where the weakness lies, a marking per passage placing POSITION or INTEREST before the relevant sentences so you can see how positional your writing is, a list of what is missing from the checklist, a concession analysis flagging every concession made without a counter-ask, and a rewritten version in the standard output structure. If you want to learn how to set up an instruction file like this yourself, writing a SKILL.md NL explains how that structure works.