prism-qa-test-plan

Generate QA test plans from code changes with pass/fail checklists.

Updated May 2, 2026
One-click install
npx skills add https://github.com/HunterMcGrew/PRISM --skill prism-qa-test-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prism-qa-test-plan
Source: https://github.com/HunterMcGrew/PRISM/tree/main/.cursor/skills/prism-qa-test-plan
Command: npx skills add https://github.com/HunterMcGrew/PRISM --skill prism-qa-test-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation of QA test plans by automatically generating checklists based on code changes, saving time and reducing errors in the QA process.

Core Features & Use Cases

  • Automated Test Plan Generation: Automatically builds manual Pass/Fail checklists in tester-facing English.
  • Mode Detection: Identifies the type of test plan required (release, sprint, single PR, bug fix) based on input and ticket labels.
  • Risk-Based Allocation: Prioritizes test effort based on the likelihood and impact of failure.
  • Observable Outcomes: Ensures test steps are clear and observable, improving consistency and accuracy.
  • Regression Analysis: Identifies potential areas of regression and suggests additional testing.
  • Ticket Traceability: Maps every commit to its ticket and test section for thorough coverage.
  • Tester-Friendly Writing: Provides plain English instructions without technical jargon.
  • Use Case: Imagine you have a bug fix that affects multiple components. Use this Skill to generate a comprehensive test plan that covers all potential scenarios.

Quick Start

Invoke the 'Reese' skill with the command: "Reese, QA plan for PR #1234."

Frequently Asked Questions about prism-qa-test-plan

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

FAQPage Schema
How do I generate a QA test plan from code changes for a pull request?

To generate a QA test plan from code changes, provide the pull request details and ticket labels. The system analyzes the modifications and produces a manual Pass/Fail checklist with risk-based test scenarios for the PR.

What is risk-based test allocation in QA test plan generation?

Risk-based test allocation in QA test plan generation prioritizes testing effort by evaluating the likelihood and impact of potential failures. This ensures critical code changes receive the most thorough regression and scenario coverage.

Can I create different types of QA test plans for sprints and releases?

Yes, you can create QA test plans for releases, sprints, single PRs, and bug fixes. The system detects the required mode by analyzing input commands, ticket labels, and prompt words to match the verification scope.

How do I map test scenarios to Jira tickets for regression testing?

To map test scenarios to tickets for regression testing, the system analyzes commit history and ticket labels. It provides ticket traceability by linking every commit to its corresponding ticket and test section.

Does the generated QA test plan include plain English instructions for testers?

Yes, the generated QA test plan includes plain English instructions for testers. It writes observable, tester-facing steps without technical jargon, improving consistency and accuracy for manual Pass/Fail verification.

What are the limitations of automated test plan generation for bug fixes?

Automated test plan generation for bug fixes relies on analyzing code changes, ticket labels, and prompt words. It cannot invent test scenarios for undocumented modifications and requires clear input to identify potential regression areas accurately.