power-bi-report-plannerlisted

# power-bi-report-planner **This is the DIRECTOR skill.** It decides *what to build, where to place it, and how to display it* — then hands a locked, concrete design brief to the `power-bi-report-design` skill, which IMPLEMENTS it with the CLI. The planner does not run `pbi visual add` itself; it produces the spec. Think: architect (planner) vs. builder (report-design). The planner gathers requirements, inspects the model, **finds the story in the data**, designs a professional page on a fixed grid, waits for approval, then hands off to the implementer. **Division of labour:** ``` power-bi-report-planner (DIRECTOR) power-bi-report-design (IMPLEMENTER) ───────────────────────────────────── ────────────────────────────────────── Requirements + model inventory Reads the design brief Finds the story (queries the data) → Maps each spec row to a pbi command Designs the page (grid + visual spec) Runs pbi visual add / set-format / format Writes interpretive titles Applies display rules + header Locks the brief, gets approval Runs design QA self-check ``` **Workflow summary:** ``` Phase 1 — Define Clarification questions (3-5 rounds) ↓ Phase 2 — Inspect Semantic model inventory via pbi commands ↓ Phase 3 — Find the Query the data to discover the actual narrative / headline / Story tension — design follows the story, not the other way round ↓ Phase 4 — Design Lay the page o