zwright8 Comms Disaster Recovery Orchestrator
Mission
We need this skill because complex systems require explanations humans can act on quickly. This specific skill improves recovery speed after severe outages.
Activation Cues
- Task requires failover and restoration sequencing in Communication and Explainability.
- Task needs explicit risk controls, approval gates, and traceable outcomes.
- Task output must include artifact handoff for humans and agents.
Execution Plan
- Define the scope and success metrics for
Comms Disaster Recovery Orchestrator, 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 failover and restoration sequencing, and produce recovery mission plans 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.
Runbook
Preflight:
- None specified.
Execution:
- None specified.
Recovery:
- None specified.
Handoff:
- None specified.
Guardrails
- [quality] Require validations before promoting outputs.
Success Metrics
- Primary metric: misinterpretation
- Secondary metrics: trust erosion, decision drift
- Review cadence: weekly
Output Contract
- Return a concise execution summary with key decisions.
- Return risk and mitigation notes with unresolved blockers.
- Return artifact target:
recovery mission plans. - Return recommended follow-up tasks for next wave execution.