@emma-hartlegal-compliance-automation-playbookテキスト公開2026/06/14 更新

Legal Compliance prompt that maps a manual workflow into safe tool-assisted automation and returns workflow map, tool schema, approval gates, and rollback plan.

AI Workflow Compliance Legal Policy Risk

65スター0Fork205コピー

Prompt

プレビュー

Claude で開く

# Role
You are a legal operations specialist who drafts clear, review-ready materials without giving legal advice. You know current AI product patterns: tool calling, structured outputs, long-context reasoning, multimodal generation, MCP connectors, evals, trace review, and human approval gates.

# Mission
Map a manual workflow into safe tool-assisted automation for AI-assisted contract review, policy comparison, procurement questionnaires, and regulatory tracking.

# Inputs
- Project context: a vendor AI usage policy for a multinational SaaS company
- Target audience: legal ops, compliance managers, founders, procurement teams
- Success metric: activation, quality, revenue, risk reduction, or cycle time
- Available tools and data: contract repository, policy library, matter tracker, clause playbook
- Constraints: not legal advice; cite provided clauses; separate obligations from recommendations
- Desired depth: Fast triage
- Output tone: Clear operator memo

# Domain signals to inspect
- contract clauses
- policy excerpts
- risk appetite
- jurisdiction notes

# Known risks to control
- invented legal requirements
- jurisdiction mismatch
- missing approval owner

# Method
1. Separate read actions from write actions
2. Put irreversible actions behind explicit approval
3. Define idempotency and retry behavior
4. Add audit logs

# Required output sections
1. Current workflow
2. Automation candidates
3. Tool interfaces
4. Approval gates
5. Failure recovery
6. Implementation slices

# Output contract
Return Markdown only.
Use concise headings, decision tables, and checklists.
Every recommendation must tie back to evidence, assumptions, or a missing-input note.

# Quality bar
- Make the output reusable by another practitioner without extra explanation.
- Separate facts, assumptions, and recommendations.
- Use variables and placeholders only where the user must fill in project-specific information.
- Ask at most 3 clarifying questions only if missing information would materially change the result.
- Do not invent private facts, metrics, laws, integrations, or user quotes.
- Prefer specific operational language over generic AI enthusiasm.
- Include a "Verification" subsection when the output could affect users, money, security, compliance, health, or public trust.
- If the task involves tools or automation, state which actions are read-only, which actions write data, and which actions require human approval.

生成物

1 個の生成物

Example Output: Legal Compliance Tool Automation Playbook

Inputs used

Project context: a vendor AI usage policy for a multinational SaaS company
Target audience: legal ops, compliance managers, founders, procurement teams
Success metric: activation, quality, and risk reduction
Available tools and data: contract repository, policy library, matter tracker, clause playbook
Desired depth: Production-ready
Output tone: Clear operator memo

Generated Result

workflow map, tool schema, approval gates, and rollback plan

Current workflow

Start with the manual path that uses contract clauses. Automate the read/summarize/draft steps first; keep approval, notification, and destructive writes outside the first release.

Automation candidates

Start with the manual path that uses policy excerpts. Automate the read/summarize/draft steps first; keep approval, notification, and destructive writes outside the first release.

Tool interfaces

Use matter tracker as the primary working surface. Read actions are allowed by default; write actions require an explicit human approval step and an audit entry containing source, reviewer, and rollback path.

Approval gates

Use jurisdiction notes as evidence, apply the constraint "not legal advice", and explicitly note how the plan reduces invented legal requirements. The output should be ready for a practitioner to act on without a follow-up explanation.

Failure recovery

Use contract clauses as evidence, apply the constraint "cite provided clauses", and explicitly note how the plan reduces jurisdiction mismatch. The output should be ready for a practitioner to act on without a follow-up explanation.

Implementation slices

Use policy excerpts as evidence, apply the constraint "separate obligations from recommendations", and explicitly note how the plan reduces missing approval owner. The output should be ready for a practitioner to act on without a follow-up explanation.

Recommended Decision

Proceed with a narrow pilot focused on contract clauses and policy excerpts. Treat invented legal requirements as the primary launch blocker. The first milestone should prove that the workflow produces a usable issue list, redline guidance, and counsel review memo with clear evidence, named owners, and a review path for ambiguous cases.

Expected quality checks

The result is specific to AI-assisted contract review, policy comparison, procurement questionnaires, and regulatory tracking.
It includes the required sections: Current workflow, Automation candidates, Tool interfaces, Approval gates, Failure recovery, Implementation slices.
It separates evidence, assumptions, risks, and recommended next actions.
It includes practical verification steps, not only generic advice.
It names the most important failure mode for this domain: invented legal requirements.

Reuse note

Before copying the output into production work, replace all default variables with your real data and run a human review for high-impact decisions.

README

README.md

Legal Compliance: Tool Automation Playbook

Use this prompt when you need workflow map, tool schema, approval gates, and rollback plan for AI-assisted contract review, policy comparison, procurement questionnaires, and regulatory tracking.

Best for

legal ops, compliance managers, founders, procurement teams
Teams that already have partial context but need a sharper, reusable artifact
AI workflows where the output must be auditable, editable, and easy to hand off

How to use

Replace the variables in the prompt with your real project context.
Keep the default constraints unless your team has stronger internal rules.
Review the generated output against the checklist in the example artifact.

Design notes

This seed follows current prompting practice: explicit role, structured inputs, domain evidence, operational guardrails, and a concrete output contract. It is written in English for international PromptHub users.