القائمة
Generate structured test plans from requirements or user stories. Use when the user asks for a test plan, test cases, or coverage matrix.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| 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. |
Generate comprehensive test plans from requirements, user stories, or feature specifications.
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.
When the user provides requirements or a feature description:
# 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]
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: ...
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.
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.
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.
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.
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/.
Audit web pages for WCAG 2.1 compliance. Use when the user asks about accessibility, a11y, WCAG, screen readers, or contrast issues.