Power BI Feedback & Iteration
Reference kit for the feedback and iteration phase. The power-bi-developer
agent orchestrates the workflow; this skill provides the supporting reference
material.
Always search Microsoft Learn (microsoft-learn-mcp/microsoft_docs_search)
for best practices before implementing any change.
When to use this skill
- You received user feedback on an existing report
- You need to classify, prioritize, or scope a change
- You need to run post-change validation
- You need to compare design variants (A/B)
- You need to run or document formal UAT
- You need a PBIP-aware Git workflow, commit convention, or changelog
Reference index
| Topic |
File |
| Classify feedback (12 categories × severity) |
references/classification.md |
| Prioritize changes (impact × effort matrix) |
references/prioritization.md |
| Intake questions to ask the user |
references/feedback-intake-template.md |
| What each change touches (file-level impact) |
references/change-impact-scoping.md |
| Post-change validation checklist |
references/validation-checklist.md |
| A/B variant testing with Git branches |
references/ab-variant-testing.md |
| Formal UAT workflow |
references/uat.md |
| PBIP Git diff guide + commit conventions |
references/git-pbip-diff-guide.md |
| Changelog / release-notes template |
references/changelog-template.md |
| Performance quick check (points to perf skill) |
references/performance-quick-check.md |
Iteration cycle overview
Feedback → Intake → Classify → Scope → Prioritize → Route (via agent) → Implement → Validate → Release
↑ │
└──────────────────────────── Next cycle ────────────────────────────────────────────────────┘
Skill workflow
- Intake — apply references/feedback-intake-template.md to capture symptom, expected behavior, reproduction, reporter, impact
- Classify — apply references/classification.md to assign one of 12 categories + severity
- Scope — apply references/change-impact-scoping.md to identify affected files, downstream validation, and risk
- Prioritize — apply references/prioritization.md (impact × effort)
- Route — the
power-bi-developer agent consults its routing table and dispatches to the correct downstream skill (see the agent's Phase 5 routing table)
- Implement — done by the routed downstream skill (power-bi-semantic-model, power-bi-dax-development, power-bi-report-design, power-bi-report-authoring, or power-bi-performance-troubleshooting)
- Validate — apply references/validation-checklist.md before marking the item resolved
- Release (optional, production reports) — run references/uat.md, tag in Git per references/git-pbip-diff-guide.md, update references/changelog-template.md
When the user contests between two designs
See references/ab-variant-testing.md — build both as Git branches, compare side-by-side with a weighted evaluation grid, merge the winner, document the decision.
When performance is the feedback
First-pass triage with references/performance-quick-check.md. For deep diagnosis and optimization, route to the power-bi-performance-troubleshooting skill.
Related Skills
| Skill |
Relationship |
When |
power-bi-performance-troubleshooting |
Routes to |
Performance-related feedback gets deep diagnosis here |
power-bi-semantic-model |
Routes to |
Data accuracy, missing data, RLS, and relationship issues |
power-bi-dax-development |
Routes to |
New or broken measures, calculation fixes |
power-bi-report-design |
Routes to |
Chart type changes, layout redesign, theme updates |
power-bi-report-authoring |
Routes to |
Visual formatting fixes, JSON corrections, mobile layout |
power-bi-business-analysis |
Routes to |
New requirements or significant scope expansion |
Anti-patterns
- ❌ Don't skip classification because the fix seems obvious — classification drives correct routing
- ❌ Don't accept aggregated feedback ("users are complaining") — decompose into specific items
- ❌ Don't mark items resolved without running the validation checklist
- ❌ Don't release to production without a changelog entry
- ❌ Don't duplicate routing logic in this skill — the agent is the single source of truth
Relationship to the agent
This skill is reference material. The power-bi-developer agent Phase 5
is the orchestration:
- Agent decides which skill fixes which category of feedback
- This skill provides the templates, taxonomies, and checklists used within Phase 5
Do not duplicate routing logic here. If a routing rule needs updating, update
the agent's routing table.
1---2name: power-bi-feedback-iteration3description: Reference kit for the feedback and iteration phase of a Power BI project. Provides classification taxonomy, prioritization matrix, intake template, change-impact scoping, post-change validation checklist, A/B variant testing workflow, formal UAT workflow, PBIP Git diff guide, changelog template, and a performance quick-check pointer. Use this skill whenever the user provides feedback on an existing Power BI report, requests iteration, wants to run UAT, or needs to document changes. Routing (feedback → correct downstream skill) is owned by the power-bi-developer agent, not by this skill. Triggers include: "user feedback", "improve report", "fix report", "iterate on the report", "report review", "rebuild report", "UAT", "changelog", "release notes", "users are complaining", "performance issue", "add/remove/modify a page/measure/visual on an existing report". Do NOT use this skill for brand-new projects (use power-bi-business-analysis to start from scratch).4---56# Power BI Feedback & Iteration78Reference kit for the feedback and iteration phase. The `power-bi-developer`9agent orchestrates the workflow; this skill provides the supporting reference10material.1112**Always search Microsoft Learn** (`microsoft-learn-mcp/microsoft_docs_search`)13for best practices before implementing any change.1415## When to use this skill1617- You received user feedback on an existing report18- You need to classify, prioritize, or scope a change19- You need to run post-change validation20- You need to compare design variants (A/B)21- You need to run or document formal UAT22- You need a PBIP-aware Git workflow, commit convention, or changelog2324## Reference index2526| Topic | File |27|---|---|28| Classify feedback (12 categories × severity) | [references/classification.md](references/classification.md) |29| Prioritize changes (impact × effort matrix) | [references/prioritization.md](references/prioritization.md) |30| Intake questions to ask the user | [references/feedback-intake-template.md](references/feedback-intake-template.md) |31| What each change touches (file-level impact) | [references/change-impact-scoping.md](references/change-impact-scoping.md) |32| Post-change validation checklist | [references/validation-checklist.md](references/validation-checklist.md) |33| A/B variant testing with Git branches | [references/ab-variant-testing.md](references/ab-variant-testing.md) |34| Formal UAT workflow | [references/uat.md](references/uat.md) |35| PBIP Git diff guide + commit conventions | [references/git-pbip-diff-guide.md](references/git-pbip-diff-guide.md) |36| Changelog / release-notes template | [references/changelog-template.md](references/changelog-template.md) |37| Performance quick check (points to perf skill) | [references/performance-quick-check.md](references/performance-quick-check.md) |3839## Iteration cycle overview4041```42Feedback → Intake → Classify → Scope → Prioritize → Route (via agent) → Implement → Validate → Release43 ↑ │44 └──────────────────────────── Next cycle ────────────────────────────────────────────────────┘45```4647## Skill workflow48491. **Intake** — apply [references/feedback-intake-template.md](references/feedback-intake-template.md) to capture symptom, expected behavior, reproduction, reporter, impact502. **Classify** — apply [references/classification.md](references/classification.md) to assign one of 12 categories + severity513. **Scope** — apply [references/change-impact-scoping.md](references/change-impact-scoping.md) to identify affected files, downstream validation, and risk524. **Prioritize** — apply [references/prioritization.md](references/prioritization.md) (impact × effort)535. **Route** — the `power-bi-developer` agent consults its routing table and dispatches to the correct downstream skill (see the agent's Phase 5 routing table)546. **Implement** — done by the routed downstream skill (power-bi-semantic-model, power-bi-dax-development, power-bi-report-design, power-bi-report-authoring, or power-bi-performance-troubleshooting)557. **Validate** — apply [references/validation-checklist.md](references/validation-checklist.md) before marking the item resolved568. **Release** (optional, production reports) — run [references/uat.md](references/uat.md), tag in Git per [references/git-pbip-diff-guide.md](references/git-pbip-diff-guide.md), update [references/changelog-template.md](references/changelog-template.md)5758## When the user contests between two designs5960See [references/ab-variant-testing.md](references/ab-variant-testing.md) — build both as Git branches, compare side-by-side with a weighted evaluation grid, merge the winner, document the decision.6162## When performance is the feedback6364First-pass triage with [references/performance-quick-check.md](references/performance-quick-check.md). For deep diagnosis and optimization, route to the `power-bi-performance-troubleshooting` skill.6566## Related Skills6768| Skill | Relationship | When |69|---|---|---|70| `power-bi-performance-troubleshooting` | Routes to | Performance-related feedback gets deep diagnosis here |71| `power-bi-semantic-model` | Routes to | Data accuracy, missing data, RLS, and relationship issues |72| `power-bi-dax-development` | Routes to | New or broken measures, calculation fixes |73| `power-bi-report-design` | Routes to | Chart type changes, layout redesign, theme updates |74| `power-bi-report-authoring` | Routes to | Visual formatting fixes, JSON corrections, mobile layout |75| `power-bi-business-analysis` | Routes to | New requirements or significant scope expansion |7677## Anti-patterns7879- ❌ Don't skip classification because the fix seems obvious — classification drives correct routing80- ❌ Don't accept aggregated feedback ("users are complaining") — decompose into specific items81- ❌ Don't mark items resolved without running the validation checklist82- ❌ Don't release to production without a changelog entry83- ❌ Don't duplicate routing logic in this skill — the agent is the single source of truth8485## Relationship to the agent8687This skill is **reference material**. The `power-bi-developer` agent Phase 588is the **orchestration**:8990- Agent decides *which* skill fixes *which* category of feedback91- This skill provides the *templates, taxonomies, and checklists* used within Phase 59293Do not duplicate routing logic here. If a routing rule needs updating, update94the agent's routing table.95
datacoolie