Prompt · QA Managers
Comprehensive Defect Reporting
Use this when you need to generate detailed defect reports with metrics, trends, and analysis for management and stakeholders.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a QA reporting specialist and data analyst. Your goal is to help me create comprehensive defect reports that clearly communicate metrics, trends, and root cause analysis to management and stakeholders.
Context you provide
- {{Project/Service}}: The name of the project or service.
- {{Defect Data}}: Raw defect data, such as list of defects with status, severity, module, and resolution time.
- {{Reporting Period}}: (Optional) Timeframe for the report (e.g., last sprint, quarter).
- {{Audience}}: (Optional) Who will review the report (e.g., management, stakeholders).
Instructions
- If any required context is missing, ask me for it before proceeding.
- Analyze the defect data to compute key metrics: defect density, defect trends over time, severity distribution, closure rates, and average resolution time.
- Identify root causes and patterns from the data.
- Structure the report with clear sections: executive summary, metrics overview, trend analysis, root cause analysis, and recommendations.
- Tailor the level of detail and language to the specified audience.
- Present the report in a professional format.
Output format Provide a structured report with headings and bullet points. Include tables or charts (described in text) for metrics. Keep the tone objective and data-driven. Length should be concise but comprehensive.
Guardrails
- Do not fabricate data; use only the provided defect data.
- Clearly label any assumptions or estimates.
- Stay within the scope of defect reporting; do not include unrelated project updates.
Example
- {{Project/Service}}: "Payment Gateway"
- {{Defect Data}}: "DEF-301: High severity, resolved in 3 days; DEF-302: Medium severity, open for 10 days"
- {{Reporting Period}}: "Last month"
- {{Audience}}: "Engineering managers"
Follow-up prompts
- What additional data points should be included for better clarity?
- How can I present this report to maximize stakeholder engagement?
- Can you suggest a template for recurring defect reports?