plan-bi-roadmap — Claude Code command: BI roadmap prioritization
plan-bi-roadmap — a Claude Code command that scores a BI initiative backlog by impact, effort, and strategic alignment, then drafts a governed roadmap.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/plan-bi-roadmap.mdWhat plan-bi-roadmap does
The command takes four required parameters: --inputs for the backlog source, --capacity for how many initiatives the team can absorb next cycle, --themes for a comma-separated list of strategic themes (revenue, success, marketing, product), and --audience to tailor the final document (exec, bi-lead, revops, or async). An optional --constraints parameter covers tooling limits, compliance notes, or dependency flags.
Five steps run in sequence: backlog normalization against OKRs, a scoring pass on impact, effort, risk, and sponsor readiness, roadmap drafting with capacity allocation and dependency flagging, a governance layer that attaches owners and KPI definitions, and final packaging into a deck or memo shaped for the chosen audience. Four agents and skills are invoked internally: insights-program-director orchestrates prioritization, data-architecture-lead checks feasibility and data contracts, metric-governance-kit locks KPI definitions, and dashboard-playbook feeds in adoption considerations.
If the backlog lacks a sponsor field, the sponsor readiness score will be incomplete — pass those details through --constraints to compensate.
What it helps with
- score and rank a BI initiative backlog against strategic themes
- allocate a fixed capacity budget across a planning cycle
- tie initiatives to OKRs and assign accountability owners
- generate a governance tracker with milestones and KPI definitions
- package the roadmap differently for exec, revops, or async audiences
Example prompts for the agent
- /business-intelligence:plan-bi-roadmap --inputs backlog.csv --capacity 5 --themes revenue,success --audience exec
- Score the Jira backlog, cap at 8 initiatives, themes product and marketing, audience bi-lead
- Build a roadmap from
q3-backlog.csvwith compliance constraints, audience revops
How to install plan-bi-roadmap
Manually: put the files in place
.claude/commands/plan-bi-roadmap.mdCall it with /plan-bi-roadmap. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/plan-bi-roadmap.mdCall it with /prompts:plan-bi-roadmap. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/plan-bi-roadmap.prompt.mdManually: put the files in place
.gemini/commands/plan-bi-roadmap.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about plan-bi-roadmap
How do I install plan-bi-roadmap in Claude Code?
Place the file plan-bi-roadmap.md inside the .claude/commands/ directory of your project.
What does the plan-bi-roadmap command do?
It ingests a BI initiative backlog, scores each item by impact, effort, risk, and sponsor readiness, drafts a swimlane roadmap within a given capacity, and produces a governance tracker with owners and KPIs alongside a decision log.
What backlog formats does plan-bi-roadmap accept?
The --inputs parameter accepts CSV files, Notion databases, Jira boards, and spreadsheets — specify the source when calling the command.
Source text
plan-bi-roadmap.md · Apache-2.0
--- name: plan-bi-roadmap description: Prioritizes BI initiatives with impact, effort, and governance alignment. usage: /business-intelligence:plan-bi-roadmap --inputs backlog.csv --capacity 5 --themes revenue,success --audience exec --- # Command: plan-bi-roadmap ## Inputs - **inputs** – backlog source (csv, notion, jira board, spreadsheet). - **capacity** – number of initiatives supportable next cycle. - **themes** – comma-separated strategic themes (revenue, success, marketing, product). - **audience** – exec | bi-lead | revops | async. - **constraints** – optional notes on tooling, compliance, or dependency limits. ## Workflow 1. **Backlog Normalization** – ingest initiatives, tag by theme, align to OKRs. 2. **Scoring Engine** – calculate impact, effort, risk, and sponsor readiness. 3. **Roadmap Draft** – allocate capacity, stage workstreams, and highlight dependencies. 4. **Governance Layer** – attach owners, status checkpoints, and success metrics. 5. **Packaging** – tailor roadmap deck/memo with decisions + asks for audience. ## Outputs - Prioritized roadmap with scoring table + swimlane view. - Governance tracker with owners, milestones, and KPI definitions. - Decision log capturing trade-offs and follow-up actions. ## Agent/Skill Invocations - `insights-program-director` – orchestrates prioritization + stakeholder alignment. - `data-architecture-lead` – validates feasibility and data contract implications. - `metric-governance-kit` skill – ensures KPI definitions are locked. - `dashboard-playbook` skill – provides adoption considerations for planning. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents