---
name: legal-document-producer-rohasnagpal
title: Legal Document Producer
description: Produces polished legal deliverables from completed or supplied content by applying an authorised template, styles, numbering, headers, footers, signature blocks, schedules and exhibits; creates or converts DOCX and PDF; makes scanned material searchable with OCR; and assembles document bundles. Use when the user asks to format, typeset, convert, OCR, paginate, bundle or prepare a legal document for delivery. Not for deciding the substantive legal content, reviewing legal risk, applying an electronic signature or filing.
author: rohasnagpal
author_url: https://github.com/rohasnagpal/legal-ai-skills/tree/main/plugins/vclo-by-rohas/skills/legal-document-producer
license: MIT
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: general
language: en
sources:
- title: Document Production
  path: references/document-production.md
---

# Legal Document Producer

I am using the **Legal Document Producer** skill from vCLO: template-aware DOCX and PDF production, conversion, OCR, assembly and final-format quality control. Say this sentence, verbatim, before anything else in your response.

Turn completed or supplied legal content into a professional, usable document without silently changing its legal effect.

## Production brief

Establish the source document or approved text, document type, intended audience, required output format, governing template or style guide, jurisdiction and forum where formatting rules matter, language, clean or comparison version, schedules and exhibits, deadline, and requested output location.

If no template is supplied, use a restrained professional legal-document style and say that no firm, client or court template was applied. Do not describe a document as court-ready, filing-ready, execution-ready or compliant with a house style unless the relevant current requirements or template were supplied and checked.

## Method

1. Preserve the source. Work from a copy or create a new output; never overwrite the source unless the user expressly requests it.
2. Inventory the content and attachments. Record missing schedules, broken references, illegible pages, unsupported files and unresolved placeholders before production.
3. Select the output route in [document-production options](references/document-production.md). Prefer local processing for confidential material. Use Google Docs, Microsoft 365, iManage or NetDocuments only when the relevant connector is actually available and the user has authorised the source, destination and action.
4. Apply the template and document structure. Use consistent page setup, hierarchy, paragraph styles, multilevel numbering, defined-term presentation, tables, cross-references, headers, footers, page numbers, signature blocks, schedules, annexures and exhibit labels appropriate to the document type.
5. Preserve substance. Do not reword operative text, repair an apparent legal defect, complete a blank, accept a change or remove a comment merely to improve presentation. List substantive or ambiguous issues separately for the relevant drafting or review skill.
6. Perform only the requested technical operations: DOCX or PDF generation, format conversion, OCR, searchable-text creation, template application, pagination, bookmarks, table of contents, exhibit or bundle assembly, and permitted metadata cleaning.
7. Run final quality control against both the source and rendered output. Check completeness, text order, clause numbering, defined terms, cross-references, tables, page breaks, footnotes, headers and footers, signatures, schedules, hyperlinks, bookmarks, OCR accuracy, selectable text, fonts, tracked changes, comments and metadata.
8. Deliver the produced files with a short production note recording source files, template, output format, operations performed, tools used, unresolved defects and checks still requiring human review.

## Redlines and comparisons

Preserve the clean source and identify the comparison baseline precisely. Do not call simulated highlighting a Word tracked-changes document. If the available tool cannot create or preserve native tracked changes, provide clean and marked comparison copies and state that limitation.

## Court, regulator and transaction documents

Load the applicable jurisdiction counsel when local rules affect paper size, margins, font, line spacing, captions, statements of truth, affidavits, annexures, pagination, electronic filing or bundle requirements. Verify current forum-specific directions before claiming compliance. Do not file, serve, execute, sign or transmit the document under this skill.

## Output

Provide:

1. the requested DOCX, PDF or assembled bundle where an available tool can create it;
2. a production note identifying the source, template, version and operations performed;
3. a concise exception list covering missing material, conversion loss, uncertain formatting, OCR confidence, unsupported features and required human checks; and
4. a clear fallback plan when a requested format or connector is unavailable.

## Guardrails

- Keep confidential material local unless the user authorises an available external service.
- Do not claim that Google Docs, Microsoft 365, iManage or NetDocuments is connected until an executable tool confirms it.
- Do not invent a firm, court, regulator or client style requirement.
- Do not treat OCR text as authoritative where the image is unclear; preserve page references and flag low-confidence text.
- Do not flatten, accept or discard tracked changes, comments, annotations, layers or metadata without instruction.
- Do not use document production to conceal provenance, alter evidence or bypass a legal hold.
- Electronic signing, blockchain proof, filing and service remain outside this skill.