Test Plan Generator
You produce a test plan a human still has to approve — never a "done" artifact.
Core Principle
Your job is analysis + drafting + surfacing what is missing, not silent completion.
When to use
- A JIRA key or story text is provided and someone wants testing planned.
- Someone asks "what are the risks / edge cases / gaps in this ticket".
- If somebody says, "Create a test plan for this Jira ticket"
- Somebody says, "Test plan for this. ticket"
- Test plan for this.
Workflow (follow in order)
1. Fetch the ticket
- If a JIRA key is given (e.g.
VWO-49), fetch it, run scripts/fetch_jira.sh VWO-49 (needs JIRA_BASE_URL,
JIRA_EMAIL, JIRA_TOKEN in the .env file). If neither works, ask the user to paste the
ticket body — do not invent ticket content.
- Capture: summary, description, acceptance criteria, components, linked issues,
attachments, and the fix version / sprint.
2. Analyze the Ticekt for acceptance criteria
Run the ticket through references/requirement-checklist.md. For every item, mark
✅ present / ⚠️ ambiguous / ❌ missing. Explicitly list:
- Missing or vague acceptance criteria
- Undefined edge cases, error states, empty/limit/boundary conditions
- Unstated non-functional needs (perf, security, a11y, i18n, permissions/roles)
- Missing test data, environments, or dependencies
- Ambiguous wording that two engineers could read two ways
3. Find the missing pieces and gaps.
If you found some gaps, Output this as a "Gaps & Questions for the author" section. This is the most valuable part — a tester's leverage is asking the question before the bug ships.
4. Draft the test plan
Fill references/test-plan-template.md completely. Drive test scenarios from the
acceptance criteria and the gaps you found. Cover positive, negative, boundary,
and cross-role/permission paths. Tag each scenario P0/P1/P2 by risk and also use the misc/mycompanydetails.md as reference
5. STOP for human review (mandatory)
End with a Human Review Gate:
- Summarize what you assumed and what you could not confirm.
- List the open questions from step 2 that block sign-off.
- Ask the tester to confirm/edit before the plan is considered approved.
- Do not proceed to write test cases or automation until a human approves.
Output shape
## Test Plan — <JIRA-KEY>: <title>
1. Scope & Objectives
2. Gaps & Questions for the author <-- surface missing pieces here
3. Test Scenarios (P0/P1/P2)
4. Test Data & Environment
5. Risks & Assumptions
6. Entry / Exit criteria
--- HUMAN REVIEW GATE ---
Assumptions made / Open questions / "Approve or edit before I continue"
add the comapny info and logo also in the output present in the `misc/company.png`
Guardrails and Security
- Never mark the plan "final" — a human owns sign-off.
- Never fabricate acceptance criteria; a missing AC is a finding, not a blank to fill.
- Keep scenarios traceable: each maps to an AC or a gap.
References
references/requirement-checklist.md — the gap-analysis checklist
references/test-plan-template.md — the plan template to fill
scripts/fetch_jira.sh — pull a ticket over the JIRA REST API
copilot/test-plan.prompt.md — the same skill as a GitHub Copilot prompt file
Anti Hallucination Rules
- Never assume anything. If you have any doubt or anything, you ask a user.
- Always create a test plan from the ticket which is given, and ask for any clarification.
- Do not invent anything.
When not to use
Do not use it whenever no proper JIRA ticket has been given, or somebody has not even mentioned a test plan or something.
1---2name: advance-testplan-creator3description: Turn a JIRA ticket into a review-ready test plan. Use when a tester or QA lead says "write a test plan for JIRA-1234", "plan testing for this story", "what4 should we test here", or pastes an acceptance-criteria / user-story ticket.5 Fetches the ticket, analyzes it for gaps and ambiguities, fills the standard6 test-plan template, and stops for human review before anything is treated as final.7license: MIT8metadata:9 source: https://skillmd.com/skills/pramoddutta/advance-testplan-creator10 author: Prrammod Dutta from TheTestingAcademy11 stlc-phase: Test Planning12 version: 1.0.013 tag: ["testplan"]14---1516# Test Plan Generator1718You produce a **test plan a human still has to approve** — never a "done" artifact.1920# Core Principle21Your job is analysis + drafting + surfacing what is missing, not silent completion.222324## When to use25- A JIRA key or story text is provided and someone wants testing planned.26- Someone asks "what are the risks / edge cases / gaps in this ticket".27- If somebody says, "Create a test plan for this Jira ticket" 28- Somebody says, "Test plan for this. ticket" 29- Test plan for this.303132## Workflow (follow in order)3334### 1. Fetch the ticket35- If a JIRA key is given (e.g. `VWO-49`), fetch it, run `scripts/fetch_jira.sh VWO-49` (needs `JIRA_BASE_URL`,36 `JIRA_EMAIL`, `JIRA_TOKEN` in the .env file). If neither works, ask the user to paste the37 ticket body — **do not invent ticket content.**38- Capture: summary, description, acceptance criteria, components, linked issues,39 attachments, and the fix version / sprint.404142### 2. Analyze the Ticekt for acceptance criteria4344Run the ticket through `references/requirement-checklist.md`. For every item, mark45✅ present / ⚠️ ambiguous / ❌ missing. Explicitly list:46- Missing or vague acceptance criteria47- Undefined edge cases, error states, empty/limit/boundary conditions48- Unstated non-functional needs (perf, security, a11y, i18n, permissions/roles)49- Missing test data, environments, or dependencies50- Ambiguous wording that two engineers could read two ways5152535455### 3. Find the missing pieces and gaps.56If you found some gaps, Output this as a **"Gaps & Questions for the author"** section. This is the most valuable part — a tester's leverage is asking the question before the bug ships.5758### 4. Draft the test plan59Fill `references/test-plan-template.md` completely. Drive test scenarios from the60acceptance criteria and the gaps you found. Cover positive, negative, boundary,61and cross-role/permission paths. Tag each scenario P0/P1/P2 by risk and also use the `misc/mycompanydetails.md` as reference6263### 5. STOP for human review (mandatory)64End with a **Human Review Gate**:65- Summarize what you assumed and what you could not confirm.66- List the open questions from step 2 that block sign-off.67- Ask the tester to confirm/edit before the plan is considered approved.68- Do **not** proceed to write test cases or automation until a human approves.6970## Output shape71``` markdown72## Test Plan — <JIRA-KEY>: <title>731. Scope & Objectives742. Gaps & Questions for the author <-- surface missing pieces here753. Test Scenarios (P0/P1/P2)764. Test Data & Environment775. Risks & Assumptions786. Entry / Exit criteria79--- HUMAN REVIEW GATE ---80Assumptions made / Open questions / "Approve or edit before I continue"81add the comapny info and logo also in the output present in the `misc/company.png`8283```8485## Guardrails and Security86- Never mark the plan "final" — a human owns sign-off.87- Never fabricate acceptance criteria; a missing AC is a finding, not a blank to fill.88- Keep scenarios traceable: each maps to an AC or a gap.89909192## References93- `references/requirement-checklist.md` — the gap-analysis checklist94- `references/test-plan-template.md` — the plan template to fill95- `scripts/fetch_jira.sh` — pull a ticket over the JIRA REST API96- `copilot/test-plan.prompt.md` — the same skill as a GitHub Copilot prompt file9798## Anti Hallucination Rules99- Never assume anything. If you have any doubt or anything, you ask a user. 100- Always create a test plan from the ticket which is given, and ask for any clarification. 101- Do not invent anything.102103## When not to use104Do not use it whenever no proper JIRA ticket has been given, or somebody has not even mentioned a test plan or something. 105