Derives human-readable manual test cases from a business-rule spec via a decision table: identify conditions and actions, build the full 2^n-column matrix, collapse columns with irrelevant entries, strike infeasible combinations, then emit one test case per remaining column (each feasible column is one coverage item per ISTQB CTFL v4.0 section 4.2.3). A deep single-technique walkthrough rather than a broad multi-lens case matrix; the output is manual step/expected cases rather than parameterized test code, and it covers how cases are derived rather than how a case record is structured. Use when a spec's outcome depends on interacting conditions (pricing, eligibility, discounts, routing rules) rather than the boundaries of a single input.
93
93%
Does it follow best practices?
Impact
94%
1.02xAverage score across 10 eval scenarios
Passed
No findings from the security scan
The refund policy note below is what support reads off when a customer cancels, and it is also what the billing service was built from. Twice this month a support agent promised money back to a card and finance issued account credit instead, which the customer then complained about publicly.
Reading it again, the note describes several different things that can happen to a cancelling customer, and they are not all refunds - one of them is not a payment at all. Support has been treating anything that is not money back as "no refund", which is how we got here.
Three things about a cancellation seem to matter: how long ago the customer bought, which plan they are on, and how much compute they burned since buying. I want every combination of those written down with what the customer should actually get, so support can be retrained off one page and QA can check the billing service against the same page.
Produce refund-rules-analysis.md containing:
Out of scope: the refund timing (finance runs refunds on Fridays), tax treatment, and any code change.
Extract the following files before beginning.
=============== FILE: docs/refund-policy-note.md ===============
A cancellation made within 14 days of purchase is refunded in full.
An annual plan cancelled after 14 days is refunded pro rata for the whole months remaining.
A monthly plan cancelled after 14 days is not refunded. The subscription keeps running until the end of the paid period and then stops.
Where the customer has used more than 10 hours of compute since purchase, the list value of that usage is deducted and the balance is issued as account credit rather than returned to the card.
Support should not promise a date. Finance runs refunds on Fridays.
Account credit does not expire and can be spent on any plan, but it cannot be withdrawn.