skills.rest
samcdavid
samcdavidCOMMUNITY
Explore all skills by this author →
𝕏@sammy_fix_itGitHub

my-test-plan

Analyze a ticket and linked PR to create a Markdown test plan.

4|1|Updated May 31, 2015
Search Tags:#quality-assurance#e2e-testing#pr-review#test-plan#test-scenarios#ticket-analysis
One-click install
npx skills add https://github.com/samcdavid/dotfiles --skill my-test-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: my-test-plan
Source: https://github.com/samcdavid/dotfiles/tree/main/claude/skills/my-test-plan
Command: npx skills add https://github.com/samcdavid/dotfiles --skill my-test-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes a ticket and its linked PR to produce a structured manual end-to-end test plan, translating requirements into concrete test scenarios and expected outcomes.

Core Features & Use Cases

  • Gather context from the ticket and PR (problem statement, acceptance criteria, reproduction steps) to inform test design.
  • Design 3-6 targeted test scenarios that validate the stated problem, cover edge cases, and guard against regressions.
  • Present the plan in a concise, review-ready format that can be handed to QA engineers.

Quick Start

Generate a 3-6 scenario test plan for the provided ticket and PR and return it in the required table format.

Frequently Asked Questions about my-test-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an end-to-end test plan from a Jira ticket and pull request?▼

To generate an end-to-end test plan, provide the ticket and linked PR so the tool can analyze problem statements, acceptance criteria, reproduction steps, and code changes to output structured test scenarios with expected outcomes.

What is the best way to structure manual test scenarios for a PR review?▼

The best way to structure manual test scenarios for a PR review is using a Markdown table under a ticket identifier, containing 3-6 high-level, non-implementation-specific cases covering primary fixes, edge cases, boundary cases, and regression guards.

How many test scenarios should I design for validating a new feature ticket?▼

You should design 3-6 targeted test scenarios per feature ticket to adequately validate the primary fix, cover edge cases, guard against regressions, and test boundary cases while keeping the plan review-ready.

Can I use ticket analysis to create non-implementation-specific regression guards?▼

Yes, ticket analysis extracts acceptance criteria and reproduction steps to design high-level regression guards that validate the stated problem without tying scenarios to specific implementation details from the code changes.

Does this test plan generation approach work without external dependencies?▼

Yes, this approach works without external dependencies, requiring only the raw context of the ticket and its linked PR to produce a review-ready Markdown table of test scenarios and expected outcomes.

What format should QA engineers expect for a review-ready test plan?▼

QA engineers should expect a review-ready test plan in a concise Markdown table format, organized under the specific ticket identifier with clear expected outcomes mapped to each high-level test scenario.

Related Skills

Explore More Software Engineering Skills→
markus41markus41
18

jira:review

Review linked commits and pull requests for a Jira issue against acceptance criteria.

Community
Intermediate
Yukine5377Yukine5377

bmad-agent-qa

Generate API and E2E tests for implemented code with deterministic pass/fail results.

Community
Intermediate
xlelibertyxleliberty

pr-review-expert

Analyze GitHub and GitLab pull request diffs for security and breaking changes.

Community
Advanced
thec3ukthec3uk

Testing Coverage

Analyze code coverage and generate tests to meet coverage standards.

Official
Basic