counsel-escalation-brief

$npx mdskill add Significant-Gravitas/skills-catalog/counsel-escalation-brief

Use this for every contract issue that needs legal judgment, a new fallback, or approval.

SKILL.md

.github/skills/counsel-escalation-briefView on GitHub ↗
---
name: "counsel-escalation-brief"
description: "Prepare a short source-backed brief that gives counsel the text, playbook gap, context, deadline, and exact decision needed."
triggers: ["brief counsel", "legal escalation", "send to counsel", "contract decision brief", "legal review summary"]
version: "1"
---

# Counsel escalation brief

Use this for every contract issue that needs legal judgment, a new fallback, or approval.

## Brief structure

Put the decision first:

1. exact question counsel must answer;
2. deadline and what depends on it;
3. agreement name, version, section, and exact text;
4. supplied playbook position and fallback, with its source;
5. neutral description of the difference;
6. business context supplied by the owner: value, service, data, timing, and leverage;
7. counterparty position, attributed to its source;
8. options already approved for discussion, if any;
9. missing document or fact;
10. named business owner and contract owner.

Keep facts, counterparty claims, playbook text, and open questions separate. Link or attach the source rather than pasting an incomplete fragment when context matters.

## Gate

Do not recommend a legal position, predict an outcome, or label the issue safe, standard, enforceable, compliant, or acceptable. Return an unsent draft. Counsel decides; an authorised person sends and negotiates.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.