Prompt Details
Model
Chat - (gpt-5.4)
Token size
602
Example input
[RAW_BUG_REPORT]: A customer says the checkout total got weird after they added a coupon and switched from monthly to annual. They are not sure if they were actually charged wrong, but the numbers looked off.
[OBSERVED_BEHAVIOR]: Coupon can be entered. Plan toggle exists. User reports confusion after switching plans. No confirmed charged amount issue yet.
[EXPECTED_BEHAVIOR_OR_UNKNOWN]: Expected behavior is that pricing should remain correct and understandable after switching plans. Unknown whether coupon should persist or reset.
[ENVIRONMENT_AND_CONTEXT]: Self-serve SaaS checkout flow. No confirmed browser or device yet. This was raised close to release review.
[CONSTRAINTS_AND_LIMITS]: Do not invent billing provider behavior. Do not assume payment impact unless confirmed. Keep the output useful for product, QA, support, and engineering.
Example output
1) Triage snapshot
- What seems to be happening: A user applies a coupon during checkout, changes the billing plan, and the final total may stop matching the visible discount state
- Confidence that this is a real bug: Medium
- Main uncertainty: It is unclear whether the issue is visual only or affects the charged total
- Most likely affected flow: Checkout plan-switch + coupon state handling
- Recommended next move: Reproduce the billing-toggle sequence before escalating severity
Instant access
Commercial use
Money‑backBy purchasing this prompt, you agree to our terms of service
4
Views
GPT-5.4
Turn vague bug reports into clear, engineer-ready tickets with reproducible steps, expected vs actual behavior, missing context, likely blockers, and a cleaner handoff for product, QA, and engineering teams. Great for support logs, internal QA notes, customer bug submissions, and messy issue tracker drafts.
...more
Updated 4 weeks ago
