/legal-response -- Generate Response from Templates

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

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.

Invocation

/legal-response [inquiry-type]

Common inquiry types:

If no inquiry type is provided, ask the user what type of response they need and show available categories.

Workflow

Step 1: Identify Inquiry Type

Accept the inquiry type from the user. If the type is ambiguous, show available categories and ask for clarification.

Step 2: Load Template

Look for templates in local settings (e.g., legal.local.md or a templates directory).

If templates are configured:

If no templates are configured:

Step 3: Check Escalation Triggers

Before generating any response, evaluate whether this situation has characteristics that should NOT use a templated response.

Universal Escalation Triggers (Apply to All Categories)

Data Subject Request Escalation Triggers

Discovery Hold Escalation Triggers

Vendor Question Escalation Triggers

NDA Request Escalation Triggers

Subpoena / Legal Process Escalation Triggers

When an escalation trigger is detected:

  1. Stop: Do not generate a templated response
  2. Alert: Inform the user that an escalation trigger has been detected
  3. Explain: Describe which trigger was detected and why it matters
  4. Recommend: Suggest the appropriate escalation path (senior counsel, outside counsel, specific team member)
  5. Offer: Provide a draft for counsel review (clearly marked as "DRAFT - FOR COUNSEL REVIEW ONLY") rather than a final response

Step 4: Gather Specific Details

Prompt the user for the details needed to customize the response:

Data Subject Request:

Discovery Hold:

Vendor Question:

NDA Request:

Step 5: Generate Response

Populate the template with the gathered details. Ensure the response:

Present the draft response to the user for review before sending.

Customization Guidelines

Required customization — Every templated response MUST be customized with:

Tone adjustment — Adjust tone based on:

Jurisdiction-specific adjustments:

Step 6: Template Creation (If No Template Exists)

If the user wants to create a new template, walk through the Template Creation Guide (see below) and present the finished template for review. Suggest the user save the approved template to their local settings for future use.

Response Categories

1. Data Subject Requests (DSRs)

Sub-categories:

Key template elements:

Example template structure:

Subject: Your Data [Access/Deletion/Correction] Request - Reference {{request_id}}

Dear {{requester_name}},

We have received your request dated {{request_date}} to [access/delete/correct] your personal data under [applicable regulation].

[Acknowledgment / verification request / fulfillment details / denial basis]

We will respond substantively by {{response_deadline}}.

[Contact information]
[Rights information]

2. Discovery Holds (Litigation Holds)

Sub-categories:

Key template elements:

Example template structure:

Subject: LEGAL HOLD NOTICE - {{matter_name}} - Action Required

PRIVILEGED AND CONFIDENTIAL
ATTORNEY-CLIENT COMMUNICATION

Dear {{custodian_name}},

You are receiving this notice because you may possess documents, communications, or data relevant to the matter referenced above.

PRESERVATION OBLIGATION:
Effective immediately, you must preserve all documents and electronically stored information (ESI) related to:
- Subject matter: {{hold_scope}}
- Date range: {{start_date}} to present
- Document types: {{document_types}}

DO NOT delete, destroy, modify, or discard any potentially relevant materials.

[Specific instructions for systems, email, chat, local files]

Please acknowledge receipt of this notice by {{acknowledgment_deadline}}.

Contact {{legal_contact}} with any questions.

3. Privacy Inquiries

Sub-categories:

Key template elements:

Sub-categories:

Key template elements:

5. NDA Requests

Sub-categories:

Key template elements:

6. Subpoena / Legal Process

Sub-categories:

Key template elements:

Critical note: Subpoena responses almost always require individualized counsel review. Templates serve as starting frameworks, not final responses.

7. Insurance Notifications

Sub-categories:

Key template elements:

Template Management Methodology

Template Organization

Templates should be organized by category and maintained in the team's local settings. Each template should include:

  1. Category: The type of inquiry the template addresses
  2. Template name: A descriptive identifier
  3. Use case: When this template is appropriate
  4. Escalation triggers: When this template should NOT be used
  5. Required variables: Information that must be customized for each use
  6. Template body: The response text with variable placeholders
  7. Follow-up actions: Standard steps after sending the response
  8. Last reviewed date: When the template was last verified for accuracy

Template Lifecycle

  1. Creation: Draft template based on best practices and team input
  2. Review: Legal team review and approval of template content
  3. Publication: Add to template library with metadata
  4. Use: Generate responses using the template
  5. Feedback: Track when templates are modified during use to identify improvement opportunities
  6. Update: Revise templates when laws, policies, or best practices change
  7. Retirement: Archive templates that are no longer applicable

Template Creation Guide

When helping users create new templates:

1. Define the Use Case

2. Identify Required Elements

3. Define Variables

4. Draft the Template

5. Define Escalation Triggers

6. Add Metadata

Template Format

## Template: {{template_name}}
**Category**: {{category}}
**Version**: {{version}} | **Last Reviewed**: {{date}}
**Approved By**: {{approver}}

### Use When
- [Condition 1]
- [Condition 2]

### Do NOT Use When (Escalation Triggers)
- [Trigger 1]
- [Trigger 2]

### Variables
| Variable | Description | Example |
|---|---|---|
| {{var1}} | [what it is] | [example value] |
| {{var2}} | [what it is] | [example value] |

### Subject Line
[Subject template with {{variables}}]

### Body
[Response body with {{variables}}]

### Follow-Up Actions
1. [Action 1]
2. [Action 2]

### Notes
[Any special instructions for users of this template]

Output Format

## Generated Response: [Inquiry Type]

**To**: [recipient]
**Subject**: [subject line]

---

[Response body]

---

### Escalation Check
[Confirmation that no escalation triggers were detected, OR flagged triggers with recommendations]

### Follow-Up Actions
1. [Post-send actions]
2. [Calendar reminders to set]
3. [Tracking or logging requirements]

Notes