Requirements to QA coverage

AI prompts: Test planning

Prompts that turn feature descriptions, user stories, and messy requirements into structured QA plans and test cases.

Data security: Use these prompts with your coding agent or QA workflow. Avoid pasting secrets, credentials, or sensitive customer data into tools you do not control.

Generate a QA test plan from a feature description

Use this when you have a new feature, ticket, or product requirement and want a structured QA plan.

You are a senior QA engineer.
Create a complete QA test plan for the following feature:
[PASTE FEATURE DESCRIPTION]

Include:
1. Main user flows
2. Positive test cases
3. Negative test cases
4. Edge cases
5. Data validation checks
6. Permission and role-based checks
7. Cross-browser or device considerations
8. Regression risks
9. Suggested automated tests
10. Suggested manual exploratory tests

Return the result as a structured QA checklist.

Convert a user story into test cases

Use this to transform a Jira, Linear, or GitHub issue into concrete test cases.

You are a QA engineer.
Convert the following user story into test cases:

User story:
[PASTE USER STORY]

Acceptance criteria:
[PASTE ACCEPTANCE CRITERIA]

For each test case, include:
- Test case title
- Preconditions
- Test steps
- Expected result
- Priority: High / Medium / Low
- Type: Functional / Regression / Edge case / Negative

Also identify any missing or unclear acceptance criteria.

Create test data for a feature

Use this when QA needs realistic data sets for positive, negative, boundary, and role-based testing.

You are a QA engineer.
Create test data for this feature:
[DESCRIBE FEATURE]

Generate data for:
- Valid users
- Invalid users
- Boundary cases
- Empty states
- Long values
- Special characters
- Different roles
- Different account states
- Different subscription plans
- Expired or archived records

Return the data in a table with explanation of what each data set is testing.

Create a bug prevention checklist for developers

Use this before implementation starts so developers can spot likely bugs early.

You are a QA engineer helping developers prevent bugs before implementation.

Feature:
[DESCRIBE FEATURE]

Create a bug prevention checklist for the developer.

Include:
- Ambiguous requirements
- Validation rules
- Error handling
- Loading states
- Empty states
- Permissions
- Data migration risks
- API failure handling
- Frontend/backend contract risks
- Analytics or monitoring needs
- Test cases the developer should cover before QA

Return a concise checklist.

Prioritize which tests to automate first

Use this when the team has too many manual tests and needs a rational automation order.

You are a QA automation strategist.
Analyze this list of manual test cases:
[PASTE TEST CASES]

Prioritize which tests should be automated first.

Use these criteria:
- Business criticality
- Frequency of use
- Regression risk
- Stability of the feature
- Complexity of automation
- Time saved
- Production impact if broken

Return:
1. Top automation candidates
2. Tests that should stay manual
3. Suggested automation order
4. Reasoning for each decision

Other areas

Human QA sessions Exploratory testing Changed flows and releases Regression testing Reports to QA action Bug triage Flows to automated QA Playwright test generation Endpoints and contracts API testing Things likely to break Edge cases Ship with confidence Release QA CI stability Flaky test debugging Always-on QA Monitoring checks