zwright8 Comms KPI Dashboard Publisher
Why This Skill Exists
We need this skill because complex systems require explanations humans can act on quickly. This specific skill keeps mission status observable in real time.
When To Use
Use this skill when the request explicitly needs "Comms KPI Dashboard Publisher" outcomes in the Communication and Explainability domain.
Step-by-Step Implementation Guide
- Define the scope and success metrics for
Comms KPI Dashboard Publisher, including at least three measurable KPIs tied to misinterpretation and trust erosion. - Design and version the input/output contract for decision factors, uncertainty markers, and audience summaries, then add schema validation and failure-mode handling.
- Implement the core capability using metric synthesis and publication, and produce operator KPI dashboards with deterministic scoring.
- Integrate the skill into swarm orchestration: task routing, approval gates, retry strategy, and rollback controls.
- Add unit, integration, and simulation tests that explicitly cover misinterpretation and trust erosion, then run regression baselines.
- Deploy behind a feature flag, monitor telemetry/alerts for two release cycles, and iterate thresholds based on observed outcomes.
Required Deliverables
- Capability contract: input schema, deterministic scoring, output schema, and failure modes.
- Runtime profile: communication-engine using metric synthesis and publication to produce operator KPI dashboards.
- Orchestration integration: communication-and-explainability:communication-engine routing, approval gates, retries, and rollback controls.
- Validation evidence: unit, integration, simulation, regression-baseline suites and rollout telemetry.
Operational Runbook
Preflight
- Confirm the Comms KPI Dashboard Publisher request scope, source evidence, and measurable success criteria before execution.
- Verify feature flag skill_0756_comms-kpi-dashboard-publisher, approval gates, and rollback owner before autonomous use.
Execution
- Execute metric synthesis and publication with deterministic scoring and reproducible trace capture.
- Produce operator KPI dashboards plus scorecard, assumptions, and unresolved-risk notes.
Recovery
- Fail closed when required signals, evidence, or approval gates are missing.
- Rollback to the last stable baseline when posture is critical or validation fails.
Handoff
- Publish operator KPI dashboards, validation evidence, and telemetry links to downstream owners.
- Queue follow-up tasks for unresolved risks, threshold tuning, or approval review.
Guardrails
- [quality] Require deterministic scoring and validation evidence before promotion.
- [reliability] Preserve retries, rollback controls, and failure-mode evidence for every run.
- [safety] Route critical posture or missing approval gates to human review before autonomous action.