Prepare and route a document for e-signature — run a pre-signature checklist, configure signing order, and send for execution. Use when a contract is finalized and ready to sign, when verifying entity names, exhibits, and signature blocks before sending, or when setting up an envelope with sequential or parallel signers.
Installs into .claude/skills of the current project.
Are you the author of Signature Request?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/cslawyer1985-signature-request)
---
name: signature-request
description: Prepare and route a document for e-signature — run a pre-signature checklist, configure signing order, and send for execution. Use when a contract is finalized and ready to sign, when verifying entity names, exhibits, and signature blocks before sending, or when setting up an envelope with sequential or parallel signers.
argument-hint: "<document or contract to send>"
---
# /signature-request -- E-Signature Routing
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.
## Workflow
### Step 1: Accept the Document
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"
### Step 2: Pre-Signature Checklist
```markdown
## Pre-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
```
### Step 3: Configure Signing
- **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
**If e-signature is connected:** Create the signature envelope/request, set signing fields and order, send.
**If not connected:** Generate a signing instruction document with all signer details.
## Output
```markdown
## Signature Request: [Document Title]
### Document Details
- **Type**: [MSA / NDA / SOW / Amendment / etc.]
- **Parties**: [Party A] and [Party B]
### Pre-Signature Check: [PASS / ISSUES FOUND]
### Signing Configuration
| Order | Signer | Email | Role |
|-------|--------|-------|------|
| 1 | [Name] | [email] | [Party A Authorized Signatory] |
| 2 | [Name] | [email] | [Party B Authorized Signatory] |
### Status
[Sent for signature / Ready to send / Issues to resolve first]
```
## Tips
1. **Check entity names carefully** — The most common signing error is incorrect legal entity names.
2. **Verify authority** — Make sure each signer is authorized to bind their organization.
3. **Keep a copy** — Executed copies should be filed immediately after execution.