Use when preparing a structured briefing for a meeting with legal relevance — assembling background, participants, agenda, key documents, open issues, legal considerations, talking points, and a follow-up action-item tracker from the materials provided.
When to use
A user says "prepare me for this meeting," "build a briefing for this board meeting," or "get me ready for this negotiation."
A legal team member needs a structured briefing pack before a meeting with legal relevance.
The user needs a way to capture and track the action items that come out of a meeting.
Required inputs
Meeting context: the meeting title and type, date and time, the participants and their roles, the agenda or expected topics, and the legal team member's role in the meeting (advisor, presenter, negotiator, observer).
Background materials: the documents and records the user provides — prior correspondence, prior meeting notes, relevant agreements, matter records, the risk register, or deal documents. The skill briefs from the materials supplied; it does not pull information from calendars, email, CRM, CLM, or other external systems.
Negotiation parameters (for a negotiation meeting): the red lines or non-negotiable positions, if any have been set.
If the meeting context is missing, request it. If background materials are thin, proceed and flag the resulting preparation gaps explicitly.
Use when a document is believed final and ready to sign — to run a pre-signature completeness checklist, identify signers and signing order, flag blockers, and produce a routing plan for attorney review before the document is sent for execution.
When to use
A user says "is this ready to sign?", "set up signing for this contract," or "prepare this for signature."
A document is believed final and needs a pre-execution completeness check and a routing plan.
The user is verifying entity names, exhibits, and signature blocks before a document goes out for signature.
Required inputs
The document to be signed — uploaded, pasted, or precisely described.
The intended signers — names, titles, the entity each signer binds, and whether each signer is understood to be internally authorized.
Required internal approvals — which approvals the document needs and whether they have been obtained.
Signing preferences — sequential or parallel signing order, and any CC recipients for the executed copy.
If the document is not provided, stop and request it. If signer information is incomplete, ask before producing the routing plan.
Use when drafting a response to a routine, recurring legal inquiry from a configured template, with a built-in escalation gate that stops the templated path when the matter shows characteristics that require individualized counsel review.
When to use
A user says "draft a response to this data subject request," "respond to this vendor legal question," "send a litigation hold notice," or names another recurring inquiry type.
A recurring inquiry arrives that the legal team normally handles with a standard template.
The team needs a consistent first draft together with a check on whether the matter is routine enough to be templated at all.
Required inputs
The inquiry and its type — data subject request, litigation hold, vendor question, NDA request, privacy inquiry, subpoena, insurance notification, or another recurring category. If the type is unclear, ask before drafting.
The team's response template for that inquiry type, if one exists — the actual firm template. If none exists, the skill drafts a default structure and flags clearly that no approved template was used.
Customization facts: names, dates, reference numbers, the applicable jurisdiction and regulation, the date the inquiry was received, and the response deadline if known.
The audience and relationship — internal or external, business or legal, individual or regulator, routine or contentious — so tone can be set.
This skill drafts a response; it does not send anything.