Use when the user asks to "configure dashboards", "set up data feeds", "design monitoring tools", "automate dashboard updates", or "integrate PM data sources". Activates when a stakeholder needs to configure PM dashboard tooling, set up automated data feeds from PM tools, design visualization components, configure alert thresholds, or establish dashboard refresh cadence and access control.
TL;DR: Configures project management dashboard tooling including data feed setup, visualization component selection, refresh cadence, and alert configuration. Ensures dashboards are automatically updated with live project data rather than requiring manual input.
Un dashboard que requiere actualización manual no es un dashboard — es una presentación recurrente. La automatización de data feeds es lo que transforma reportes en monitoreo en tiempo real. El valor del dashboard es inversamente proporcional al esfuerzo de mantenerlo actualizado.
executive-dashboard or similar# Configure data feeds for project dashboard
/pm:dashboard-tooling $PROJECT --type=feeds --sources="jira,ado"
# Set up alert rules for project metrics
/pm:dashboard-tooling $PROJECT --type=alerts --metrics="cpi,spi,velocity"
# Configure dashboard refresh cadence
/pm:dashboard-tooling $PROJECT --type=refresh --cadence="hourly"
Parameters:
| Parameter | Required | Description |
|---|---|---|
$PROJECT | Yes | Project identifier |
--type | Yes | feeds, alerts, refresh, access-control, maintenance |
--sources | No | Data sources (jira, ado, monday, sheets) |
--metrics | No | Metrics for alert configuration |
--cadence | No | Refresh frequency (real-time, hourly, daily) |
{TIPO_PROYECTO}: All project types need dashboard tooling. Agile uses velocity and burndown widgets; Waterfall uses EVM and milestone widgets; Portfolio uses heatmap and aggregate views.
skills/dashboard-tooling/references/*.md for data feed configuration patternsGood Dashboard Tooling:
| Attribute | Value |
|---|---|
| Data feeds configured | All metrics from automated sources |
| Refresh cadence | Configured per metric type (hourly/daily) |
| Alert rules | Tiered with calibrated thresholds |
| Access control | Role-based with 3 permission levels |
| Testing | Data accuracy verified against source |
| Maintenance plan | Documented with ownership |
Bad Dashboard Tooling: A dashboard that requires someone to manually copy data from Jira into a spreadsheet every Friday. No automated feeds, no alerts, no refresh cadence. Fails because manual dashboards are always stale, error-prone, and abandoned within weeks when the person responsible gets busy.
| Resource | When to read | Location |
|---|---|---|
| Body of Knowledge | Before configuring to understand data integration patterns | references/body-of-knowledge.md |
| State of the Art | When evaluating dashboard platforms | references/state-of-the-art.md |
| Knowledge Graph | To link tooling to dashboard design and metrics | references/knowledge-graph.mmd |
| Use Case Prompts | When scoping tooling requirements | prompts/use-case-prompts.md |
| Metaprompts | To generate data feed configuration templates | prompts/metaprompts.md |
| Sample Output | To calibrate expected tooling documentation | examples/sample-output.md |
Designs data source connections for dashboard feeds. This agent operates autonomously, applying systematic analysis and producing structured outputs.
Plans automated dashboard refresh and distribution. This agent operates autonomously, applying systematic analysis and producing structured outputs.
Evaluates dashboard tools against project requirements. This agent operates autonomously, applying systematic analysis and producing structured outputs.
Designs dashboard visualizations for different audiences. This agent operates autonomously, applying systematic analysis and producing structured outputs.