sumo-qa-creating-test-plan

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.

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.

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.

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.

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.

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.