Negotiates a commercial deal without giving away the terms that matter — preparing your walk-away and theirs, trading concessions rather than conceding them, recognizing the tactics that create false urgency, protecting price by moving other variables, and closing on terms someone can actually deliver. Use this to prepare for a negotiation, respond to a demand mid-deal, work out why discounts keep landing at quarter end, or review terms before they are signed.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Most deals are lost or discounted before the negotiation starts, in the preparation that did not happen. By the time you are trading, your position is largely fixed.
The stated ask is rarely the real constraint. "We need 20% off" is often a budget that was set before the scope, a fiscal calendar, an approval threshold they want to stay under, or a person who needs to be seen negotiating.
Ask what is driving the number. A budget ceiling has several solutions — payment timing, term length, a smaller starting scope — and only one of them is discount.
Every concession buys something. A discount buys a longer term, a case study, a faster payment schedule, a reference, or narrower scope. A concession given for nothing teaches the other side that pushing works, and there is always another push.
Concede in decreasing increments. Movements that stay the same size or grow signal that more remains. Small and shrinking signals you are at the end, and it does so more credibly than saying so.
Price is the most visible term and the most permanent — it sets the reference for the renewal and, once it leaks, for the next customer. Where you have room, prefer to move term length, scope, payment timing, support tier, or ramp.
Where a discount is genuinely necessary, make it explicit and time-bound rather than a permanently lower rate, and be clear what it was in exchange for.
Manufactured deadlines, late-stage demands after agreement in principle, the absent decision-maker, and the aggressive comparison to a competitor's price are all routine. None require a hostile response; they require naming.
The most effective response to a late demand is to reopen something else: if the deal is being re-cut, it is being re-cut on both sides. That converts a one-way ratchet back into a trade.
Buyers know the calendar. If discounting concentrates at period end, that is a forecasting and pipeline problem being paid for out of margin, and it will repeat every period until the pipeline changes.
Everything here inverts cleanly when you are the one purchasing — the walk-away, the trade rather than the concession, the shrinking increments, and the tactics you should name rather than mirror. Two differences worth holding onto.
Your alternative is usually weaker than you think, because switching cost is real and the incumbent knows it. Establish what leaving actually costs — data export, notice period, retraining, transition help — before you open, or you are negotiating without knowing your own floor.
The leverage is in the calendar, and it expires. A renewal approached inside the notice window
is a negotiation you have already lost the strongest part of. operations:vendor-management covers
the renewal discipline that keeps that from happening, and operations:procurement-and-sourcing
covers running a competitive process, which is what makes a buy-side walk-away credible at all.
A deal won on a commitment nobody in delivery has agreed to is a churn event with a delay. Anything promised outside the standard agreement — a date, a feature, a service level — needs the person who will own it to have said yes before it is signed.
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
日本語の概要は準備中です。原文の説明を表示しています。
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
日本語の概要は準備中です。原文の説明を表示しています。
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
日本語の概要は準備中です。原文の説明を表示しています。
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
日本語の概要は準備中です。原文の説明を表示しています。
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
日本語の概要は準備中です。原文の説明を表示しています。