Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

test-plan-generator

Estrelas3

Forks0

Atualizado11 de junho de 2026 às 23:06

Generate structured test plans from requirements or user stories. Use when the user asks for a test plan, test cases, or coverage matrix.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

LucaB28

LucaB28/claude-qa-toolkit

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

SKILL.md

readonly

name	test-plan-generator
description	Generate structured test plans from requirements or user stories. Use when the user asks for a test plan, test cases, or coverage matrix.

Test Plan Generator

Generate comprehensive test plans from requirements, user stories, or feature specifications.

Description

This skill transforms requirements documents, user stories, Jira tickets, or feature descriptions into structured, actionable test plans with full coverage of functional, edge case, and non-functional scenarios.

Instructions

When the user provides requirements or a feature description:

Parse Requirements: Extract testable requirements, acceptance criteria, and business rules
Identify Test Scenarios: For each requirement, generate:
- Happy path scenarios
- Negative/error scenarios
- Boundary value scenarios
- Edge cases
Organize by Priority: Classify tests as P0 (Critical), P1 (High), P2 (Medium), P3 (Low)
Define Test Cases: For each scenario, specify:
- ID: Unique identifier (TC-XXX)
- Title: Clear, descriptive name
- Preconditions: Required setup
- Steps: Numbered step-by-step instructions
- Expected Result: Specific, verifiable outcome
- Priority: P0-P3
- Type: Functional / UI / API / Security / Performance
Coverage Matrix: Map test cases back to requirements to ensure 100% coverage

Output Template

# Test Plan: [Feature Name]
**Version**: 1.0
**Author**: [Generated by Claude QA Toolkit]
**Date**: [date]
**Status**: Draft

## 1. Scope
### In Scope
- [list]
### Out of Scope
- [list]

## 2. Test Strategy
- **Approach**: [manual/automated/hybrid]
- **Environments**: [list]
- **Test Data**: [requirements]

## 3. Test Cases
### [Module/Feature Area]
| ID | Title | Priority | Type | Steps | Expected Result |
|----|-------|----------|------|-------|-----------------|

## 4. Coverage Matrix
| Requirement | Test Cases | Coverage |
|-------------|-----------|----------|

## 5. Risks & Dependencies
| Risk | Mitigation |
|------|-----------|

## 6. Entry/Exit Criteria
### Entry Criteria
- [list]
### Exit Criteria
- [list]

Example Usage

Generate a test plan for this user story:
"As a user, I want to reset my password via email so I can regain access to my account."
Acceptance criteria: ...

Mais deste repositório

mesmo repositório

qa-audit

LucaB28/claude-qa-toolkit

Full QA audit orchestrator. Use when the user asks to "test my app", "run a full QA audit", "test everything", or invokes /qa-audit. Discovers what kind of application this is, selects the relevant QA agents (ui-inspector, api-sentinel, security-scout, perf-guardian, data-validator, regression-watcher), runs them, and merges their reports into one master QA report.

2026-06-113

qa-init

LucaB28/claude-qa-toolkit

Onboard the QA toolkit onto any project. Use on first contact with a new codebase, when the user says "set up QA", "qa init", "/qa-init", or when any QA agent finds no qa-profile.md. Studies the project deeply and writes the persistent QA profile that every other agent reads first — the toolkit's long-term memory for this project.

2026-06-113

qa-ci

LucaB28/claude-qa-toolkit

Wire the QA suite into CI. Use when the user wants tests running automatically on every PR or on a schedule: "add this to CI", "run tests on every push", "/qa-ci". Generates GitHub Actions workflows for the generated Playwright suite and (optionally) scheduled full audits.

2026-06-113

qa-heal

LucaB28/claude-qa-toolkit

Self-healing for the generated test suite. Use when previously-green Playwright tests are failing, the user says "my tests broke", "fix the tests", "/qa-heal", or after a UI refactor breaks selectors. Classifies each failure (real bug vs test drift) and repairs the drift — never papers over real bugs.

2026-06-113

qa-trend

LucaB28/claude-qa-toolkit

Compare two QA audit runs and report what improved, what regressed, and what persists. Use when the user asks "did it improve since last time?", "compare audits", "QA trend", or invokes /qa-trend. Requires at least two timestamped runs under qa-reports/runs/.

2026-06-113

accessibility-checker

LucaB28/claude-qa-toolkit

Audit web pages for WCAG 2.1 compliance. Use when the user asks about accessibility, a11y, WCAG, screen readers, or contrast issues.

2026-06-113

Test Plan Generator

Generate comprehensive test plans from requirements, user stories, or feature specifications.

Description

Instructions

When the user provides requirements or a feature description:

Parse Requirements: Extract testable requirements, acceptance criteria, and business rules

Identify Test Scenarios: For each requirement, generate:

Happy path scenarios
Negative/error scenarios
Boundary value scenarios
Edge cases

Organize by Priority: Classify tests as P0 (Critical), P1 (High), P2 (Medium), P3 (Low)

Define Test Cases: For each scenario, specify:

ID: Unique identifier (TC-XXX)
Title: Clear, descriptive name
Preconditions: Required setup
Steps: Numbered step-by-step instructions
Expected Result: Specific, verifiable outcome
Priority: P0-P3
Type: Functional / UI / API / Security / Performance

Coverage Matrix: Map test cases back to requirements to ensure 100% coverage

Output Template

# Test Plan: [Feature Name] **Version**: 1.0 **Author**: [Generated by Claude QA Toolkit] **Date**: [date] **Status**: Draft ## 1. Scope ### In Scope - [list] ### Out of Scope - [list] ## 2. Test Strategy - **Approach**: [manual/automated/hybrid] - **Environments**: [list] - **Test Data**: [requirements] ## 3. Test Cases ### [Module/Feature Area] | ID | Title | Priority | Type | Steps | Expected Result | |----|-------|----------|------|-------|-----------------| ## 4. Coverage Matrix | Requirement | Test Cases | Coverage | |-------------|-----------|----------| ## 5. Risks & Dependencies | Risk | Mitigation | |------|-----------| ## 6. Entry/Exit Criteria ### Entry Criteria - [list] ### Exit Criteria - [list]

Example Usage

Generate a test plan for this user story: "As a user, I want to reset my password via email so I can regain access to my account." Acceptance criteria: ...