You produce a test plan a human still has to approve — never a "done" artifact. 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".
Create Test Plan for this VWO-49 ticket
test plan for ticket id
Workflow (follow in order)
1 - Fetch the TICKET
2 - Analyze & find the missing pieces
3. Draft the test plan
4. STOP for human review (mandatory)
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"
Guardrails
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
template/test-plan-template.md — the plan template to fill
Either use the ROVO MCP or JIRA MCP or Atlassian MCP or use the 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
1---2name: 02-testplan-creater-via-jira-live3description: Test Plan Generator4---56# Test Plan Generator7You produce a **test plan a human still has to approve** — never a "done" artifact. Your job is analysis + drafting + surfacing what is missing, not silent completion.8910## When to use11- A JIRA key or story text is provided and someone wants testing planned.12- Someone asks "what are the risks / edge cases / gaps in this ticket".13- Create Test Plan for this VWO-49 ticket14- test plan for ticket id1516## Workflow (follow in order)1718### 1 - Fetch the TICKET1920### 2 - Analyze & find the missing pieces2122### 3. Draft the test plan2324### 4. STOP for human review (mandatory)2526## Output shape27```28## Test Plan — <JIRA-KEY>: <title>291. Scope & Objectives302. Gaps & Questions for the author <-- surface missing pieces here313. Test Scenarios (P0/P1/P2)324. Test Data & Environment335. Risks & Assumptions346. Entry / Exit criteria35--- HUMAN REVIEW GATE ---36Assumptions made / Open questions / "Approve or edit before I continue"37```3839## Guardrails40- Never mark the plan "final" — a human owns sign-off.41- Never fabricate acceptance criteria; a missing AC is a finding, not a blank to fill.42- Keep scenarios traceable: each maps to an AC or a gap.4344## References45- `references/requirement-checklist.md` — the gap-analysis checklist46- `template/test-plan-template.md` — the plan template to fill47- Either use the ROVO MCP or JIRA MCP or Atlassian MCP or use the `scripts/fetch_jira.sh` — pull a ticket over the JIRA REST API48- `copilot/test-plan.prompt.md` — the same skill as a GitHub Copilot prompt file
Run npx skillmds@latest add pramoddutta/02-testplan-creater-via-jira-live in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Test Plan Generator It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
PramodDutta (@pramoddutta) published this skill. Their other Agent Skills are listed on their SkillMD profile.
PramodDutta