---
name: qa-test-plan
description: Create a practical QA test plan from requirements, epics, user stories, acceptance criteria, or Jira issue context.
---

# QA Test Plan Skill

Use this skill when the user asks Copilot to create or improve a test plan for a feature, release, epic, sprint, or Jira ticket.

## Inputs To Ask For

- Product or feature name
- Requirement, user story, epic, or Jira ticket key
- Release scope and out-of-scope items
- Platforms, browsers, devices, and environments
- Risk areas, dependencies, and known constraints
- Timeline, owners, entry criteria, and exit criteria

## Output Format

Create the test plan with these sections:

1. Objective
2. Scope
3. Out Of Scope
4. Test Items
5. Test Approach
6. Test Types
7. Environment And Test Data
8. Entry Criteria
9. Exit Criteria
10. Risks And Mitigations
11. Roles And Responsibilities
12. Deliverables
13. Schedule
14. Approval Checklist

## Rules

- Keep the plan realistic for the supplied context.
- Call out missing information as assumptions.
- Separate functional, integration, regression, exploratory, accessibility, security, and performance coverage where relevant.
- Include SDLC/STLC traceability from requirement to test artifact.
- If Jira MCP tools are available, use them to read linked issues, epics, labels, comments, and acceptance criteria before drafting.

## Example Prompt

Create a QA test plan for Jira story `PROJ-142`. Use the linked epic, acceptance criteria, comments, and attachments if available. Highlight assumptions and risks.