PowerBi-Codex-Plugin

Use when Power BI tenant administration needs Admin API playbooks for workspace inventory, usage metrics, refresh failures, endorsements, sensitivity labels, sharing risk, gateways, and capacity.

Coordinate virtual Power BI expert roles such as BI Architect, DAX Expert, Power Query Engineer, Fabric Architect, Finance BI Lead, QA Reviewer, Security Reviewer, and CoE Lead. Use to replace manual expert routing with role-based analysis and deliverables.

Use when DAX measures require executable or semi-executable unit tests, query-based assertions, XMLA or Tabular Editor validation, edge cases, totals, RLS contexts, and reconciliation evidence.

Use when Power BI work needs PBIP, Git, deployment pipelines, semantic model versioning, Tabular Editor, DAX checks, regression tests, release gates, workspace promotion, or CI/CD governance.

Use when the user asks for Expert Mode, senior Power BI engineering, deep model/report/DAX/M review, precise control, or developer-facing Power BI delivery with explicit technical evidence.

Use when the user asks for Generalisten Mode, Prozess Manager mode, Process Owner mode, autonomous BI delivery, or wants the plugin to handle Power BI work end-to-end without requiring expert knowledge.

Classify Power BI requests and route them to the right delivery path. Use when a request may involve data sources, semantic models, DAX, UX, governance, performance, migration, Fabric architecture, portfolio cleanup, or business problem design.

Use when Power BI or Fabric work needs live metadata discovery from tenants, semantic models, SQL, lakehouse, SAP, Salesforce, Dynamics, Snowflake, APIs, or files before design decisions.

Use when Power BI work spans multiple customers, tenants, business units, or MSP-style delivery boundaries and requires isolated policies, artifacts, evidence, rollout status, and governance.

Use when a Power BI design should become PBIP or TMDL-ready structures, model folders, table specs, measure files, calculation groups, perspectives, roles, and deployment-ready artifacts.

Use when a user asks to generate, build, or improve a Power BI report/model package from a process request, source description, or business question using the executable report-package path.

Build, review, and validate generic Power BI reports and dashboards from any supported data source. Use for report requirements, data ingestion, semantic models, DAX, Power Query, PBIP/PBIR, RLS, refresh, governance, page layouts, visual selection, validation, and business problems such as churn, FiCO, sales, supply chain, service, HR, risk, and operations.

Use when Power BI Desktop produces a Frown error, PBIP load failure, model validation error, visual error, DirectQuery error, Power Query load error, or Desktop crash that must be mapped to likely fixes.

Use when a Power BI semantic model relationship graph must be checked for ambiguous paths, fact-to-fact chains, wrong filter direction, unsupported topology, DirectQuery/OLAP limitations, or certification risk.

Use when each source table or query must be routed to the correct native Power Query connector pattern, including Excel, CSV, Folder, SharePoint, SQL, Fabric, OData, REST, SaaS, ODBC/OLE DB, or embedded demo mode.

Use when generated PBIP, PBIR, TMDL, report, or semantic model artifacts must be opened and smoke-tested in the installed Power BI Desktop version with Frown, process, and load checks.

Use when PBIR report visuals must be validated against actual semantic model tables, columns, measures, visual roles, query references, and supported visual types.

Use when learning which Power BI-generated actions actually improved KPIs, closed exceptions, created ROI, or should change future recommendations.

Use when multiple Power BI AI expert agents must be coordinated across consultant, source mapper, modeler, DAX expert, Power Query expert, designer, QA, CoE reviewer, and release manager roles.

Use when AI-generated Power BI decisions must be explained with evidence, confidence, assumptions, missing data, and rationale for model, DAX, Power Query, visual, and connector choices.

Use when benchmarking Power BI process analytics, KPI maturity, data readiness, report quality, CoE maturity, and expert-replacement maturity against internal or industry bands.

Use when business users need plain-language explanations of Power BI numbers, filters, source lineage, DAX logic, missing data, and model assumptions.

Use when a business question must be translated into required facts, dimensions, measures, source fields, drilldowns, report pages, and validation tests.

Use when determining whether a Power BI semantic model, report, data product, or process pack is ready for endorsement, promotion, certification, or production release.

Use when Power BI and Fabric costs must be compared with usage, business value, refresh load, capacity pressure, storage mode, and consolidation opportunities.

Use when a Power BI data product must pass end-to-end certification across KPI contracts, semantic model, DAX, M, RLS/OLS, refresh, UX, owner acceptance, release evidence, and CoE decision.

Use when data quality issues must be translated into business impact on KPIs, reports, process decisions, certification readiness, and operational actions.

Use when DAX measures need executable test cases, expected values, reconciliation queries, edge cases, and regression checks.

Use when KPI exceptions, anomalies, delays, risks, or threshold breaches must be converted into prioritized actions with owner, cause, impact, due date, and retest condition.

Use when generating boardroom-ready Power BI executive packs with narratives, KPI movements, risks, decisions, actions, confidence, data gaps, and changes since last meeting.

Use when measuring how much Power BI expert, designer, data analyst, DAX, M, modeling, QA, governance, and documentation work was replaced by AI/KI skills.

Use when creating governed prompt packs for Process Owners, Data Analysts, Data Stewards, CoE reviewers, executives, BI developers, or IT roles using approved boundaries and evidence requirements.

Use when departments define the same KPI differently and need conflict detection, side-by-side comparison, certified standard definition, variants, and downstream impact analysis.

Use when a business KPI description must be compiled into KPI contract, DAX measure design, test cases, reconciliation logic, report placement, and owner acceptance criteria.

Use when creating, browsing, reusing, governing, or certifying an internal marketplace of Power BI KPI contracts with definitions, owners, DAX, sources, tests, and variants.

Use when a source field, Power Query step, model column, measure, relationship, RLS rule, or report visual change needs lineage and downstream blast-radius analysis.

Use when migrating Excel, Access, Tableau, Qlik, SSRS, legacy PBIX, manual reports, or old semantic models into governed Power BI data products.

Use when generating business owner or process owner acceptance artifacts for KPIs, reports, models, tests, known limitations, and sign-off.

Use when an existing PBIX, PBIP, TMDL, report, model, DAX catalog, or Power Query project must be reviewed and refactored for model quality, performance, governance, UX, and maintainability.

Use when producing release evidence for Power BI artifacts, including change summary, model diff, DAX changes, M changes, screenshots, tests, risks, rollback, and owner sign-off.