domains / families / devops / risky-changes

risky-changes

separate

Verify assumptions before implementing large or risky changes to APIs, provider data, billing, pricing, quotas, or defaults. Use when a mistake could affect customers or the user asks if a change is safe to ship. Checks real-world impact beyond passing tests.

When to use

• Public API fields, filters, or response shaping
• Dropping, transforming, or reordering upstream data
• Billing, pricing, caps, or quotas
• Defaults, thresholds, or provider request parameters
• Unverified assumptions about external data or user behavior
• Changes where being wrong is expensive or customer-visible

When not to use

• Changes where mistakes are not expensive or customer-visible

Skill page

Source