send-for-signaturelisted

# Send for signature > **PREREQUISITE:** Use the `propper` skill for authentication, tool routing, and the > agreement status model. Use `agreement-workflows` for recipient roles and the > confirmation wording. Take a document from wherever it is to signatures requested, in one pass, with one confirmation before anything is emailed. ## Steps ### 1. Authenticate `get_current_user`. Report the organization. Stop on failure per the `propper` skill. ### 2. Locate the source | The user has | Do | |---|---| | A file path | Read it. Confirm it is PDF or DOCX; those are the two accepted types | | A named template | `list_templates` with `search`, then `get_template` to read its roles | | Content to generate | `generate-document` produces it from a template, then return here | | Nothing concrete | Ask which document. Do not invent one | If the document is unsigned-off or looks like a draft, run `signature-ready-check` first and report what it finds before going further. ### 3. Resolve signers Collect a full name and email for every signer. Ask for anything missing; never infer an address from a domain or a name. Decide `PARALLEL` or `SEQUENTIAL` per `agreement-workflows`. State the choice. ### 4. Create the draft Document-based, when the file is on disk: ``` create_agreement { name, type } manage_documents { action: "add", agreementId, document: <base64>, filename, mimeType } manage_recipients { action: "add", agreementId, name, email, role, order } // per signer ```