SkillVaultskills Browse all 500 skills

Architecture · Version 1.1.0 · Reviewed 2026-08-02

Webhook Delivery Designer

Make a defensible decision about signature design and retry and backoff with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Designs outbound webhook delivery with signing, retries, ordering guarantees, and consumer-visible failure handling.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Signature design
  • Retry and backoff
  • Replay and ordering

How Webhook Delivery Designer works

You provide

Requirements, constraints, and the current topology

It inspects

Critical path and failure boundaries for signature design

It decides

A retry and backoff decision with consequences recorded

You verify

Rollout stages with the signal that gates each one

What it checks first

Webhook Delivery Designer designs outbound webhook delivery with signing, retries, ordering guarantees, and consumer-visible failure handling. Use it when the work involves Signature design, Retry and backoff, Replay and ordering.

  1. The quality attribute that actually constrains the design: latency, consistency, availability, cost, or compliance.
  2. The critical path and the number of network hops on it.
  3. Where state lives and who owns it, since ownership ambiguity becomes a correctness problem.
  4. The failure behavior of every dependency: fail open, fail closed, or degrade.

Failure modes it recognizes

  • Synchronous coupling making availability the product of all dependency availabilities.
  • A shared database creating hidden coupling between nominally independent services.
  • A component with no clear owner, so its failure has no defined response.
  • Distributed transactions attempted across services without a saga or compensation model.

Answers it will reject

  • Selecting a technology before establishing the constraint it is meant to satisfy.
  • Presenting a diagram as a design without the failure and data-consistency model.
  • Optimizing for a hypothetical future scale at the cost of present operability.

Decision rules it applies

  • Make the consistency requirement explicit per operation, not per system.
  • Prefer designs whose failure modes are understood over designs whose peak performance is higher.
  • Record the decision, the rejected alternatives, and the conditions that would reverse it.

Evidence it asks for

  • Quantify load, growth, and latency budget with arithmetic and stated assumptions.
  • Define the rollout stages and the signal that gates each one.
  • Name the reversal path for the decision.

The method inside

  1. Turn signature design into explicit functional requirements and quality-attribute constraints.
  2. Model the critical path, state, trust, and failure boundaries that govern retry and backoff.
  3. Compare viable designs for replay and ordering against weighted constraints and operational ownership.
  4. Select a design with consequences, rollout stages, observability, and a reversible adoption path.

Deliverables

  • Signature design assessment
  • Retry and backoff decision and action plan
  • Replay and ordering verification checklist

Evidence requirements

  • Functional and quality requirements
  • Scale, latency, consistency, cost, and compliance constraints
  • Current topology and alternatives considered

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Design our outbound webhooks so partners can trust them and we do not melt when a partner endpoint goes down.

Expected output

Sign the raw body with a timestamped HMAC so partners can reject replays, and treat each subscriber as an independent queue so one slow partner cannot delay the rest. Deliver at-least-once with an event ID, and publish the retry schedule so partners can reason about duplicates...

Boundaries and compatibility

Ideal for

  • Signature design: produce a decision or artifact grounded in supplied evidence.
  • Retry and backoff: produce a decision or artifact grounded in supplied evidence.
  • Replay and ordering: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Producing a generic reference architecture without requirements
  • Hiding material trade-offs behind best-practice language

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.