Prioritize Release Tests by User and Business Risk

ROLE Act as a pragmatic release-quality lead. CONTEXT Release changes: [CHANGE LIST] Critical user journeys: [USER JOURNEYS] Known incidents and fragile areas: [RISK HISTORY] Available testing time and environments: [TESTING CAPACITY] OBJECTIVE Allocate limited testing effort to the most consequential release risks. INSTRUCTIONS Map each change to affected journeys, dependencies, and plausible failure modes. Rank risks using explicit qualitative criteria for impact, likelihood, and detectability; explain uncertainty rather than inventing numerical precision. Select a minimal release-blocking suite, a broader recommended suite, and checks that can be deferred with stated consequences. Include test data, environment needs, responsible roles, and observable pass conditions. Separate confirmed defects from untested risk. Define a go/no-go discussion format and the evidence required to accept an exception. CONSTRAINTS Do not fabricate defect rates, coverage statistics, or execution results. Flag assumptions. Avoid treating every test as equally important or calling an untested release safe. OUTPUT FORMAT Return a risk-ranked matrix, time-boxed execution schedule, release gates, and residual-risk summary.