test-plan-generator SKILL.md skillA
test-plan-generator from pramoddutta/aitesterblueprint4x is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pramoddutta/aitesterblueprint4x/test-plan-generator@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pramoddutta/aitesterblueprint4x
- Path
chapter_02_Prompt_Eng/prompt_templates/stlc/02-test-planning/test-plan-generator/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Aug 11, 2026
- Size
- 3,533 bytes
- Repository stars
- 14
- License
- none declared
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", "what should we test here", or pastes an acceptance-criteria / user-story ticket. Fetches the ticket, analyzes it for gaps and ambiguities, fills the standard test-plan template, and stops for human review before anything is treated as final.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Test Plan Generator 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". ## Workflow (follow in order) ### 1. Fetch the ticket - If a JIRA key is given (e.g. `VOC-1234`), fetch it. Prefer an available JIRA MCP tool. If none, run `bash scripts/fetch_jira.sh VOC-1234` (needs `JIRA_BASE_URL`, `JIRA_EMAIL`, `JIRA_TOKEN` env vars). 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 & find the missing pieces 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 …
Read the whole file at its exact version.
How to install
mdr add pramoddutta/aitesterblueprint4x/test-plan-generator@sha256:669d4ac250d20743The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_m76mpwrjkzc3cczq)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 11, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3533 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pramoddutta/aitesterblueprint4x · 14 stars · license none declared · pushed 2026-10-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_m76mpwrjkzc3cczq GET https://markdownregistry.com/api/v1/resolve?ref=pramoddutta/aitesterblueprint4x/test-plan-generator GET https://markdownregistry.com/api/v1/blob/669d4ac250d207435a247c2c1edce3045aa3317b969ed38f2587c004085194ac
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from pramoddutta/aitesterblueprint4x
Every file in pramoddutta/aitesterblueprint4x