From pm-simulators
Simulate the car-buying gauntlet before you walk in — the four-square worksheet, the payment-question trap, the trade-in shuffle, and the finance office's second sales floor, all run against your actual deal. Use when asked practice negotiating at a dealership, simulate the finance office, what tricks will the dealer use, or prep me before I buy a car. Produces the showroom and finance-office transcripts with the salesperson's playbook notes, the deal outcome vs your targets, and a debrief with the holds that would have worked.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-simulators:the-car-dealershipThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The dealership is two negotiations wearing one showroom: the car price out front, and the *finance office* in back — where the real margin often lives, sold to a buyer whose guard dropped the moment they heard "congratulations." This skill runs both rooms against your actual numbers: the four-square worksheet that blends price/trade/payment into fog, the "what payment works for you?" trap, the ...
The dealership is two negotiations wearing one showroom: the car price out front, and the finance office in back — where the real margin often lives, sold to a buyer whose guard dropped the moment they heard "congratulations." This skill runs both rooms against your actual numbers: the four-square worksheet that blends price/trade/payment into fog, the "what payment works for you?" trap, the trade-in shuffle, and then the F&I gauntlet of add-ons and rate markup. Every move gets named in the dealer's private notes, and the debrief hands you the exact holds.
Ask for these if not provided:
Room one — the showroom moves: the payment question ("what monthly works for you?" — answering it surrenders the price; the counter is "let's settle the out-the-door price first") · the four-square (price, trade, down, payment on one sheet — fog by design; the counter is one number at a time, out-the-door) · the trade-in shuffle (great car price, terrible trade number, or vice versa — the counter is negotiating them as separate transactions) · the manager walk ("let me talk to my manager" — theater and a pacing device) · the today-only urgency (the deal that dies at midnight rarely does).
Room two — the finance office: the rate markup (the quoted APR may carry dealer reserve — the counter is your pre-approval on the desk: "beat this or use it") · the add-on cascade (VIN etching, paint protection, nitrogen, extended warranty, GAP — each priced at 3–10× cost; some, like GAP on a long loan, are legitimately worth pricing elsewhere) · the payment-packing move (add-ons quoted as "just $9 more a month" — ×72 months, out loud, every time) · the menu close (three columns of bundles, none labeled "none of these" — that column exists; ask for it).
Mechanics to honor: out-the-door price is the only number that can't be shuffled · everything is negotiable until signed, nothing after · the walk-out is a legitimate and often winning move, and one run should show it working · four hours in the building is a tactic, not bad luck.
Simulation — a plausible adversarial reading, not a prediction.
[Transcript. Dealer's note: after each move, naming the play and reading you: "asked their payment — they answered. Working payment now, price is loose."]
[Transcript: rate, add-ons, menu — with the ×72 math shown wherever "per month" appears]
[Deal vs. targets · the dealer's notes on where you left money · the walk-out branch: what re-engagement looked like]
| Moment you softened | The move | The hold (exact words) |
|---|---|---|
| [Plus: the crib sheet — out-the-door only · trade separate · pre-approval on the desk · ×months every add-on · the none-column ask] |
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-simulatorsGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.