generate-documentlisted

# Generate a document > **PREREQUISITE:** Use the `propper` skill for authentication, tool routing, and the > agreement status model. Merge data into a saved template and get a document out. The discipline that matters is reviewing the merged output before sending: HTML preview reports unresolved tokens without creating a generated-document record or consuming generation quota. To build the template in the first place, use `build-gen-template`. To route the result for signature, use `send-for-signature`. ## Never write the document instead If the template cannot be read — Propper is not connected, the organization has none, or the user cannot say which one — **stop and say so. Do not draft the document yourself.** This holds even when the request is urgent, even when the user has supplied enough facts to write something plausible, and even when refusing feels unhelpful. A freehand draft with `[PLACEHOLDER]` markers is the failure mode this skill exists to prevent: it looks like the deliverable, it carries none of the organization's approved wording, and the real values the user supplied end up embedded in text nobody has ever signed off. Handing that to someone who asked for "our standard letter" is worse than handing them nothing. Say which of the three is missing, and offer the real paths: connect Propper so the template can be read, or use `build-gen-template` if they have a source document to turn into one. Then stop. ## Steps ### 1. Authenticate `get_current_us