# Render-DOCX Handoff Checklist

The render passes only when all 9 items are true:

- Input was a real `.md` or `.markdown` file.
- If input was `docs/business/<project-slug>/proposal.md`, it passed the business-proposal template-shape validation before rendering.
- Output path is beside the input and uses the same basename with `.docx`.
- Existing `.docx` files were not overwritten.
- `templates/reference.docx` was used as the Pandoc reference document.
- Relative images, if present, resolve from the Markdown file's directory.
- The DOCX opens in Word-compatible software and is not empty.
- Headings, tables, quotes, links, and code blocks visibly use the template styles.
- The footer shows only the page counter (for example, `Página    1`) and no brand/confidentiality text.

## On failure

- Missing Pandoc → the script auto-installs a standalone pandoc binary silently; only report a failure if that automatic install itself fails (for example, no network access).
- Existing output → ask the user to move, rename, or delete the `.docx`.
- Missing template → report the skill installation is incomplete.
- Broken relative image → ask the user to fix the image path relative to the Markdown file.