This skill should be used when predicting what support emails, refund requests, app reviews, bug reports, and confused user complaints a product launch or feature change will generate. It is especially useful for launch readiness, onboarding review, diagnosing support burden, and finding the gaps between what builders think is obvious and what users will actually report.
Use this skill to simulate the messy human exhaust of a launch: vague bug reports, annoyed reviews, refund requests, and exhausted follow-up threads.
This skill is for answering:
Use this skill when reviewing:
A support burden is not just the number of issues. It is:
Read enough context to understand:
Then list:
Generate a realistic mix of artifacts:
Make them feel real:
For each simulated item, add:
Identify the issues that are worst because they are:
Use this format:
# Support Inbox Simulation: [Product / Feature]
## Executive Read
- Most likely support subject line:
- Most expensive recurring ticket:
- Most likely refund reason:
- Public review story most likely to spread:
## Simulated Inbox
### Support Emails
#### 1. Subject: ...
[message]
**What really happened:**
**Missing facts:**
**Estimated support rounds:**
**Best fix type:**
### Public Reviews
#### 1. ★★☆☆☆ “...”
[review]
**Underlying issue:**
**What story this reinforces:**
### Refund / Cancellation Notes
...
## Support Sinkholes
- [Issue] — why it will eat time
- [Issue] — why diagnostics fail
## Highest-Leverage Support Fixes
1. [ ]
2. [ ]
3. [ ]
## Support Summary / Diagnostics Missing Today
- [missing field]
- [missing field]
- [missing field]
The simulation is successful when it makes support feel painfully concrete and identifies: