sumo-qa-creating-test-plan

Name: sumo-qa-creating-test-plan
Availability: InStock
Author: sumithr

Generate a phased ISTQB-style test plan with entry and exit criteria.

5|1|Updated May 12, 2026

Search Tags:#tdd #qa #test plan #risk analysis #istqb #exit criteria #entry criteria

Ready to run

npx skills add https://github.com/sumithr/sumo-qa --skill sumo-qa-creating-test-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sumo-qa-creating-test-plan
Source: https://github.com/sumithr/sumo-qa/tree/main/skills/sumo-qa-creating-test-plan
Command: npx skills add https://github.com/sumithr/sumo-qa --skill sumo-qa-creating-test-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams turn upcoming work into a phased, ISTQB-style QA test plan with explicit entry and exit criteria, so you don’t end up with an unreviewable checklist or a wish-list.

Core Features & Use Cases

Phased planning with confirmations: Walks through scope, risks, criteria, and phases one section at a time, gating progress on your confirmation.
Risk-first test design: Produces named risks grounded in repo evidence, then assigns one technique per risk from an ISTQB-grounded catalogue.
Hard-gated entry/exit: Enforces the Iron Law that a plan cannot be produced without explicit entry criteria and exit criteria, plus residual risks.

Quick Start

Ask the AI to create a formal test plan for your upcoming feature or tracked change, including the entry/exit criteria you want for QA sign-off.

Frequently Asked Questions about sumo-qa-creating-test-plan

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

FAQPage Schema

How do I create an ISTQB-style test plan with entry and exit criteria?▼

An ISTQB-style test plan defines explicit entry and exit criteria, scope, risks, and measurable acceptance boundaries. This Skill builds a formal, phased test plan by walking through scope, risks, criteria, and phases one section at a time, gating progress on your confirmation.

What's the best way to design risk-based test plans for major software changes?▼

Risk-based test plans ground named risks in repository evidence, assigning one testing technique per risk from an ISTQB-grounded catalogue. This approach enforces mandatory entry and exit gating, plus residual risks, ensuring measurable acceptance boundaries for major software changes.

How do I define exit criteria for QA sign-off on a tracked software change?▼

Exit criteria for QA sign-off define the measurable acceptance boundaries a change must meet. This Skill enforces an Iron Law that no plan can be produced without explicit exit criteria, alongside entry criteria and residual risks, to ensure reviewable boundaries.

Can I generate a full test plan in a single prompt for my upcoming feature?▼

No, this Skill avoids single-turn plan dumps by walking through test-planning scenarios step-by-step. It produces a phased, ISTQB-style test plan through collaborative confirmation, gating progress on your input for scope, evidence-based risks, and criteria sections.

Why does my test plan need risk analysis before selecting testing techniques?▼

Risk analysis before technique selection ensures evidence-based test design. This Skill requires repo exploration to produce named risks, then assigns one ISTQB technique per risk from loaded catalogues, preventing unreviewable checklists or wish-lists.

When do I need formal entry criteria in a software test plan?▼

Formal entry criteria are needed when defining measurable acceptance boundaries for tracked or major software changes. This Skill enforces mandatory entry and exit gating, requiring explicit criteria before phased test planning can proceed.