1. Test Plan Writer
Copy-paste prompt
You are a senior QA engineer. Write a comprehensive test plan for [FEATURE/RELEASE NAME] on [PRODUCT]. Include: test objectives and scope, in-scope and out-of-scope items, test types (functional, regression, performance, security), test environment requirements, entry and exit criteria, test schedule, resource requirements, and risk assessment with mitigation strategies. Format: formal QA test plan document.
2. Bug Report Writer
Copy-paste prompt
You are a QA engineer filing a formal bug report. Write a detailed bug report for the following issue: [DESCRIBE THE BUG, e.g. 'Checkout fails when applying a discount code on mobile Safari']. Include: bug title, severity (Critical/High/Medium/Low), environment (browser, OS, app version), steps to reproduce (numbered), expected behavior, actual behavior, screenshots/logs placeholder, workaround if known, and suggested assignee team. Format: structured bug report.
3. Release Readiness Checklist Generator
Copy-paste prompt
You are a QA lead preparing for a production release. Generate a release readiness checklist for [PRODUCT NAME] version [VERSION]. Cover: code freeze confirmation, all P0/P1 bugs resolved, regression suite pass rate (threshold: [X]%), performance benchmarks met, security scan completed, documentation updated, rollback plan confirmed, stakeholder sign-offs required, and go/no-go decision criteria. Format: checkbox list by category.
Nexus Vault
Need more than the free prompts?
Get 200 business prompts, instant download, and no subscription.
4. Regression Test Suite Summary Writer
Copy-paste prompt
Write a regression test suite execution summary for [PRODUCT/FEATURE] after the [SPRINT/RELEASE] cycle. Include: total test cases run, pass/fail/blocked counts, pass rate percentage, critical failures and their impact, flaky tests identified, coverage gaps, and recommendation (ship / hold / ship with known issues). Audience: engineering manager and product owner.
5. QA Retrospective Writer
Copy-paste prompt
You are a QA lead facilitating a post-release retrospective. Write a QA retrospective report for the [RELEASE NAME] release. Include: what went well in the QA process, what didn't go well (escaped bugs, missed coverage, timeline issues), root cause analysis for any production incidents, action items with owners, process improvements for next release, and metrics comparison to previous release. Tone: constructive and forward-looking.