When a contract is finalized and ready to sign, /signature-request runs the pre-signature checklist and routes the envelope for execution. — Claude Skill
Run the pre-signature checklist and route any contract for e-signature.
- Pre-signature checklist: final form, exhibits, entity names, signature blocks, internal approvals
- Signing config: sequential or parallel, internal approvers, CC recipients
- Connected: DocuSign, Adobe Sign, Dropbox Sign — envelope created with fields and order
- Standalone: signing instructions for wet signature or manual e-sign
- Catches the most common error: incorrect legal entity names on signature blocks
Pour qui
Ce qu'il fait
/signature-request runs the 7-item pre-signature checklist, catches that one exhibit is still in track-changes mode, asks you to confirm signing order between your CFO and the counterparty, and creates the DocuSign envelope with fields pre-placed.
/signature-request takes your template, populates the counterparty entity name from CRM, sets parallel signing (both sides can sign in any order), and sends the envelope — finished in 5 minutes from inbox to sent.
/signature-request configures sequential routing: legal review, finance approval, business owner, GC — then counterparty signer last. CC's the original deal team and files the executed copy in iManage on completion.
/signature-request catches the entity name mismatch ("Acme Inc." vs "Acme Holdings LLC") in the pre-signature check, refuses to send, and flags the issue with the exact correction needed before routing.
Fonctionnement
Accept the document: file upload, URL to CLM, or reference to a finalized contract
Run the 7-item pre-signature checklist
Configure signers, signing order, internal approvers, and CC list
Route for signature via connected e-sig provider, or generate signing instructions if standalone
File the executed copy in CLM or document storage on completion
Exemple
TechVendor MSA — final version, 42 pages, ready for signature. Our signer: Jane Smith (CFO). Their signer: John Doe (VP Sales).
PASS — all 7 checks cleared [x] Document in final form, no open redlines [x] All 4 exhibits attached [x] Entity names correct: 'Acme Corporation' (us) and 'TechVendor, Inc.' (them) [x] Dates left blank for execution date [x] Signature blocks match authorized signers [x] Internal approval from VP Legal recorded [x] Counsel review complete
Order | Signer | Email | Role 1 | Jane Smith | [email protected] | Acme CFO 2 | John Doe | [email protected] | TechVendor VP Sales Mode: Sequential CC: [email protected], [email protected]
DocuSign envelope created: Envelope ID DS-2026-0419 Sent to Jane Smith for first signature Expected turnaround: 2 business days
1. Jane signs by 2026-04-10 (calendar reminder set) 2. John auto-receives after Jane signs 3. Executed copy auto-filed to iManage on completion 4. Follow-up reminder if not signed by 2026-04-15
Métriques améliorées
Compatible avec
Creates DocuSign envelopes with signing fields, order, and CC list
Routes finalized contracts from DocuSign CLM to signature workflow
Routes Ironclad contracts to e-signature with internal approver chain
Sends Juro documents for signature with sequential or parallel signing
Files executed copies in NetDocuments workspace on completion
Files executed copies in iManage on completion
Prêt à installer E-Signature Routing ?
Choisissez comment commencer.
Installez et exécutez ce plugin localement sur votre ordinateur.
Ouvrez un terminal sur votre ordinateur et collez cette commande :
Cela télécharge le plugin avec tous ses fichiers sur votre ordinateur :
Ajoutez -g à la fin pour le rendre disponible dans tous vos projets.
Démarrez Claude Code, puis tapez la commande :
/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 in any format: file upload (PDF, DOCX), URL to cloud storage or CLM, reference ("the Acme MSA we finalized yesterday").
Step 2: Pre-Signature Checklist
## 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
- [ ] Required internal approvals obtained
- [ ] Document reviewed by appropriate counsel
Step 3: Configure Signing
Gather details: signers (names, emails, titles), signing order (sequential or parallel), internal approval before counterparty, CC recipients.
Step 4: Route for Signature
If e-signature is connected: create envelope/request, set signing fields and order, add initials/date fields, send.
If not connected: generate signing instruction document, format for wet signature or manual e-sign, list all signers.
Output
## Signature Request: [Document Title]
### Document Details
- Type: [MSA / NDA / SOW / Amendment]
- Parties: [Party A] and [Party B]
- Pages: [X]
### Pre-Signature Check: [PASS / ISSUES FOUND]
[List any issues to resolve]
### Signing Configuration
| Order | Signer | Email | Role |
|-------|--------|-------|------|
| 1 | [Name] | [email] | [Party A Authorized Signatory] |
| 2 | [Name] | [email] | [Party B Authorized Signatory] |
### 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
Tips
- Check entity names carefully — 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