Enterprise Legal Workflows
This skill is a merged entry point. The porting method is copy → merge → modify → optimize:
- Source README / practice profile / SKILL.md / agent markdown files were copied into
references/source-workflows/.
- Hook and slash-command behavior was removed because this marketplace uses experts, agents, and skills.
- The exposed skill below consolidates the copied source workflows into a smaller routing surface.
- Local adaptation should be done cautiously through jurisdiction notes, not by replacing the source workflow wholesale.
Copied source materials
See references/source-workflows/ in this plugin for the debranded source workflow text used during consolidation.
Consolidated behavior
Source capability groups
- Commercial legal: contract review, NDA review, SaaS MSA review, renewal tracking, escalation flagging, stakeholder summaries.
- Corporate legal: M&A diligence, tabular issue extraction, material contract schedules, closing checklists, board minutes, written consents.
- Employment legal: hiring review, termination review, employment relationship review, working-time and compensation QA, internal investigations, leave and handbook tracking.
- Privacy legal: use-case triage, PIA generation, DPA review, personal information rights request response, policy monitoring, regulatory gap analysis.
- Product legal: launch review, marketing claims review, feature risk assessment, quick issue triage.
- Regulatory legal: feed watching, policy diffing, gap surfacing, policy redraft, regulatory deadline tracking.
- AI governance legal: AI inventory, use-case triage, AI impact assessment, vendor AI review, AI policy starter, AI regulatory gaps.
- IP legal: trademark clearance, FTO triage, invention intake, IP clause review, OSS review, infringement triage, cease-and-desist and takedown drafts.
Operating rule
For any non-trivial request, route to the corresponding team member instead of answering as a generic legal assistant. Outputs are lawyer-review drafts, not legal advice.
Working across jurisdictions
Use the source workflow as the operating skeleton, but read the matter through the jurisdiction the user is actually working in. If the facts point to China or another non-US setting, first anchor the analysis in the applicable law, regulator, industry, contract language, and document purpose. Keep the familiar review flow, while translating only the parts that are jurisdiction-shaped: legal labels, deadlines, regulator references, employment classifications, data-protection vocabulary, and court or filing procedures.
When the local rule is not in the provided materials or a current source you can inspect, say so naturally in the analysis and treat it as something for counsel to verify. The goal is a localized draft that still feels like the original workflow, not a new legal product rebuilt from scratch.
Legal-output boundary
Outputs are lawyer-review drafts, not legal advice. Mark assumptions, sources, and attorney-review points.
1---2name: enterprise-legal-workflows3description: Consolidated workflow layer copied and merged from commercial-legal, corporate-legal, employment-legal, privacy-legal, product-legal, regulatory-legal, ai-governance-legal, and ip-legal. Use this skill as the exposed entry point while preserving detailed source workflows under references/source-workflows.4---5
6# Enterprise Legal Workflows
7
8This skill is a merged entry point. The porting method is copy → merge → modify → optimize:
9
101. Source README / practice profile / SKILL.md / agent markdown files were copied into `references/source-workflows/`.
112. Hook and slash-command behavior was removed because this marketplace uses experts, agents, and skills.
123. The exposed skill below consolidates the copied source workflows into a smaller routing surface.
134. Local adaptation should be done cautiously through jurisdiction notes, not by replacing the source workflow wholesale.
14
15## Copied source materials
16
17See `references/source-workflows/` in this plugin for the debranded source workflow text used during consolidation.
18
19## Consolidated behavior
20
21## Source capability groups
22
231. Commercial legal: contract review, NDA review, SaaS MSA review, renewal tracking, escalation flagging, stakeholder summaries.
242. Corporate legal: M&A diligence, tabular issue extraction, material contract schedules, closing checklists, board minutes, written consents.
253. Employment legal: hiring review, termination review, employment relationship review, working-time and compensation QA, internal investigations, leave and handbook tracking.
264. Privacy legal: use-case triage, PIA generation, DPA review, personal information rights request response, policy monitoring, regulatory gap analysis.
275. Product legal: launch review, marketing claims review, feature risk assessment, quick issue triage.
286. Regulatory legal: feed watching, policy diffing, gap surfacing, policy redraft, regulatory deadline tracking.
297. AI governance legal: AI inventory, use-case triage, AI impact assessment, vendor AI review, AI policy starter, AI regulatory gaps.
308. IP legal: trademark clearance, FTO triage, invention intake, IP clause review, OSS review, infringement triage, cease-and-desist and takedown drafts.
31
32## Operating rule
33
34For any non-trivial request, route to the corresponding team member instead of answering as a generic legal assistant. Outputs are lawyer-review drafts, not legal advice.
35## Working across jurisdictions
36
37Use the source workflow as the operating skeleton, but read the matter through the jurisdiction the user is actually working in. If the facts point to China or another non-US setting, first anchor the analysis in the applicable law, regulator, industry, contract language, and document purpose. Keep the familiar review flow, while translating only the parts that are jurisdiction-shaped: legal labels, deadlines, regulator references, employment classifications, data-protection vocabulary, and court or filing procedures.
38
39When the local rule is not in the provided materials or a current source you can inspect, say so naturally in the analysis and treat it as something for counsel to verify. The goal is a localized draft that still feels like the original workflow, not a new legal product rebuilt from scratch.
40
41
42## Legal-output boundary
43
44Outputs are lawyer-review drafts, not legal advice. Mark assumptions, sources, and attorney-review points.
infometa