When a DSAR or litigation hold lands in your inbox, /legal-response drafts the reply from your templates with built-in escalation checks. — Claude Skill

/legal-response -- Generate Response from Templates

Generate a response to a common legal inquiry using configured templates. Customizes the response with specific details and includes escalation triggers for situations that should not use a templated response.

Important: This command assists with legal workflows but does not provide legal advice. Generated responses should be reviewed by qualified legal professionals before being sent, especially for regulated communications.

Common inquiry types

• dsr / data-subject-request -- Data subject access/deletion/correction requests
• hold / discovery-hold -- Litigation hold notices
• vendor / vendor-question -- Vendor legal questions
• nda / nda-request -- NDA requests from business teams
• privacy / privacy-inquiry -- Privacy-related questions
• subpoena -- Subpoena or legal process responses
• insurance -- Insurance claim notifications
• custom -- Use a custom template

Workflow

1. Identify Inquiry Type — accept type from user; if ambiguous, show categories.
2. Load Template — look in local settings (legal.local.md or templates dir). If none, offer to help create one or use a default structure.
3. Check Escalation Triggers — before generating, evaluate whether this situation should NOT use a templated response.
4. Gather Specific Details — prompt for variables (requester name, dates, references, scope, jurisdiction).
5. Generate Response — populate template, customize tone, present draft for review.
6. Template Creation — if no template exists, walk through creation guide.

Universal Escalation Triggers (apply to all categories)

• Matter involves potential litigation or regulatory investigation
• Inquiry from a regulator, government agency, or law enforcement
• Response could create a binding legal commitment or waiver
• Matter involves potential criminal liability
• Media attention involved or likely
• Situation is unprecedented (no prior handling by team)
• Multiple jurisdictions with conflicting requirements
• Matter involves executive leadership or board members

Category-Specific Escalation Triggers

Data Subject Request

• Request involves a minor's data
• From a regulatory authority (not individual)
• Data subject to litigation hold
• Requester is current/former employee with active dispute
• Unusually broad scope or fishing expedition
• Special category data (health, biometric, genetic)

Discovery Hold

• Potential criminal liability
• Preservation scope unclear or disputed
• Prior holds for related matter
• Hold conflicts with regulatory deletion requirements

Vendor Question

• Dispute or potential breach
• Vendor threatening litigation/termination
• Regulatory compliance question
• Could create binding commitment

NDA Request

• Counterparty is a competitor
• Government classified information
• Potential M&A context
• Unusual subject matter (AI training data, biometric)

Subpoena / Legal Process

• ALWAYS requires counsel review (templates are starting points only)

When escalation trigger detected

1. Stop: do not generate templated response
2. Alert: inform user
3. Explain: which trigger and why
4. Recommend: appropriate escalation path
5. Offer: draft for counsel review only ("DRAFT - FOR COUNSEL REVIEW ONLY")

Response Categories with Template Structure

Data Subject Requests (DSRs)

Sub-categories: acknowledgment, verification request, fulfillment, partial denial, full denial, extension notification. Required elements: applicable regulation, timeline, identity verification, rights of data subject, contact info.

Discovery Holds

Sub-categories: initial hold notice, reminder/reaffirmation, scope modification, hold release. Required elements: matter name and reference, preservation obligations, scope (date range, data types, systems), prohibition on spoliation, acknowledgment requirement.

Privacy Inquiries

Sub-categories: cookie/tracking, privacy policy, data sharing, children's data, cross-border transfer.

Vendor Legal Questions

Sub-categories: contract status, amendment request, compliance certification, audit request, insurance certificate.

NDA Requests

Sub-categories: send standard form, accept counterparty NDA with markup, decline with explanation, renewal/extension.

Subpoena / Legal Process

Sub-categories: acknowledgment, objection letter, extension request, compliance cover letter. Critical: subpoena responses almost always require individualized counsel review.

Insurance Notifications

Sub-categories: initial claim, supplemental information, reservation of rights response.

Customization Guidelines

Required: correct names/dates/references, specific facts, applicable jurisdiction and regulation, correct response deadlines, signature block.

Tone adjustment by audience (internal/external, business/legal, individual/regulatory), relationship (new/existing/adversarial), sensitivity (routine/contentious/investigation), urgency.

Jurisdiction-specific: verify cited regulations, adjust timelines to applicable law, include jurisdiction-specific rights, use appropriate terminology.

Template Lifecycle

Creation → Review → Publication → Use → Feedback → Update → Retirement.

Each template should include: category, name, use case, escalation triggers, required variables, body with placeholders, follow-up actions, last reviewed date.

Notes

• Always present draft for user review before suggesting it be sent
• If connected to email via MCP, offer to create a draft email
• Track response deadlines, offer calendar reminders
• For regulated responses (DSRs, subpoenas), always note applicable deadlines
• Templates should be living documents — suggest updates when modified