Prompt Details
Model
(claude-5-sonnet)
Token size
4,355
Example input
[WORK_ITEMS_AND_BUSINESS_SIGNALS]: Incident INC-104: Checkout API latency increased from normal levels to repeated p95 spikes during peak usage. Three customer-support tickets reference slow checkout. An engineering workshop note says database connections may be saturating, but no query-plan evidence has been collected. Incident INC-108: Password-reset emails are occasionally delayed by 10–20 minutes. Support received six complaints this month. Request REQ-77: Sales asked for a new reporting filter before the next enterprise demo. Email from Head of Customer Success: “Checkout reliability is becoming a recurring customer conversation and we need clarity before the next renewal cycle.” Workshop note: Several engineers suspect connection-pool pressure may also affect order-processing jobs. [DOMAIN_RISK_FOCUS]: Application Layer, Database, Integration Layer
Example output
Note: this input set has fewer than 12 items, so it runs at full depth with no consolidation pass. ## 1. EXECUTIVE FIX PRIORITY SUMMARY Four work items were supplied: two incidents (checkout latency, delayed password-reset emails), one feature request (reporting filter), and one supporting workshop note plus one customer-success email, both of which attach to the checkout incident rather than standing alone. The evidence points to a possible shared root cause — database connection-pool saturation — linking checkout latency (INC-104) to a suspected but unconfirmed effect on order-processing jobs. This is the highest-leverage thread to investigate, but it is currently **PLAUSIBLE, not CONFIRMED**: no query-plan or connection-pool metrics were supplied. INC-108 (password-reset delay) shows a different, unrelated impact pattern (email delivery timing, not API latency) and no evidence ties it to the same mechanism. REQ-77 is a feature request with a business deadline, not a defect, and is sequenced separately.
Reviews
There are no reviews yet.