From product-design
Enforces QA test naming conventions, directory structure, status lifecycle transitions, and metadata for organized test management and traceability.
How this skill is triggered — by the user, by Claude, or both
Slash command
/product-design:qa-test-managementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Ensure consistent QA test organization, lifecycle management, and traceability.
Ensure consistent QA test organization, lifecycle management, and traceability.
When working with QA tests, automatically:
qa-tests/
├── draft/ # Tests being written
│ └── QA-20250105-001-login.md
├── active/ # Tests ready for execution
│ └── QA-20250104-002-checkout.md
├── executed/ # Recently executed tests
│ └── QA-20250103-001-search.md
├── archived/ # Historical tests
│ └── 2024/
│ └── QA-20241215-001-old-feature.md
└── screenshots/ # Test evidence
├── login-page.png
└── checkout-success.png
QA-YYYYMMDD-###-feature-name.md
QA - Prefix for all QA test filesYYYYMMDD - Creation date### - Sequential number for that day (001, 002, etc.)feature-name - Kebab-case feature descriptionExamples:
QA-20250105-001-user-login.mdQA-20250105-002-password-reset.mdQA-20250106-001-checkout-flow.mdDRAFT → ACTIVE → EXECUTED → ARCHIVED
| Status | Description | Location |
|---|---|---|
DRAFT | Being written, not ready for execution | qa-tests/draft/ |
ACTIVE | Ready to be executed by testers | qa-tests/active/ |
EXECUTED | Has been run, awaiting review/archival | qa-tests/executed/ |
ARCHIVED | Historical reference, no longer active | qa-tests/archived/YYYY/ |
Every QA test file MUST include:
## Metadata
- **Test ID**: QA-YYYYMMDD-###
- **Feature**: [Feature name]
- **Application**: [App name]
- **URL**: [Test environment URL]
- **Created**: [YYYY-MM-DD]
- **Author**: [Name]
- **Status**: [DRAFT|ACTIVE|EXECUTED|ARCHIVED]
- **Priority**: [Critical|High|Medium|Low]
- **Estimated Time**: [X minutes]
- **PRD Reference**: [Link to PRD section if applicable]
| Priority | Description | Execution Frequency |
|---|---|---|
| Critical | Core functionality, blocking issues | Every release |
| High | Important features, user-facing | Every sprint |
| Medium | Secondary features, edge cases | Monthly |
| Low | Nice-to-have, rare scenarios | Quarterly |
Link QA tests to PRD requirements:
## Requirement Traceability
| Requirement | PRD Section | Test Cases |
|-------------|-------------|------------|
| User can login with email/password | PRD 3.1.1 | TC-001, TC-002 |
| Password must be 8+ characters | PRD 3.1.2 | TC-003 |
| Failed login shows error message | PRD 3.1.3 | EC-001, EC-002 |
Track test runs in each test file:
## Test Execution Log
| Date | Tester | Environment | Build | Result | Issues |
|------|--------|-------------|-------|--------|--------|
| 2025-01-05 | Jane | staging | v1.2.3 | PASS | None |
| 2025-01-04 | John | staging | v1.2.2 | FAIL | #123 |
Before moving a test from DRAFT to ACTIVE:
Archive a test when:
Archival metadata to add:
## Archive Information
- **Archived Date**: [YYYY-MM-DD]
- **Archived By**: [Name]
- **Archive Reason**: [Deprecated|Superseded|Stale|Requirements Changed]
- **Superseded By**: [New test ID, if applicable]
When listing or reporting on QA tests:
npx claudepluginhub jpoutrin/product-forge --plugin product-designEstablishes QA processes for software projects: test strategies, Google-standard cases (AAA pattern), execution tracking, P0-P4 bug classification, OWASP security testing, quality metrics, reports, autonomous execution, and handoff templates.
Owns the quality gate for features and releases. Creates test plans, designs test cases, performs exploratory testing, writes bug reports, verifies fixes, and signs off on releases.
Generates ISTQB CTFL-aligned QA artifacts like test plans, cases, bug reports, traceability matrices, and regression suites. Supports test design techniques, risk-based testing, and Playwright automation.