188 lines
5.2 KiB
Markdown
188 lines
5.2 KiB
Markdown
---
|
||
name: contract-document-generator
|
||
description: Draft contracts and formal business documents, rewrite clauses, identify risks, and organize negotiation-ready language. Use when the user asks for contract drafting, clause revision, legal-style document generation, formal agreement structuring, or document-ready policy and terms content. 中文触发词包括：合同起草、协议生成、条款修改、风险审查、保密协议、正式文档撰写。
|
||
---
|
||
|
||
# Contract & Document Generator
|
||
|
||
## Overview
|
||
|
||
This skill handles the **content layer** of contracts and formal documents:
|
||
- drafting and rewriting clauses
|
||
- structuring agreements
|
||
- highlighting risks and ambiguities
|
||
- preparing negotiation-ready revisions
|
||
|
||
It does **not** replace file-format skills. Use `docx` and `pdf` for the final document container when needed.
|
||
|
||
## Quick Start
|
||
|
||
When the user asks for a contract or formal document:
|
||
|
||
1. Identify the document type
|
||
2. Clarify the governing context and required clauses
|
||
3. Confirm whether the task is drafting, editing, summarizing, or risk review
|
||
4. Produce a structured output with clear labels for assumptions and unresolved items
|
||
5. If the user needs a file, pass the final content to `docx` or `pdf`
|
||
|
||
### 中文任务映射
|
||
- “起草一份合同” → new draft
|
||
- “改一下这段条款” → clause revision
|
||
- “审一下风险” → risk review
|
||
- “整理成正式文件” → draft + docx/pdf handoff
|
||
|
||
|
||
## Input Requirements
|
||
|
||
| Field | Required | Description |
|
||
|-------|----------|-------------|
|
||
| document type | yes | NDA, service agreement, employment clause, terms, policy, notice, memo |
|
||
| objective | yes | Drafting, revision, review, comparison, simplification |
|
||
| parties / stakeholders | no | The involved entities or roles |
|
||
| jurisdiction / governing law | no | Legal or regional context |
|
||
| must-have clauses | no | Required provisions |
|
||
| prohibited or risky clauses | no | Clauses to avoid or watch |
|
||
| tone / style | no | Formal, plain language, business-friendly, negotiation-ready |
|
||
| output format | no | Clause list, full draft, risk memo, redline guidance |
|
||
|
||
## Workflow Decision Tree
|
||
|
||
### New Draft
|
||
Use when the user wants a first version of a contract or formal document.
|
||
|
||
### Clause Revision
|
||
Use when the user wants to rewrite specific language, tighten wording, or simplify terms.
|
||
|
||
### Risk Review
|
||
Use when the user wants to understand what is risky, ambiguous, one-sided, or incomplete.
|
||
|
||
### Comparison / Negotiation Support
|
||
Use when the user wants a position memo, fallback language, or issue-by-issue negotiation guidance.
|
||
|
||
## Instructions
|
||
|
||
### Step 1: Define document role
|
||
Clarify what the document is supposed to do:
|
||
- bind parties
|
||
- allocate risk
|
||
- state responsibilities
|
||
- define process
|
||
- provide internal or external communication
|
||
|
||
### Step 2: Identify the minimum structure
|
||
Typical sections may include:
|
||
- parties and definitions
|
||
- scope
|
||
- payment or consideration
|
||
- obligations
|
||
- confidentiality
|
||
- IP ownership
|
||
- term and termination
|
||
- liability and indemnity
|
||
- dispute resolution
|
||
- notices
|
||
|
||
Only include sections relevant to the user’s objective.
|
||
|
||
### Step 3: Mark assumptions explicitly
|
||
If party names, law, numbers, dates, or scope are missing, mark them as placeholders instead of inventing them.
|
||
|
||
### Step 4: Review for risk and ambiguity
|
||
Check for:
|
||
- undefined terms
|
||
- missing triggers or deadlines
|
||
- one-sided liability allocation
|
||
- vague performance obligations
|
||
- inconsistent terms across sections
|
||
|
||
### Step 5: Package the output for the user’s goal
|
||
Depending on the request, return one of:
|
||
- full draft
|
||
- clause alternatives
|
||
- risk memo
|
||
- revision guidance
|
||
- negotiation checklist
|
||
|
||
## Output Format
|
||
|
||
### Full Draft Mode
|
||
```markdown
|
||
# [Document Title]
|
||
|
||
## Draft Notes
|
||
- Purpose:
|
||
- Assumptions:
|
||
- Jurisdiction status:
|
||
|
||
## Draft
|
||
[Full structured document]
|
||
|
||
## Open Items
|
||
- [Missing information]
|
||
```
|
||
|
||
### Risk Review Mode
|
||
```markdown
|
||
# Contract Risk Review
|
||
|
||
## Summary
|
||
[Short overall view]
|
||
|
||
## Key Risks
|
||
### 1. [Risk]
|
||
- Clause / section:
|
||
- Why it matters:
|
||
- Suggested revision:
|
||
|
||
## Missing Terms
|
||
- [Item]
|
||
|
||
## Negotiation Suggestions
|
||
- [Suggestion]
|
||
```
|
||
|
||
## Quality Checklist
|
||
|
||
Before finalizing, verify:
|
||
- placeholders are clearly marked
|
||
- legal assumptions are not presented as confirmed facts
|
||
- obligations, timing, and consequences are clear
|
||
- defined terms are used consistently
|
||
- risk comments are concrete and actionable
|
||
- document structure matches the user’s purpose
|
||
|
||
## Fallback Strategy
|
||
|
||
If legal context is unclear:
|
||
- provide a business draft
|
||
- mark jurisdiction-specific items as requiring legal review
|
||
- avoid pretending to give definitive legal advice
|
||
|
||
## Related Skills
|
||
|
||
- `skills/docx/SKILL.md` - generate a formal `.docx` document or tracked-change revision
|
||
- `skills/pdf/SKILL.md` - extract, archive, or distribute final documents in PDF
|
||
|
||
## Examples
|
||
|
||
**User**: "帮我起草一份软件服务合同"
|
||
|
||
Expected output:
|
||
- structured draft
|
||
- placeholders for missing commercial terms
|
||
- open items section
|
||
|
||
**User**: "把这段保密条款改得更平衡一些"
|
||
|
||
Expected output:
|
||
- revised clause
|
||
- explanation of changes
|
||
- negotiation rationale if useful
|
||
|
||
**User**: "审一下这份合同有哪些风险"
|
||
|
||
Expected output:
|
||
- risk summary
|
||
- clause-by-clause risks
|
||
- suggested revisions
|