From legal
Generates contextual legal briefings for teams: daily summaries of urgent items and deadlines, topic research, or incident responses from connected email, calendar, chat, CLM, and CRM sources.
npx claudepluginhub sksdesignnew/claudepg --plugin legal[daily | topic <query> | incident]# /brief -- Legal Team Briefing > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md). Generate contextual briefings for legal work. Supports three modes: daily brief, topic brief, and incident brief. **Important**: This command assists with legal workflows but does not provide legal advice. Briefings should be reviewed by qualified legal professionals before being relied upon. ## Invocation If no mode is specified, ask the user which type of brief they need. ## Modes --- ### Daily Brief A morning summary of everyth...
/briefInteractively generates creative brief for marketing campaigns: collects scope, type, deliverables, timeline via questions, confirms, then outputs brief using loaded brand and plan context.
/briefGenerates a concise visual briefing on project state, progress, key decisions, blockers, and next steps from git status, specs, tasks, and context.
/briefGenerates contextual legal briefings for teams: daily summaries of urgent items and deadlines, topic research, or incident responses from connected email, calendar, chat, CLM, and CRM sources.
/briefInteractive product brief generator — conducts a dialog, then writes docs/product-brief.md
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate contextual briefings for legal work. Supports three modes: daily brief, topic brief, and incident brief.
Important: This command assists with legal workflows but does not provide legal advice. Briefings should be reviewed by qualified legal professionals before being relied upon.
/brief daily # Morning brief of legal-relevant items
/brief topic [query] # Research brief on a specific legal question
/brief incident [topic] # Rapid brief on a developing situation
If no mode is specified, ask the user which type of brief they need.
A morning summary of everything a legal team member needs to know to start their day.
Check each connected source for legal-relevant items:
Email (if connected):
Calendar (if connected):
Chat (if connected):
CLM (if connected):
CRM (if connected):
## Daily Legal Brief -- [Date]
### Urgent / Action Required
[Items needing immediate attention, sorted by urgency]
### Contract Pipeline
- **Awaiting Your Review**: [count and list]
- **Pending Counterparty Response**: [count and list]
- **Approaching Deadlines**: [items due this week]
### New Requests
[Contract review requests, NDA requests, compliance questions received since last brief]
### Calendar Today
[Meetings with legal relevance and what prep is needed]
### Team Activity
[Key messages or updates from legal team channels]
### This Week's Deadlines
[Upcoming deadlines and filing dates]
### Sources Not Available
[Any sources that were not connected or returned errors]
Research and brief on a specific legal question or topic across available sources.
## Topic Brief: [Topic]
### Summary
[2-3 sentence executive summary of findings]
### Background
[Context and history from internal sources]
### Current State
[What the organization's current position or approach is, based on available documents]
### Key Considerations
[Important factors, risks, or open questions]
### Internal Precedent
[Prior decisions, memos, or positions found in internal sources]
### Gaps
[What information is missing or what sources were not available]
### Recommended Next Steps
[What the user should do with this information]
Rapid briefing for developing situations that require immediate legal attention (data breaches, litigation threats, regulatory inquiries, IP disputes, etc.).
## Incident Brief: [Topic]
**Prepared**: [timestamp]
**Classification**: [severity assessment if determinable]
### Situation Summary
[What is known about the incident]
### Timeline
[Chronological summary of events based on available sources]
### Immediate Legal Considerations
[Regulatory notification requirements, preservation obligations, privilege concerns]
### Relevant Agreements
[Contracts, insurance policies, or other agreements that may be implicated]
### Internal Response
[What response activity has already occurred based on email/chat]
### Key Contacts
[Relevant internal and external contacts identified from sources]
### Recommended Immediate Actions
1. [Most urgent action]
2. [Second priority]
3. [etc.]
### Information Gaps
[What is not yet known and needs to be determined]
### Sources Checked
[What was searched and what was not available]