Przejdź do treści
Biblioteka skilli
Dokumenty i biuro · Planowanie

document-generation

/document-generation

Planuje zmiany w szablonach Word do generowania dokumentów w Dataverse: mapuje pola, kontrolki treści i symbole zastępcze.

Licencja
Apache-2.0
Ostatnia zmiana repozytorium
13.07.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 13.07.2026, bez odwołań do wycofanych modeli i API.

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Planuje zmiany w szablonach Word do generowania dokumentów w Dataverse: mapuje pola, kontrolki treści i symbole zastępcze.

Wyzwalacze z opisu

why is this field blank in the generated docadd a placeholder to the templatewhat tags does this template use
Oryginalny opis (EN)

Use for Dataverse document generation built on Word Templates - inventory the content controls in a `.docx`/`.dotx` template, map placeholders to data, and plan a template-aware change before editing blindly. Fires whenever the user mentions a Word Template, document generation, content controls, placeholder or merge-field mapping, document-definition records, "why is this field blank in the generated doc", "add a placeholder to the template", "what tags does this template use", or a document-generation plug-in, even if no helper is named. Treats `Word Templates/` as first-class source, surfac

Jak działa

  1. When to use this
  2. Helpers
  3. Domain workflow
  4. Safety and decision rules
  5. References
Sekcje z nagłówków SKILL.md, w oryginale · 48 linii, 670 słów
Podgląd SKILL.md
---
name: document-generation
description: >
  Use for Dataverse document generation built on Word Templates - inventory the content controls
  in a `.docx`/`.dotx` template, map placeholders to data, and plan a template-aware change
  before editing blindly. Fires whenever the user mentions a Word Template, document generation,
  content controls, placeholder or merge-field mapping, document-definition records, "why is this
  field blank in the generated doc", "add a placeholder to the template", "what tags does this
  template use", or a document-generation plug-in, even if no helper is named. Treats `Word
  Templates/` as first-class source, surfaces duplicate tags, missing required placeholders, and
  unused controls, and points at the `*.Business`, `*.Plugins`, and `*.Data` touchpoints a
  placeholder change implies. Run the live-mutation preflight from the `powerplatform-core`
  orchestrator before any live template or component write.
---

# Document Generation — Word Templates and Placeholder Mapping

This skill handles Power Platform document generation that uses Word Templates and content controls. It inventories the content controls inside `.docx`/`.dotx` templates, maps requested placeholders against what the template actually exposes, and plans template-aware changes — flagging duplicate tags, missing required placeholders, and unused controls before anyone edits a template blindly. It treats `Word Templates/` as a first-class source area and connects a placeholder change to the `*.Business`, `*.Plugins`, and document-definition data it depends on. It is intentionally generic about environment, publisher prefix, solution name, and folder layout — discover those per task.

## When to use this

- The user wants to know which content controls, tags, or aliases a template contains.
- A placeholder or merge field needs to be added, renamed, or remapped, and you need to know what it touches.
- A generated document has a blank or wrong field and you need to map the placeholder back to its data source.
- The user wants required-versus-optional placeholders validated against a template before a change.
- You are scoping a document-generation change across `Word Templates`, `Business`, `Plugins`, and `Data` source areas.

Route here from the `powerplatform-core` orchestrator. For solution packaging or promotion of templates and related components, use the `solution-alm-delivery` sibling skill.

## Helpers

The helpers live in the plugin's `scripts/` directory at the plugin root, not in this skill folder. Resolve the plugin root and invoke them like:

- `python "$CLAUDE_PLUGIN_ROOT/scripts/inspect_word_templates.py" --path <template-or-dir>` (Claude Code)
- `python "$CODEX_PLUGIN_ROOT/scripts/inspect_word_templates.py" --path <template-or-dir>` (also exposed as `$PLUGIN_ROOT`)
- Installed standalone / unsure: the `scripts/` folder sits beside this skill bundle — invoke by its path within the install.

| Helper | Purpose |
| --- | --- |
| `inspect_word_templates.py` | Inspect `.docx`/`.dotx` files and summarize their content controls. Defaults to the inferred `Word Templates` area; pass `--path` for a specific file or directory, `--recurse` for a directory tree, and `--summary-only` for per-file summaries without full control detail. Read-only inventory. |
| `plan_document_generation.py` | Plan a template-aware document-generation change from a `--spec` (template path or name, placeholder mappings, required-versus-optional placeholders, and entity/document-definition context). Returns current content controls, duplicate tags and aliases, mapped placeholders, missing required placeholders, unused controls, and the `Word Templates`/`Business`/`Plugins`/`Data` source-area touchpoints. Planning only. |

## Domain workflow

1. **Inventory the template first.** Run `inspect_word_templates.py` against the real template so you work from the actual content controls, tags, and aliases rather than assumptions.
2. **Plan before editing.** Run `plan_document_generation.py` with the requested placeholder mappings to see mapped placeholders, missing required placeholders, duplicate tags, and unused controls — plus the source-area touchpoints the change implies.
3. **Trace meaning changes to their source.** When a placeholder changes meaning, inspect the related `*.Business`, `*.Plugins`, and document-definition data before editing the template, rather than changing the tag in isolation.
4. **Keep templates source-controlled.** Treat `Word Templates/` as the deployable source; do not treat `Reference/` copies of templates as deployable source by default.
5. **Hand off structural redesign with judgment.** Inspection and planning are helper-backed; creating or redesigning `.docx` structure still needs repo-specific judgment and should stay review-driven until a stronger repeated pattern emerges.

## Safety and decision rules

- **`Word Templates/` is first-class source; `Reference/` is not.** Plan and edit against the deployable template, not a reference copy.
- **Do not retag blindly.** A placeholder is a contract with the generation logic — confirm the `*.Business`/`*.Plugins`/document-definition side before renaming or remapping a tag.
- **Surface duplicates and gaps explicitly.** Report duplicate tags/aliases, missing required placeholders, and unused controls instead of silently editing around them.
- **Keep structural redesign review-driven.** Lean on the helpers for inspection and mapping; treat new `.docx` structure as repo-specific work that needs explicit review.
- **Preflight gate.** Run the mandatory live-mutation preflight from the `powerplatform-core` orchestrator before any live template or related component write. Do not restate the full preflight here — invoke it there.

## References

- `references/document-generation.md` — primary helpers, operating rules, template planning inputs, what the planning helper returns, and the current helper-versus-judgment boundary.

Wersje

RepozytoriumWynikLicencja
Ta strona · satriotsubasa/powerplatform-core90Apache-2.0
automateyournetwork/netclaw100Apache-2.0

Migawka bazy z 13.11.2026 · wersja paczki 0c82efe38b62 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100docx-template-fill
    Wypełnia szablony Word (.docx) z symbolami zastępczymi typu {{PLACEHOLDER}}, obsługuje symbole rozbite na kilka fragmentów XML i sekcje warunkowe, zachowując formatowanie.
  • 100word-placeholder-replacement
    Zastępuje znaczniki {{PLACEHOLDER}} w szablonach Word (.docx) i obsługuje sekcje warunkowe typu {{IF_CONDITION}}...{{END_IF_CONDITION}}.
  • 100docx
    Tworzy, czyta i edytuje dokumenty Word (.docx) i szablony (.dotx), wyciąga treść, wstawia obrazy, zmienia tekst i obsługuje zmiany śledzone.
  • 100docx
    Tworzy, czyta, edytuje i przetwarza dokumenty Word (.docx) oraz szablony .dotx, w tym wyodrębnianie treści, wstawianie obrazów, wyszukiwanie i zamianę, zmiany śledzone i komentarze.
  • 100word-documents
    Tworzy, czyta i edytuje dokumenty Word (.docx): generowanie ze stylami i strukturą, wyciąganie treści, znajdź i zamień, śledzone zmiany oraz szablony.
  • 100microsoft-word
    Tworzy i edytuje dokumenty Word (.docx) programowo: python-docx, szablony docxtpl, korespondencja seryjna, tabele, konwersja z markdown i Microsoft Graph dla dokumentów w chmurze.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.