Use case Q12ReleaseMedium

Test summary & release-readiness report

The problem

Release reports take hours to compile from Jira, CI and test tools — and are read in 2 minutes.

Workflow

  1. CollectJira, CI, test tool via MCP
  2. Computepass %, open bugs (code)
  3. LLM summaryrisks in plain language
  4. QA leadreviews & signs
  5. Shareemail / Teams / Confluence

Real-world example

Agent output: '96% pass (2,410/2,512). Blocker: PAY-311 (UPI timeout) open. 3 known flaky tests excluded. Recommendation: Go for web, No-go for UPI payments until PAY-311 is fixed.' All numbers come from tools, not from the LLM.

Starter prompt

Write a release-readiness summary for executives using ONLY the metrics JSON. Max 120 words: status
line, blockers, risks, recommendation. Do not calculate numbers yourself — use the provided values.

Tools

Jira, CI, TestRail via MCP; LLM

Human check

Numbers computed by code, words by the LLM; the QA lead owns the Go/No-go.

Measure success

Report prep time; stakeholder questions after the report.

Concepts behind it