Add word document generator from template

[Nazish (nazishqassim)]

Title: Add word-document-generator-from-template skill

## Summary

- Adds an instruction-only Copilot Studio skill that fills a Word template supplied at runtime (upload, SharePoint, OneDrive, or another connector) and writes a **new** DOCX without overwriting the original.
- Works for any document the template defines — policy, procedure, report, paper, briefing, SOP, or SOW — using user input, approved knowledge, uploaded files, and prior tool/connector results (e.g. Dataverse).
- Agent inspects the template, builds JSON that matches its headings/placeholders/repeating tables, generates section by section, and marks unsupported facts as `Not specified in approved sources`.
- README includes a generic template skeleton (styles, `{{placeholders}}`, one sample repeating row) plus example prompts; Leave Policy is only an illustration of the same pattern.

Word Document Generator from Template is a Copilot Studio skill that drafts any Word document—policy, procedure, report, paper, or similar—by filling a runtime template from an upload, SharePoint, OneDrive, or another connector. It uses only user input, approved knowledge, attached files, and prior tool/connector results, maps those into JSON that matches the template’s headings and repeating tables, preserves branding and layout, never overwrites the original file, and returns a new DOCX plus a short generation summary with gaps marked for human review.

[Copilot]

Pull request overview

Adds a new submission to the submissions/ gallery: an instruction-only Copilot Studio skill for generating a new DOCX by filling a runtime-provided Word template (upload/SharePoint/OneDrive/connector), grounded in approved sources and prior tool/connector results.

Changes:

• Added word-document-generator-from-template skill instructions for template inspection, JSON mapping, population, and validation while preventing template overwrite.
• Added a human-facing README.md describing intended usage, inputs, and a generic Word template skeleton with examples.
• Added metadata.json registering the skill for Copilot Studio with tags, author info, and versioning.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
submissions/word-document-generator-from-template/SKILL.md	Defines the agent-run procedure and guardrails for filling a runtime Word template and saving a new DOCX.
submissions/word-document-generator-from-template/README.md	Provides human-facing adoption guidance, template structure recommendations, and example prompts.
submissions/word-document-generator-from-template/metadata.json	Registers the submission (name/description/platform/tags/author/version/dates).

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (3)

submissions/word-document-generator-from-template/SKILL.md:86

• source_ids is described as holding tool/connector names like Dataverse:accounts, but the JSON example and sources section use stable IDs like SRC-001. This inconsistency will cause the intermediate JSON to be structured differently depending on which part the agent follows.

- Treat prior tool and connector outputs as approved sources. Record the tool or connector name in `source_ids` (for example `Dataverse:accounts`, `SharePoint:policy-library`).

submissions/word-document-generator-from-template/README.md:43

• The README prescribes {{placeholders}}, but Copilot Studio’s Word/Graph connector approaches typically require a specific templating mechanism (e.g., content controls), and the skill does not mandate any particular engine. As written, users could build templates that the runtime tooling can’t actually fill.

The same pattern works for every document type. Use **Word styles** (Heading 1,
Heading 2, Normal) and `{{placeholders}}` — not finished body text.

submissions/word-document-generator-from-template/SKILL.md:45

• The skill assumes it can inspect a .docx template and then populate it while preserving formatting, but it doesn’t first require/verify that an actual Copilot Studio action/tool exists that can (a) read the template and (b) write a new .docx for the template’s placeholder/repeating-row syntax. Without that preflight, the procedure can’t be executed reliably.

1. Locate the Word template supplied at runtime. Obtain it from whichever source the user identified:
   - a file uploaded with the request;
   - SharePoint (library, folder, or site);
   - OneDrive; or
   - another connector or prior tool result that returns a `.docx` file.

[Copilot]

Pull request overview

Copilot reviewed 9 out of 10 changed files in this pull request and generated no new comments.

Suppressed comments (1)

submissions/word-document-generator-from-template/scripts/docx_template.py:147

• zipfile.ZipFile.read() can raise RuntimeError for encrypted/password-protected DOCX files (and zipfile.LargeZipFile for large ZIP64 archives). Currently _read_package() only wraps BadZipFile/OSError, so those cases would surface as an unhandled exception instead of a TemplateError with exit code 2.

    except (zipfile.BadZipFile, OSError) as exc:
        raise TemplateError(f"Cannot read DOCX package {source}: {exc}") from exc