@luquimbo/bi-superpowers 3.2.0 → 4.1.1

package/skills/report-design/scripts/validate-pbir.js

@@ -0,0 +1,322 @@
+#!/usr/bin/env node
+/**
+ * validate-pbir.js — allowlist-driven PBIR validator.
+ *
+ * Complements `pbi report validate` (which does schema sanity) by enforcing
+ * the native-visuals allowlist maintained in create-visual.js. Catches:
+ *
+ *   - visualType that's not a native PBIR type (e.g. `stackedBarChart`,
+ *     typos) — Desktop renders these as "objeto visual personalizado" but
+ *     the CLI validate passes them. This is the exact bug F1 that motivated
+ *     the migration away from the CLI.
+ *
+ *   - bindings on roles that the type doesn't declare (e.g. `--bind size`
+ *     on a funnelChart) — CLI validate doesn't catch these either.
+ *
+ *   - missing required roles (e.g. a barChart with no Category).
+ *
+ *   - visualContainer schema drift (wrong $schema URL or missing `name`).
+ *
+ * Usage:
+ *   node validate-pbir.js <reportPath>
+ *   node validate-pbir.js --json <reportPath>    # machine-readable output
+ *
+ * Exit codes:
+ *   0  valid
+ *   1  validation errors found
+ *   2  I/O error (bad path, corrupt JSON)
+ *
+ * NOT a replacement for `pbi report validate` — run both. This validator
+ * trusts that the .Report folder is structurally correct (has definition/,
+ * pages/, etc.) and focuses on visual-level correctness that the CLI misses.
+ */
+
+'use strict';
+
+const fs = require('fs');
+const path = require('path');
+
+const { NATIVE_VISUAL_TYPES, KNOWN_NON_NATIVE_TYPES } = require('./create-visual.js');
+
+const EXPECTED_VISUAL_SCHEMA =
+  'https://developer.microsoft.com/json-schemas/fabric/item/report/definition/visualContainer/2.7.0/schema.json';
+
+function fail(msg, code = 2) {
+  process.stderr.write(`validate-pbir: ${msg}\n`);
+  process.exit(code);
+}
+
+function parseArgs(argv) {
+  const out = {};
+  const positional = [];
+  for (let i = 0; i < argv.length; i += 1) {
+    const a = argv[i];
+    if (a === '--json') out.json = true;
+    else if (a === '-h' || a === '--help') out.help = true;
+    else if (a.startsWith('-')) fail(`unknown flag: ${a}`, 2);
+    else positional.push(a);
+  }
+  out.reportPath = positional[0];
+  return out;
+}
+
+function printHelp() {
+  process.stdout.write(
+    [
+      'Usage: validate-pbir.js [--json] <reportPath>',
+      '',
+      'Arguments:',
+      '  reportPath   Path to a .Report folder',
+      '',
+      'Options:',
+      '  --json       Emit JSON instead of human-readable output',
+      '  -h, --help   Show this help',
+      '',
+      'Exit codes:',
+      '  0  valid',
+      '  1  validation errors found',
+      '  2  I/O error',
+      '',
+    ].join('\n')
+  );
+}
+
+function listPages(reportPath) {
+  const pagesDir = path.join(reportPath, 'definition', 'pages');
+  if (!fs.existsSync(pagesDir)) {
+    fail(`pages directory not found: ${pagesDir}`, 2);
+  }
+  const out = [];
+  for (const entry of fs.readdirSync(pagesDir, { withFileTypes: true })) {
+    if (!entry.isDirectory()) continue;
+    const pageJsonPath = path.join(pagesDir, entry.name, 'page.json');
+    if (!fs.existsSync(pageJsonPath)) continue;
+    out.push({ name: entry.name, dir: path.join(pagesDir, entry.name) });
+  }
+  return out;
+}
+
+function listVisuals(pageDir) {
+  const visualsDir = path.join(pageDir, 'visuals');
+  if (!fs.existsSync(visualsDir)) return [];
+  const out = [];
+  for (const entry of fs.readdirSync(visualsDir, { withFileTypes: true })) {
+    if (!entry.isDirectory()) continue;
+    const visualJsonPath = path.join(visualsDir, entry.name, 'visual.json');
+    if (!fs.existsSync(visualJsonPath)) continue;
+    out.push({ name: entry.name, path: visualJsonPath });
+  }
+  return out;
+}
+
+function readJsonSafe(filePath) {
+  try {
+    const raw = fs.readFileSync(filePath, 'utf8');
+    return { data: JSON.parse(raw), err: null };
+  } catch (err) {
+    return { data: null, err };
+  }
+}
+
+// Extracts the set of roles that have at least one projection bound.
+function boundRoles(visualData) {
+  const qs = visualData && visualData.visual && visualData.visual.query && visualData.visual.query.queryState;
+  if (!qs || typeof qs !== 'object') return new Set();
+  const bound = new Set();
+  for (const [role, spec] of Object.entries(qs)) {
+    const projections = spec && spec.projections;
+    if (Array.isArray(projections) && projections.length > 0) bound.add(role);
+  }
+  return bound;
+}
+
+function validateVisual(visual) {
+  const errors = [];
+  const { data, path: filePath } = visual;
+
+  // Schema URL check.
+  if (data.$schema !== EXPECTED_VISUAL_SCHEMA) {
+    errors.push({
+      severity: 'warn',
+      rule: 'schema-url',
+      message: `unexpected $schema (got ${data.$schema || 'none'})`,
+    });
+  }
+
+  // `name` must exist and match the folder.
+  if (typeof data.name !== 'string' || !data.name) {
+    errors.push({ severity: 'error', rule: 'name', message: 'missing "name"' });
+  }
+
+  const vt = data.visual && data.visual.visualType;
+  if (!vt) {
+    errors.push({ severity: 'error', rule: 'visual-type', message: 'missing visualType' });
+    return errors;
+  }
+
+  // Allowlist: known non-native (like stackedBarChart).
+  if (KNOWN_NON_NATIVE_TYPES[vt]) {
+    errors.push({
+      severity: 'error',
+      rule: 'non-native-type',
+      visualType: vt,
+      message: KNOWN_NON_NATIVE_TYPES[vt],
+    });
+    return errors;
+  }
+
+  const def = NATIVE_VISUAL_TYPES[vt];
+  if (!def) {
+    errors.push({
+      severity: 'error',
+      rule: 'unknown-type',
+      visualType: vt,
+      message: `visualType "${vt}" is not in the native allowlist. Run create-visual.js --list-types for the canonical list.`,
+    });
+    return errors;
+  }
+
+  // Check required roles are bound (skip for textbox — no roles).
+  if (vt !== 'textbox') {
+    const bound = boundRoles(data);
+    for (const [role, spec] of Object.entries(def.roles)) {
+      if (spec.required && !bound.has(role)) {
+        errors.push({
+          severity: 'error',
+          rule: 'missing-required-role',
+          visualType: vt,
+          role,
+          message: `required role "${role}" has no projections (visualType: ${vt})`,
+        });
+      }
+    }
+
+    // Check that every bound role is valid for this type.
+    for (const role of bound) {
+      if (!(role in def.roles)) {
+        errors.push({
+          severity: 'error',
+          rule: 'invalid-role',
+          visualType: vt,
+          role,
+          message: `role "${role}" is not valid for visualType ${vt}. Valid: ${Object.keys(def.roles).join(', ') || '(none)'}`,
+        });
+      }
+    }
+  }
+
+  return errors;
+}
+
+function main() {
+  const args = parseArgs(process.argv.slice(2));
+  if (args.help) {
+    printHelp();
+    return;
+  }
+  if (!args.reportPath) fail('reportPath is required. Run --help for usage.', 2);
+
+  const reportPath = path.resolve(args.reportPath);
+  if (!fs.existsSync(reportPath)) fail(`not found: ${reportPath}`, 2);
+
+  const pages = listPages(reportPath);
+  const results = {
+    reportPath,
+    pagesChecked: pages.length,
+    visualsChecked: 0,
+    errors: [],
+  };
+
+  for (const page of pages) {
+    const visuals = listVisuals(page.dir);
+    // Track visual.name per page so we can flag duplicates. PBI Desktop
+    // does not reject a duplicate-name pair on load, but downstream tooling
+    // that references visuals by name (filters, bookmarks, selections) gets
+    // ambiguous — validate-pbir treats it as a hard error.
+    const namesSeenOnPage = new Map();
+    for (const v of visuals) {
+      results.visualsChecked += 1;
+      const { data, err } = readJsonSafe(v.path);
+      if (err) {
+        results.errors.push({
+          page: page.name,
+          visual: v.name,
+          severity: 'error',
+          rule: 'bad-json',
+          message: `could not parse visual.json: ${err.message}`,
+        });
+        continue;
+      }
+
+      // Duplicate-name check (page-scoped).
+      const declaredName = data && typeof data.name === 'string' ? data.name : null;
+      if (declaredName) {
+        if (namesSeenOnPage.has(declaredName)) {
+          results.errors.push({
+            page: page.name,
+            visual: v.name,
+            severity: 'error',
+            rule: 'duplicate-name',
+            message: `visual name "${declaredName}" is also used by "${namesSeenOnPage.get(declaredName)}" on this page`,
+          });
+        } else {
+          namesSeenOnPage.set(declaredName, v.name);
+        }
+      }
+
+      const visualErrors = validateVisual({ data, path: v.path });
+      for (const e of visualErrors) {
+        results.errors.push({
+          page: page.name,
+          visual: v.name,
+          ...e,
+        });
+      }
+    }
+  }
+
+  const errorCount = results.errors.filter((e) => e.severity === 'error').length;
+  const warnCount = results.errors.filter((e) => e.severity === 'warn').length;
+  const valid = errorCount === 0;
+
+  if (args.json) {
+    process.stdout.write(JSON.stringify({ ...results, valid, errorCount, warnCount }, null, 2) + '\n');
+  } else {
+    const W = 77; // inner width between the | borders
+    const padRow = (label, value) => {
+      const text = `${label}: ${value}`;
+      return `| ${text}${' '.repeat(Math.max(0, W - text.length - 1))}|`;
+    };
+    const border = `+${'-'.repeat(W)}+`;
+    process.stdout.write(border + '\n');
+    process.stdout.write(padRow('valid', valid ? 'True' : 'False') + '\n');
+    process.stdout.write(padRow('pages_checked', String(results.pagesChecked)) + '\n');
+    process.stdout.write(padRow('visuals_checked', String(results.visualsChecked)) + '\n');
+    process.stdout.write(padRow('errors', String(errorCount)) + '\n');
+    process.stdout.write(padRow('warnings', String(warnCount)) + '\n');
+    process.stdout.write(border + '\n');
+    if (results.errors.length) {
+      process.stdout.write('\nIssues:\n');
+      for (const e of results.errors) {
+        const icon = e.severity === 'error' ? '✗' : '⚠';
+        const loc = `${e.page}/${e.visual}`;
+        process.stdout.write(`  ${icon} [${e.rule}] ${loc}: ${e.message}\n`);
+      }
+      process.stdout.write('\n');
+    }
+  }
+
+  process.exit(valid ? 0 : 1);
+}
+
+module.exports = {
+  validateVisual,
+  boundRoles,
+  listPages,
+  listVisuals,
+  parseArgs,
+};
+
+if (require.main === module) {
+  main();
+}

package/src/content/base.md

@@ -59,67 +59,13 @@ You are a **Business Intelligence Expert** with deep knowledge of:
 
 ---
 
-## Available Resources
-
-### Library Structure
-
-```
-library/
-├── snippets/           # Reusable code patterns
-│   ├── dax/            # DAX patterns and formulas
-│   ├── power-query/    # M language patterns
-│   ├── excel-formulas/ # Excel function patterns
-│   ├── report-design/  # Chart selection, accessibility, layouts
-│   └── governance/     # Naming conventions, review checklists
-├── templates/          # Project templates
-│   ├── power-bi/
-│   ├── excel/
-│   └── data-models/
-├── themes/             # Visual themes
-│   └── power-bi/       # Power BI JSON themes
-└── examples/           # Reference implementations
-    ├── finance-reporting/
-    ├── hr-analytics/
-    ├── retail-analytics/
-    ├── supply-chain/
-    └── marketing-analytics/
-```
-
-### Skills (24 Total)
-
-#### Command Skills (11 Interactive Wizards)
+## Available Skills (3)
 
 | Skill | Purpose | Trigger |
 |-------|---------|---------|
-| `/project-kickoff` | Analyze and plan projects | "analyze project", "get started" |
-| `/data-model-design` | Design star schema models | "design model", "create tables" |
-| `/theme-tweaker` | Customize Power BI themes | "customize theme", "change colors" |
-| `/rls-design` | Row-level security design | "RLS", "security" |
-| `/pbi-connect` | Connect to Power BI Desktop | "connect Power BI", "MCP" |
-| `/fabric-scripts` | Fabric automation scripts | "Fabric", "scripts" |
-| `/contributions` | Contribution validation | "contribute", "PR" |
-| `/dax-doctor` | DAX debugging wizard | "debug DAX", "fix measure" |
-| `/model-documenter` | Model documentation generator | "document model", "data dictionary" |
-| `/migration-assistant` | Migration and upgrade assistant | "migrate", "convert to PBIP" |
-| `/report-layout` | Report page layout planner | "report layout", "page design" |
-
-#### Reference Skills (13 Background Knowledge)
-
-| Skill | Purpose |
-|-------|---------|
-| `/dax` | DAX writing and optimization |
-| `/power-query` | Power Query / M language patterns |
-| `/data-modeling` | Star schema theory and patterns |
-| `/excel-formulas` | Modern Excel formula patterns |
-| `/fast-standard` | FAST financial modeling standard |
-| `/query-performance` | Performance optimization |
-| `/data-quality` | Data validation patterns |
-| `/testing-validation` | Testing and validation patterns |
-| `/governance` | Naming conventions and standards |
-| `/semantic-model` | Semantic model best practices |
-| `/report-design` | Report design and visualization |
-| `/deployment` | CI/CD and deployment patterns |
-| `/dax-udf` | DAX user-defined functions (UDFs) |
+| `/project-kickoff` | Analyze a BI project, build the semantic model, and write AGENTS.md | "analyze project", "get started", "kickoff" |
+| `/pbi-connect` | Connect to Power BI Desktop via the official Modeling MCP | "connect Power BI", "MCP" |
+| `/report-design` | Generate 3-page PBIR report via `pbi-cli-tool` (cards, charts, matrix, slicers) | "crear reportes", "report design", "dashboard" |
 
 ---
 
@@ -177,30 +123,28 @@ in
 
 ### Official Microsoft MCP Stack
 
-BI Agent Superpowers is now plugin-first and should prefer these official Microsoft MCPs:
+BI Agent Superpowers ships 2 official Microsoft MCP servers:
 
-- `powerbi-remote` for remote Power BI / Fabric access
-- `fabric-mcp-server` for Microsoft Fabric workflows
-- `powerbi-modeling-mcp` for local semantic model work on Windows
+- `powerbi-modeling-mcp` — local stdio MCP for Power BI Desktop on Windows
+- `microsoft-learn` — HTTP MCP for official Power BI / Fabric / DAX docs
 
 ### Connection model
 
-**Remote / Fabric flows**
+**Local Modeling flow (Windows only)**
 ```
-AI Assistant → official Microsoft MCP → Fabric / Power BI service
+AI Assistant → local launcher → powerbi-modeling-mcp.exe --start → Power BI Desktop / PBIP semantic model
 ```
 
-**Local Modeling flow (Windows only)**
+**Docs flow (any platform)**
 ```
-AI Assistant → local launcher → powerbi-modeling-mcp.exe --start → Power BI Desktop / PBIP / Fabric model
+AI Assistant → microsoft-learn HTTP MCP → learn.microsoft.com docs
 ```
 
 ### Practical guidance
 
 - Prefer `.mcp.json` in the plugin root over tool-specific MCP config files.
 - Never invent or hardcode local ports for the official Modeling MCP flow.
-- On macOS/Linux, explain that the local Modeling MCP is unavailable and continue with `powerbi-remote` or `fabric-mcp-server`.
-- Excel remains supported as guidance, snippets, and templates, but it is not configured as a default MCP in the main product path.
+- On macOS/Linux, explain that the local Modeling MCP is unavailable and fall back to `microsoft-learn` for docs. Live editing of a local model requires Windows.
 
 ---
 

package/src/content/mcp-requirements.json

@@ -1,30 +1,5 @@
 {
   "mcps": [
-    {
-      "name": "powerbi-remote",
-      "displayName": "Power BI Remote MCP",
-      "source": "http",
-      "url": "https://api.fabric.microsoft.com/v1/mcp/powerbi",
-      "docs": "https://learn.microsoft.com/en-us/power-bi/developer/mcp/remote-mcp-server-get-started",
-      "requiresAuth": true,
-      "config": {
-        "type": "http",
-        "url": "https://api.fabric.microsoft.com/v1/mcp/powerbi"
-      }
-    },
-    {
-      "name": "fabric-mcp-server",
-      "displayName": "Microsoft Fabric MCP Server",
-      "source": "npx",
-      "package": "@microsoft/fabric-mcp@latest",
-      "docs": "https://github.com/microsoft/mcp/tree/main/servers/Fabric.Mcp.Server",
-      "requiresAuth": true,
-      "config": {
-        "type": "stdio",
-        "command": "npx",
-        "args": ["-y", "@microsoft/fabric-mcp@latest", "server", "start", "--mode", "all"]
-      }
-    },
     {
       "name": "powerbi-modeling-mcp",
       "displayName": "Power BI Modeling MCP",

package/src/content/routing.md

@@ -50,15 +50,9 @@ Scan current directory for relevant files:
 
 | Files Detected | Suggested Skill |
 |----------------|-----------------|
-| `.pbix` files | `/project-kickoff` (if not analyzed) |
-| `.tmdl` files | `/data-model-design` or `/dax` |
-| `.tmdl` files + no docs | `/model-documenter` |
-| `.xlsx` / `.xlsm` files | `/excel-formulas` |
-| `dataflows/` folder | `/fabric-scripts` |
-| `theme.json` | `/theme-tweaker` |
-| `scripts/` with `.py` | `/fabric-scripts` |
-| `.pbip` + no `.git` | `/migration-assistant` (suggest PBIP+Git) |
-| `deployment/` or `.github/workflows/` | `/deployment` |
+| `.pbix` / `.pbip` / `.tmdl` files | `/project-kickoff` (if not analyzed) |
+| `.xlsx` / `.xlsm` files | `/project-kickoff` |
+| No plugin `.mcp.json` found when user asks about Power BI | `/pbi-connect` |
 
 ### 4. CHECK KEYWORDS
 
@@ -66,31 +60,13 @@ Match user message against skill triggers:
 
 | Keywords | Skill |
 |----------|-------|
-| "DAX", "measure", "CALCULATE", "SUMX" | `/dax` |
-| "data model", "star schema", "fact table", "dimension" | `/data-modeling` |
-| "Power Query", "M code", "query folding", "ETL" | `/power-query` |
-| "theme", "colors", "branding", "visual style" | `/theme-tweaker` |
-| "Excel", "formula", "XLOOKUP", "dynamic array" | `/excel-formulas` |
-| "kickoff", "analyze project", "project analysis" | `/project-kickoff` |
-| "design model", "create model", "new data model" | `/data-model-design` |
-| "FAST", "financial model", "spreadsheet model" | `/fast-standard` |
-| "RLS", "row-level security", "data security", "user filter" | `/rls-design` |
-| "performance", "optimize", "slow", "DAX Studio" | `/query-performance` |
-| "Fabric", "scripts", "deploy", "sync", "dataflow" | `/fabric-scripts` |
-| "data quality", "validation", "null values", "profiling" | `/data-quality` |
-| "debug DAX", "fix measure", "DAX not working", "wrong result", "DAX error" | `/dax-doctor` |
-| "document model", "data dictionary", "model documentation" | `/model-documenter` |
-| "migrate", "upgrade", "convert to PBIP", "move to Fabric" | `/migration-assistant` |
-| "report layout", "page design", "visual placement", "dashboard layout" | `/report-layout` |
-| "naming convention", "governance", "standards" | `/governance` |
-| "semantic model", "TMDL", "DirectLake", "calculation groups" | `/semantic-model` |
-| "report design", "chart type", "visualization", "IBCS", "accessibility" | `/report-design` |
-| "CI/CD", "pipeline", "ALM", "DevOps", "git integration" | `/deployment` |
-| "UDF", "user defined function", "DEFINE FUNCTION", "DAX Lib", "NAMEOF", "functions.tmdl" | `/dax-udf` |
+| "kickoff", "analyze project", "analizar proyecto", "empezar", "qué tengo aquí?" | `/project-kickoff` |
+| "connect Power BI", "MCP connection", "Power BI Desktop", "conectar Power BI", "modeling mcp" | `/pbi-connect` |
+| "crear reportes", "armar reporte", "report design", "dashboard", "páginas del reporte", "visualizaciones" | `/report-design` |
 
 ### 5. DEFAULT BEHAVIOR
 
-No skill activated → respond as general BI assistant using AGENTS.md context.
+No skill activated → respond as general BI assistant using AGENTS.md context, referencing `library/` snippets when available in the user's project.
 
 ---
 
@@ -98,7 +74,7 @@ No skill activated → respond as general BI assistant using AGENTS.md context.
 
 If multiple skills match:
 
-1. **Explicit command always wins** - `/skill-name` overrides everything
+1. **Explicit command always wins** — `/skill-name` overrides everything
 2. **Context + keyword same skill** → Activate immediately
 3. **Context + keyword different skills** → Ask user which they prefer
 4. **Never activate multiple wizard-style skills** simultaneously
@@ -122,46 +98,18 @@ Users can customize routing in `config.json`:
 | Setting | Effect |
 |---------|--------|
 | `autoSuggestProjectKickoff: false` | Disable first-run auto-suggestion |
-| `disabledSkills: ["theme-tweaker"]` | Never suggest these skills |
-| `defaultSkill: "dax"` | Suggest this skill when context is ambiguous |
+| `disabledSkills: ["pbi-connect"]` | Never suggest these skills |
+| `defaultSkill: "project-kickoff"` | Suggest this skill when context is ambiguous |
 
 ---
 
-## Available Skills
-
-### Interactive Wizards (Command Skills)
+## Available Skills (3)
 
 | Skill | Purpose | Typical Duration |
 |-------|---------|-----------------|
-| `/project-kickoff` | Analyze new/existing projects | 5-10 min |
-| `/data-model-design` | Design star schema from scratch | 10-20 min |
-| `/theme-tweaker` | Customize Power BI themes | 5-10 min |
-| `/fabric-scripts` | Run Fabric automation scripts | 2-5 min |
-| `/rls-design` | Design row-level security | 10-15 min |
-| `/pbi-connect` | Connect to Power BI Desktop | 2-5 min |
-| `/contributions` | Contribution validation | 2-5 min |
-| `/dax-doctor` | DAX debugging and optimization | 5-15 min |
-| `/model-documenter` | Semantic model documentation | 5-10 min |
-| `/migration-assistant` | Migration and upgrade wizard | 10-20 min |
-| `/report-layout` | Report page layout planner | 10-15 min |
-
-### Reference Skills (Background Knowledge)
-
-| Skill | Purpose |
-|-------|---------|
-| `/dax` | DAX best practices and patterns |
-| `/power-query` | Power Query/M code patterns |
-| `/data-modeling` | Dimensional modeling guidance |
-| `/excel-formulas` | Modern Excel formula patterns |
-| `/fast-standard` | FAST financial modeling standard |
-| `/query-performance` | Performance optimization |
-| `/data-quality` | Data validation patterns |
-| `/testing-validation` | Testing and validation patterns |
-| `/governance` | Naming conventions and standards |
-| `/semantic-model` | Semantic model best practices |
-| `/report-design` | Report design and visualization |
-| `/deployment` | CI/CD and deployment patterns |
-| `/dax-udf` | DAX user-defined functions (UDFs) |
+| `/project-kickoff` | Analyze a BI project, build the semantic model, and write AGENTS.md | 10-20 min |
+| `/pbi-connect` | Connect to Power BI Desktop via the official Microsoft MCP | 2-5 min |
+| `/report-design` | Generate 3-page PBIR report via `pbi-cli-tool` CLI (requires close-write-open cycle) | 5-15 min |
 
 ---
 
@@ -170,14 +118,11 @@ Users can customize routing in `config.json`:
 After completing a skill, suggest the logical next step:
 
 | After Completing | Suggest Next |
-|-----------------|-------------|
-| `/project-kickoff` | `/data-model-design` → `/dax` → `/rls-design` |
-| `/data-model-design` | `/dax` → `/rls-design` → `/theme-tweaker` |
-| `/dax-doctor` | `/query-performance` or `/testing-validation` |
-| `/report-layout` | `/theme-tweaker` |
-| `/model-documenter` | `/governance` |
-| `/migration-assistant` | `/fabric-scripts` → `/deployment` |
-| `/rls-design` | `/testing-validation` |
+|-----------------|--------------|
+| `/project-kickoff` (model base ready) | `/report-design` to build the 3 report pages |
+| `/project-kickoff` (MCP not connected) | `/pbi-connect` to set up the connection |
+| `/report-design` | None — hand off to the user for refresh + iteration in Power BI Desktop |
+| `/pbi-connect` | Back to `/project-kickoff` if the project hasn't been analyzed yet |
 
 **Suggestion format:**
 ```