Autonomous SaaS Failed-Payment Dunning & Churn Recovery Skill

Detect `invoice.payment_failed` events, classify decline codes (soft vs hard declines), generate hosted card-update links, and stage personalized recovery

---
name: stripe-dunning-recovery
description: Detect `invoice.payment_failed` events, classify decline codes (soft vs hard declines), generate hosted card-update links, and stage personalized recovery outreach. Use when working with Stripe Billing, Churn Recovery, Payment Links, Gmail/Slack.
triggers:
  - stripe dunning recovery
  - stripe billing
  - churn recovery
---

# Autonomous SaaS Failed-Payment Dunning & Churn Recovery Skill

## 1. When to Use This Skill
Load `skill-stripe-dunning-recovery` whenever an engineering or operations task involves **Stripe Billing, Churn Recovery, Payment Links, Gmail/Slack**. Specifically:
- Detect `invoice.payment_failed` events, classify decline codes (soft vs hard declines), generate hosted card-update links, and stage personalized recovery outreach.
- Designing, reviewing, or debugging production configurations without guesswork or deprecated flags.
- Running deterministic pre-flight and post-execution verification checks before reporting completion.

## 2. Prerequisites & Required Environment
- **Target Stack:** Stripe Billing, Churn Recovery, Payment Links, Gmail/Slack
- **Permissions:** Read-only inspection by default; ask for explicit confirmation before executing destructive mutations or production deployments.
- **Reference Repository:** `https://github.com/stripe/agent-toolkit`

## 3. Step-by-Step Execution Playbook
1. **Context & Configuration Discovery:**
   Inspect existing project manifests (`package.json`, `wrangler.jsonc`, schema files, or environment declarations) before proposing changes. Never overwrite existing bindings or credentials blindly.
2. **Deterministic Implementation:**
   Apply the canonical patterns for **Stripe Billing**:
   - Enforce strict schema/type validation at every external boundary.
   - Include explicit error handling, structured logging, and idempotency keys on all mutating calls.
   - Keep secrets in environment variables or secret stores—never hardcode tokens in source files.
3. **Verification & Regression Gate:**
   Run the verification commands below and inspect both exit codes and output payloads before marking the task complete.

## 4. Reference Commands & CLI Workflow
```bash
stripe events list --type=invoice.payment_failed
stripe billing_portal sessions create
```

## 5. Edge Cases & Anti-Hallucination Guardrails
- **Zero Unverified Claims:** Never claim a deployment, migration, or API call succeeded without inspecting the command output or HTTP status code.
- **Rollback Readiness:** Always record the previous state or migration version so changes can be reverted cleanly if downstream health checks fail.

Synthesized Engineering Blueprint & Setup Guide