# Powerbi Bilingual Documentation

> Use when Power BI artifacts, skills, delivery packs, reports, governance documents, training, acceptance evidence, or AI/KI outputs need matching documentation in en-US and de-DE.

- Skill: `rweisssieker-xp/powerbi-bilingual-documentation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rweisssieker-xp/powerbi-bilingual-documentation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rweisssieker-xp/powerbi-bilingual-documentation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: rweisssieker-xp (https://skillmd.com/u/rweisssieker-xp)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rweisssieker-xp/powerbi-bilingual-documentation

---


# Power BI Bilingual Documentation

Use this skill whenever the plugin creates or updates documentation, specs, delivery packs, report text, glossary terms, training, acceptance packs, governance artifacts, prompts, or AI/KI outputs.

## Required Languages

- `en-US`: primary international enterprise documentation.
- `de-DE`: German documentation for German-speaking stakeholders.

## Required Structure

Every substantial artifact should include:

1. English section/file: purpose, scope, owners, inputs, outputs, assumptions, validation, risks, next steps.
2. German section/file: same content, adapted terminology, not a partial summary.
3. Terminology table: business terms, KPI names, source-system terms, approved translations.
4. Non-translatable terms: source object names, system IDs, table names, field names, DAX names, API names.

## Output Requirements

- Use headings `## en-US` and `## de-DE` for compact artifacts.
- Use paired files for larger artifacts: `README.en-US.md` and `README.de-DE.md`, or `<artifact>.en-US.md` and `<artifact>.de-DE.md`.
- Keep KPI names, glossary terms, report titles, acceptance criteria, quality gates, and owner responsibilities aligned across both languages.
- Mark untranslated or disputed terms as `Translation review required`.