Skip to main content

u02267-retry-and-backoff-orchestration-for-sales-and-client-success

Build and operate the "Retry And Backoff Orchestration for sales and client success" capability for sales and client success. Use when this exact capability is required by autonomous or human-guided missions.

Jump to install

Source facts

Repository
zwright8/OpenClaw-Code
Last source activity
June 18, 2026 at 22:48
Detected SKILL.md language
English
Stars
0
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
u02267-retry-and-backoff-orchestration-for-sales-and-client-success
description
Build and operate the "Retry And Backoff Orchestration for sales and client success" capability for sales and client success. Use when this exact capability is required by autonomous or human-guided missions.
# Retry And Backoff Orchestration for sales and client success ## Why This Skill Exists Use retry and backoff orchestration in sales and client success with emphasis on safety, dignity, equity, and long-term societal benefit. ## When To Use Use this skill when the request explicitly needs "Retry And Backoff Orchestration for sales and client success" outcomes in the sales and client success domain. ## Step-by-Step Implementation Guide 1. Define measurable outcomes for Retry And Backoff Orchestration for sales and client success, including baseline and target metrics for sales and client success. 2. Specify structured inputs/outputs for retry and backoff orchestration and validate schema contract edge cases. 3. Implement the core retry and backoff orchestration logic with deterministic scoring and reproducible execution traces. 4. Integrate orchestration policy, routing, approval gates, retries, and rollback for autonomous execution. 5. Run unit, integration, simulation, and regression suites for Retry And Backoff Orchestration for sales and client success under pro-humanity impact conditions. 6. Roll out behind a feature flag, monitor telemetry, and refine thresholds using observed operational outcomes. ## Required Deliverables - Capability contract: input schema, deterministic scoring, output schema, and failure modes. - Runtime profile: generalist-engine using retry and backoff orchestration to produce retry-and-backoff-orchestration-artifact-sales-and-client-succes. - Orchestration integration: sales-and-client-success:generalist-engine routing, approval gates, retries, and rollback controls. - Validation evidence: unit, integration, simulation, regression-baseline suites and rollout telemetry. ## Operational Runbook ### Preflight - Validate mission scope, contracts, and required inputs. - Verify feature flag posture, dependencies, and approval prerequisites. ### Execution - Execute retry and backoff orchestration workflow with deterministic scoring and trace capture. - Track posture transitions and preserve reproducible evidence artifacts. ### Recovery - Apply rollback strategy if posture is critical or guardrails fail. - Escalate blocked execution to oversight with incident packet and trace references. ### Handoff - Publish outcome report, scorecard, and telemetry links. - Queue follow-up tasks for unresolved risks, approvals, or optimization work. ## Guardrails - [quality] Require unit and integration validations before promoting Retry And Backoff Orchestration for sales and client success. -> `run-validation:unit+integration+simulation+regression-baseline` - [reliability] Trigger rollback on critical posture or repeated failures. -> `rollback:rollback-to-last-stable-baseline` - [cost] Respect bounded resource pressure and execution budget during scaling. -> `budget-guard:resource-pressure-cap`
View on GitHub