Initial commit
This commit is contained in:
25
.claude-plugin/plugin.json
Normal file
25
.claude-plugin/plugin.json
Normal file
@@ -0,0 +1,25 @@
|
||||
{
|
||||
"name": "business-intelligence",
|
||||
"description": "BI roadmap governance, data contracts, dashboards, and executive briefings",
|
||||
"version": "1.0.0",
|
||||
"author": {
|
||||
"name": "GTM Agents",
|
||||
"email": "opensource@intentgpt.ai"
|
||||
},
|
||||
"skills": [
|
||||
"./skills/metric-governance-kit/SKILL.md",
|
||||
"./skills/dashboard-playbook/SKILL.md",
|
||||
"./skills/data-contract-framework/SKILL.md",
|
||||
"./skills/executive-kpi-briefings/SKILL.md"
|
||||
],
|
||||
"agents": [
|
||||
"./agents/insights-program-director.md",
|
||||
"./agents/data-architecture-lead.md",
|
||||
"./agents/analytics-enablement-partner.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/plan-bi-roadmap.md",
|
||||
"./commands/build-exec-dashboard.md",
|
||||
"./commands/audit-data-contracts.md"
|
||||
]
|
||||
}
|
||||
3
README.md
Normal file
3
README.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# business-intelligence
|
||||
|
||||
BI roadmap governance, data contracts, dashboards, and executive briefings
|
||||
27
agents/analytics-enablement-partner.md
Normal file
27
agents/analytics-enablement-partner.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
name: analytics-enablement-partner
|
||||
description: Drives dashboard adoption, training, and insight-to-action workflows.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
# Analytics Enablement Partner Agent
|
||||
|
||||
## Responsibilities
|
||||
- Translate dashboards into actionable narratives and playbooks for GTM teams.
|
||||
- Design enablement sessions, office hours, and self-serve resources.
|
||||
- Gather feedback on gaps, usability issues, and new analytics requests.
|
||||
- Track adoption metrics and escalate blockers to BI + RevOps leadership.
|
||||
|
||||
## Workflow
|
||||
1. **Audience Mapping** – understand personas, workflows, and reporting cadences.
|
||||
2. **Enablement Design** – create training plans, cheat sheets, and automation hooks.
|
||||
3. **Insight Facilitation** – host readouts, run Q&A, and capture next steps.
|
||||
4. **Adoption Analytics** – monitor usage, NPS, and operational impact of dashboards.
|
||||
5. **Feedback Loop** – route requests to BI backlog and close the loop with stakeholders.
|
||||
|
||||
## Outputs
|
||||
- Enablement plan with session agenda, collateral, and success metrics.
|
||||
- Adoption dashboard with usage + satisfaction trends.
|
||||
- Insight/action tracker that pairs dashboards with owners + deadlines.
|
||||
|
||||
---
|
||||
28
agents/data-architecture-lead.md
Normal file
28
agents/data-architecture-lead.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
name: data-architecture-lead
|
||||
description: Owns BI data models, contracts, and governance for GTM analytics.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
|
||||
# Data Architecture Lead Agent
|
||||
|
||||
## Responsibilities
|
||||
- Define semantic layers, data contracts, and modeling standards for GTM KPIs.
|
||||
- Coordinate with engineering, analytics, and RevOps on source-of-truth tables.
|
||||
- Monitor data quality, freshness, and lineage for critical dashboards.
|
||||
- Manage documentation, change control, and auditability requirements.
|
||||
|
||||
## Workflow
|
||||
1. **Contract Design** – map business questions to source tables, metrics, and ownership.
|
||||
2. **Model Development** – build dbt/semantic layers with reusable components.
|
||||
3. **Quality Monitoring** – set up tests, alerts, and dashboards for data reliability.
|
||||
4. **Change Management** – run approvals for schema updates and communicate downstream impact.
|
||||
5. **Enablement** – publish documentation, sample queries, and onboarding guides.
|
||||
|
||||
## Outputs
|
||||
- Data contract templates with SLA + owner details.
|
||||
- Semantic model documentation + lineage diagrams.
|
||||
- Quality dashboards highlighting issues and remediation actions.
|
||||
|
||||
---
|
||||
29
agents/insights-program-director.md
Normal file
29
agents/insights-program-director.md
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
name: insights-program-director
|
||||
description: Leads BI program governance, roadmap, and stakeholder alignment.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
|
||||
|
||||
# Insights Program Director Agent
|
||||
|
||||
## Responsibilities
|
||||
- Define analytics strategy, KPI frameworks, and OKR alignment.
|
||||
- Prioritize BI roadmap, manage intake, and coordinate cross-functional execution.
|
||||
- Ensure data literacy enablement and adoption across GTM teams.
|
||||
- Publish executive-ready narratives with actions and ownership.
|
||||
|
||||
## Workflow
|
||||
1. **Intake & Prioritization** – capture business questions, size impact, and stack-rank initiatives.
|
||||
2. **Governance Cadence** – run steering committees, backlog reviews, and roadmap updates.
|
||||
3. **Delivery Oversight** – coordinate analysts, engineers, and enablement teams.
|
||||
4. **Insight Packaging** – translate dashboards into decisions, actions, and follow-ups.
|
||||
5. **Continuous Improvement** – measure adoption, capture feedback, and refine templates.
|
||||
|
||||
## Outputs
|
||||
- BI roadmap with priorities, owners, and timelines.
|
||||
- Executive insight briefs with KPIs, narratives, and action items.
|
||||
- Enablement plans to drive dashboard adoption and literacy.
|
||||
|
||||
---
|
||||
34
commands/audit-data-contracts.md
Normal file
34
commands/audit-data-contracts.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
name: audit-data-contracts
|
||||
description: Reviews BI data contracts, ownership, and quality SLAs across GTM domains.
|
||||
usage: /business-intelligence:audit-data-contracts --domains revenue,success --window 30d --format memo
|
||||
---
|
||||
|
||||
# Command: audit-data-contracts
|
||||
|
||||
## Inputs
|
||||
- **domains** – comma-separated business areas (revenue, marketing, success, product, finance).
|
||||
- **window** – lookback for incidents/changes (7d, 30d, quarter).
|
||||
- **owners** – optional list of data owners to highlight.
|
||||
- **format** – dashboard | memo | ticket-pack.
|
||||
- **severity-threshold** – warn | breach to filter issues.
|
||||
|
||||
## Workflow
|
||||
1. **Contract Inventory** – pull registered contracts with schemas, owners, SLAs.
|
||||
2. **Issue Harvest** – gather incidents, failed tests, schema changes, and backlog tickets.
|
||||
3. **Compliance Review** – compare to SLAs, governance policies, and regulatory requirements.
|
||||
4. **Recommendation Engine** – prioritize fixes, assign owners, and set timelines.
|
||||
5. **Packaging** – produce memo/dashboard plus follow-up tasks for RevOps + engineering.
|
||||
|
||||
## Outputs
|
||||
- Contract health report with SLA adherence and issue list.
|
||||
- Remediation tracker assigning owners, due dates, and status.
|
||||
- Governance summary for leadership covering risks + decisions needed.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `data-architecture-lead` – leads contract evaluation + remediation planning.
|
||||
- `insights-program-director` – escalates systemic risks and resource asks.
|
||||
- `data-contract-framework` skill – enforces documentation + SLA standards.
|
||||
- `metric-governance-kit` skill – cross-checks KPI dependencies.
|
||||
|
||||
---
|
||||
34
commands/build-exec-dashboard.md
Normal file
34
commands/build-exec-dashboard.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
name: build-exec-dashboard
|
||||
description: Generates executive KPI dashboard spec with governance hooks and adoption plan.
|
||||
usage: /business-intelligence:build-exec-dashboard --audience elt --kpis bookings,pipeline,nrr --cadence weekly --format deck
|
||||
---
|
||||
|
||||
# Command: build-exec-dashboard
|
||||
|
||||
## Inputs
|
||||
- **audience** – elt | board | revenue-leadership | marketing-lead | cs-lead.
|
||||
- **kpis** – comma-separated KPI list to emphasize.
|
||||
- **cadence** – reporting frequency (daily, weekly, monthly, quarterly).
|
||||
- **format** – deck | dashboard | memo | loom.
|
||||
- **drilldowns** – optional list of dimensions to include (segment, region, product).
|
||||
|
||||
## Workflow
|
||||
1. **Requirement Intake** – align on decisions the dashboard should drive + success metrics.
|
||||
2. **KPI Blueprint** – confirm definitions, formulas, source tables, and owners.
|
||||
3. **Layout Design** – arrange hero metrics, drill panels, and action callouts.
|
||||
4. **Governance Layer** – document refresh cadence, QA steps, and change control.
|
||||
5. **Enablement Pack** – prepare walkthrough notes, adoption plan, and automation hooks.
|
||||
|
||||
## Outputs
|
||||
- Dashboard spec with layout, queries, filters, and data sources.
|
||||
- KPI dictionary snippet for the selected metrics.
|
||||
- Enablement kit (talk track, adoption checklist, Slack/email rollout plan).
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `data-architecture-lead` – validates KPI definitions + data contracts.
|
||||
- `analytics-enablement-partner` – crafts rollout + training plan.
|
||||
- `dashboard-playbook` skill – enforces layout + storytelling best practices.
|
||||
- `executive-kpi-briefings` skill – formats exec-ready narratives.
|
||||
|
||||
---
|
||||
34
commands/plan-bi-roadmap.md
Normal file
34
commands/plan-bi-roadmap.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
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.
|
||||
|
||||
---
|
||||
81
plugin.lock.json
Normal file
81
plugin.lock.json
Normal file
@@ -0,0 +1,81 @@
|
||||
{
|
||||
"$schema": "internal://schemas/plugin.lock.v1.json",
|
||||
"pluginId": "gh:gtmagents/gtm-agents:plugins/business-intelligence",
|
||||
"normalized": {
|
||||
"repo": null,
|
||||
"ref": "refs/tags/v20251128.0",
|
||||
"commit": "9abcfd011c9935ec5b3256f9547531b703099880",
|
||||
"treeHash": "c625baa3d912b7d970308196ef4cd69b0bbb53787ceeb4f885308c21caa3c5a7",
|
||||
"generatedAt": "2025-11-28T10:17:15.665924Z",
|
||||
"toolVersion": "publish_plugins.py@0.2.0"
|
||||
},
|
||||
"origin": {
|
||||
"remote": "git@github.com:zhongweili/42plugin-data.git",
|
||||
"branch": "master",
|
||||
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
|
||||
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
|
||||
},
|
||||
"manifest": {
|
||||
"name": "business-intelligence",
|
||||
"description": "BI roadmap governance, data contracts, dashboards, and executive briefings",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
"content": {
|
||||
"files": [
|
||||
{
|
||||
"path": "README.md",
|
||||
"sha256": "fdc0107ed1b5b811491e911c0669ca5485b6d55e1a98608c6352831fbd2ddb3e"
|
||||
},
|
||||
{
|
||||
"path": "agents/data-architecture-lead.md",
|
||||
"sha256": "7e66f307d1a869020a087e096515c125389b47b205b6cb25930b2cdb7697f643"
|
||||
},
|
||||
{
|
||||
"path": "agents/insights-program-director.md",
|
||||
"sha256": "21511cf9427d506d1583fe95adfd0b398de007fd502fbf04faed215ca8b8bb9f"
|
||||
},
|
||||
{
|
||||
"path": "agents/analytics-enablement-partner.md",
|
||||
"sha256": "0b4a130293681608d7589e1723b88cb2f6ee882fc9515354847a261c436a056d"
|
||||
},
|
||||
{
|
||||
"path": ".claude-plugin/plugin.json",
|
||||
"sha256": "24d09e9edb4e05592533e3e44040c43ef2ebd1f81dcd2d8c7c30057bd03e5963"
|
||||
},
|
||||
{
|
||||
"path": "commands/audit-data-contracts.md",
|
||||
"sha256": "fc44b04484c77518f7611e4b174c992013607fde9a405d54f2c877e44c501fff"
|
||||
},
|
||||
{
|
||||
"path": "commands/plan-bi-roadmap.md",
|
||||
"sha256": "01c413bc3afd1e577bdcfa38395751cee068e223607e44950325ea0ec3e977d7"
|
||||
},
|
||||
{
|
||||
"path": "commands/build-exec-dashboard.md",
|
||||
"sha256": "d0c403a630cfc721925844bfded9712ef69f9c8aa1854fe5d5db31bddb10de6a"
|
||||
},
|
||||
{
|
||||
"path": "skills/metric-governance-kit/SKILL.md",
|
||||
"sha256": "407edba63b2fb00719aed1bbf0f98f1ec8497592b49f3f1a07ba7d635f46149e"
|
||||
},
|
||||
{
|
||||
"path": "skills/data-contract-framework/SKILL.md",
|
||||
"sha256": "365ad05e68c537f7afce6cc812f725e85e02c9096b103d08e2839e9a193beed0"
|
||||
},
|
||||
{
|
||||
"path": "skills/executive-kpi-briefings/SKILL.md",
|
||||
"sha256": "2f36560084e068c14c8f0d6395441cd34fc29ebab10e60ec23b2155950128808"
|
||||
},
|
||||
{
|
||||
"path": "skills/dashboard-playbook/SKILL.md",
|
||||
"sha256": "378e85ebaf4229ea9bfd379ad15deb7934ffd1f35efc200276cb0f31d71ff8b7"
|
||||
}
|
||||
],
|
||||
"dirSha256": "c625baa3d912b7d970308196ef4cd69b0bbb53787ceeb4f885308c21caa3c5a7"
|
||||
},
|
||||
"security": {
|
||||
"scannedAt": null,
|
||||
"scannerVersion": null,
|
||||
"flags": []
|
||||
}
|
||||
}
|
||||
30
skills/dashboard-playbook/SKILL.md
Normal file
30
skills/dashboard-playbook/SKILL.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: dashboard-playbook
|
||||
description: Best-practice kit for BI dashboard layout, storytelling, and adoption.
|
||||
---
|
||||
|
||||
# Dashboard Playbook Skill
|
||||
|
||||
## When to Use
|
||||
- Designing new dashboards or refreshing existing ones for GTM stakeholders.
|
||||
- Auditing dashboards that suffer from low engagement or unclear narratives.
|
||||
- Training analysts on consistent storytelling and UX patterns.
|
||||
|
||||
## Framework
|
||||
1. **Audience & Decisions** – document persona, cadence, and key decisions.
|
||||
2. **Story Arc** – headline metric, supporting evidence, drill-downs, and action prompts.
|
||||
3. **Layout System** – hero tiles, contextual panels, alerts, and annotation space.
|
||||
4. **Governance Hooks** – data freshness indicator, owner info, and SLA links.
|
||||
5. **Adoption Loop** – training plans, feedback capture, and iteration cadence.
|
||||
|
||||
## Templates
|
||||
- **Wireframe Template**: See `templates/dashboard_wireframe.md` for layout structure.
|
||||
- **Dashboard brief** (goals, KPIs, filters, mockups).
|
||||
- **Adoption checklist** (enablement, comms, success metrics).
|
||||
|
||||
## Tips
|
||||
- Limit hero metrics to 3–5; move detailed tables into drill sections.
|
||||
- Use consistent color semantics for good vs risk states.
|
||||
- Pair with `build-exec-dashboard` to package specs + rollout plan.
|
||||
|
||||
---
|
||||
30
skills/data-contract-framework/SKILL.md
Normal file
30
skills/data-contract-framework/SKILL.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: data-contract-framework
|
||||
description: Operating model for defining, enforcing, and auditing BI data contracts.
|
||||
---
|
||||
|
||||
# Data Contract Framework Skill
|
||||
|
||||
## When to Use
|
||||
- Establishing ownership and SLAs for mission-critical BI tables.
|
||||
- Coordinating schema changes between engineering, analytics, and RevOps.
|
||||
- Auditing data reliability before major launches or executive reporting cycles.
|
||||
|
||||
## Framework
|
||||
1. **Contract Scope** – table/view name, business purpose, consumer list.
|
||||
2. **Owner Matrix** – technical owner, business owner, escalation contacts.
|
||||
3. **SLA Definition** – refresh cadence, acceptable latency, data quality thresholds.
|
||||
4. **Change Workflow** – approval steps, testing requirements, communication plan.
|
||||
5. **Compliance & Audit** – logging, version history, and retention requirements.
|
||||
|
||||
## Templates
|
||||
- Data contract one-pager (scope, owners, SLAs, dependencies).
|
||||
- Change request form with impact assessment.
|
||||
- Audit checklist for quarterly reviews.
|
||||
|
||||
## Tips
|
||||
- Keep contracts lightweight but enforceable—link to dbt/docs for deeper detail.
|
||||
- Automate SLA checks via dashboards and alerting.
|
||||
- Pair with `audit-data-contracts` to prioritize fixes and highlight risk.
|
||||
|
||||
---
|
||||
30
skills/executive-kpi-briefings/SKILL.md
Normal file
30
skills/executive-kpi-briefings/SKILL.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: executive-kpi-briefings
|
||||
description: Template pack for summarizing BI insights for ELT/board stakeholders.
|
||||
---
|
||||
|
||||
# Executive KPI Briefings Skill
|
||||
|
||||
## When to Use
|
||||
- Preparing weekly/monthly ELT updates with BI insights.
|
||||
- Translating dashboards into succinct decision memos.
|
||||
- Coordinating follow-up actions after KPI reviews.
|
||||
|
||||
## Framework
|
||||
1. **Headline & Signal** – lead with KPI delta, direction, and confidence.
|
||||
2. **Driver Analysis** – highlight top drivers, segments, or anomalies.
|
||||
3. **Implications** – spell out impact on goals, customers, or investments.
|
||||
4. **Actions & Owners** – list next steps, DRIs, due dates, and guardrails.
|
||||
5. **Appendix** – link to dashboard tabs, methodology, and deeper data.
|
||||
|
||||
## Templates
|
||||
- 1-page KPI memo (headline, context, actions).
|
||||
- Slide template for ELT/board readouts.
|
||||
- Follow-up tracker with ownership + status fields.
|
||||
|
||||
## Tips
|
||||
- Keep narratives under 200 words unless deeper context is requested.
|
||||
- Pair with `build-exec-dashboard` and `plan-bi-roadmap` for consistent storytelling.
|
||||
- Capture questions/decisions in a log to feed future prioritization.
|
||||
|
||||
---
|
||||
31
skills/metric-governance-kit/SKILL.md
Normal file
31
skills/metric-governance-kit/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: metric-governance-kit
|
||||
description: Framework for defining, approving, and auditing GTM metrics and KPIs.
|
||||
---
|
||||
|
||||
# Metric Governance Kit Skill
|
||||
|
||||
## When to Use
|
||||
- Establishing source-of-truth KPIs for revenue, marketing, or CS teams.
|
||||
- Resolving conflicting definitions or reporting anomalies.
|
||||
- Preparing for exec/board reviews where metric accuracy is scrutinized.
|
||||
|
||||
## Framework
|
||||
1. **Metric Charter** – purpose, formula, filters, owner, review cadence.
|
||||
2. **Data Lineage** – upstream sources, transformations, semantic layer, downstream dashboards.
|
||||
3. **Quality Controls** – tests, alerts, thresholds, backup calculations.
|
||||
4. **Change Management** – approval workflow, communication plan, version history.
|
||||
5. **Adoption Enablement** – cheat sheets, FAQs, and example analyses.
|
||||
|
||||
## Templates
|
||||
- **Metric Dictionary**: See `references/metric_dictionary_template.md` for standard definition format.
|
||||
- **Metric charter one-pager**.
|
||||
- **Lineage diagram checklist**.
|
||||
- **Change log workbook** with approvals + timestamps.
|
||||
|
||||
## Tips
|
||||
- Assign both business and technical owners for each KPI.
|
||||
- Tag metrics with “tier” (executive, operational, exploratory) to prioritize rigor.
|
||||
- Pair with `plan-bi-roadmap` to keep initiatives tied to governed metrics.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user