signature-request
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese/signature-request -- E-Signature Routing
/signature-request -- 电子签名路由
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Prepare a document for electronic signature — verify completeness, set signing order, and route for execution.
Important: This command assists with legal workflows but does not provide legal advice. Verify documents are in final form before sending for signature.
若遇到不熟悉的占位符或需要检查已连接的工具，请查看 CONNECTORS.md。
为电子签名准备文档——验证完整性、设置签名顺序并路由至签署流程。
重要提示：本命令协助处理法律工作流，但不提供法律建议。请在发送签署前确认文档为最终版本。
Usage
使用方法
/signature-request $ARGUMENTSPrepare for signature: @$1
/signature-request $ARGUMENTS准备签署：@$1
Workflow
工作流
Step 1: Accept the Document
步骤1：接收文档
Accept the document in any format:
- File upload: PDF, DOCX
- URL: Link to a document in ~~cloud storage or ~~CLM
- Reference: "The Acme Corp MSA we finalized yesterday"
接收任意格式的文档：
- 文件上传：PDF、DOCX
- URL：指向
云存储或CLM中文档的链接 - 引用：“我们昨日定稿的Acme Corp主服务协议”
Step 2: Pre-Signature Checklist
步骤2：签名前检查清单
Before routing for signature, verify:
markdown
undefined在路由至签署前，请验证：
markdown
undefinedPre-Signature Checklist
签名前检查清单
- Document is in final, agreed form (no open redlines)
- All exhibits and schedules are attached
- Correct legal entity names on signature blocks
- Dates are correct or left blank for execution date
- Signature blocks match the authorized signers
- Any required internal approvals have been obtained
- Document has been reviewed by appropriate counsel
undefined- 文档为最终商定版本（无未解决的修订标记）
- 所有附件和附录均已附上
- 签名栏上的法律实体名称正确
- 日期正确或留空以待签署日期
- 签名栏与授权签署人匹配
- 已获取所有必要的内部审批
- 文档已由相关法律顾问审核
undefinedStep 3: Configure Signing
步骤3：配置签署信息
Gather signing details:
- Signers: Who needs to sign? (names, emails, titles)
- Signing order: Sequential or parallel?
- Internal approval: Does anyone need to approve before the counterparty signs?
- CC recipients: Who should receive a copy of the executed document?
收集签署详情：
- 签署人：谁需要签署？（姓名、邮箱、职位）
- 签名顺序：顺序签署还是并行签署？
- 内部审批：在对方签署前是否需要有人审批？
- 抄送收件人：谁应收到已签署文档的副本？
Step 4: Route for Signature
步骤4：路由至签署流程
If ~~e-signature is connected:
- Create the signature envelope/request
- Set signing fields and order
- Add any required initials or date fields
- Send for signature
If not connected:
- Generate a signing instruction document
- Provide the document formatted for wet signature or manual e-sign
- List all signers with contact information
若已连接电子签名工具：
- 创建签名信封/请求
- 设置签名字段和顺序
- 添加任何必要的首字母或日期字段
- 发送签署请求
若未连接：
- 生成签署说明文档
- 提供适合湿签名或手动电子签名的文档格式
- 列出所有签署人的联系信息
Output
输出
markdown
undefinedmarkdown
undefinedSignature Request: [Document Title]
签名请求：[文档标题]
Document Details
文档详情
- Type: [MSA / NDA / SOW / Amendment / etc.]
- Parties: [Party A] and [Party B]
- Pages: [X]
- 类型：[主服务协议/保密协议/工作说明书/修正案/等]
- 双方：[甲方] 和 [乙方]
- 页数：[X]
Pre-Signature Check: [PASS / ISSUES FOUND]
签名前检查：[通过/发现问题]
[List any issues that need attention before sending]
[列出发送前需要注意的所有问题]
Signing Configuration
签署配置
| Order | Signer | Role | |
|---|---|---|---|
| 1 | [Name] | [email] | [Party A Authorized Signatory] |
| 2 | [Name] | [email] | [Party B Authorized Signatory] |
| 顺序 | 签署人 | 邮箱 | 角色 |
|---|---|---|---|
| 1 | [姓名] | [邮箱] | [甲方授权签署人] |
| 2 | [姓名] | [邮箱] | [乙方授权签署人] |
CC Recipients
抄送收件人
- [Name] — [email]
- [姓名] — [邮箱]
Status
状态
[Sent for signature / Ready to send / Issues to resolve first]
[已发送签署请求/待发送/需先解决问题]
Next Steps
后续步骤
- [What to expect after sending]
- [Expected turnaround time]
- [Follow-up if not signed within X days]
undefined- [发送后的预期事项]
- [预计处理时间]
- [若X天内未签署的跟进措施]
undefinedTips
提示
- Check entity names carefully — The most common signing error is incorrect legal entity names.
- Verify authority — Make sure each signer is authorized to bind their organization.
- Keep a copy — Executed copies should be filed in ~~cloud storage or ~~CLM immediately after execution.
- 仔细检查实体名称——最常见的签署错误是法律实体名称不正确。
- 验证授权——确保每位签署人有权代表其组织签署。
- 留存副本——签署完成后，应立即将已签署副本归档至
云存储或CLM中。