メニュー
QA test planning patterns. Use when creating test plans, writing test cases, building regression suites, validating designs against Figma, or documenting bugs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Code review knowledge. Use when reviewing an implementation against requirements, validating code quality, checking edge cases and security, or before opening a PR.
Systematic debugging knowledge. Use when diagnosing errors, investigating unexpected behavior, doing root cause analysis, or troubleshooting production issues.
QA and testing knowledge. Use when testing an implementation end-to-end — building a test plan, validating APIs with curl, driving the UI with Playwright, comparing against Figma, and documenting pass/fail with evidence.
Requirements refinement knowledge. Use when turning a vague request into a clear spec, defining API contracts, identifying affected repositories, or capturing scope and edge cases before coding.
AWS infrastructure patterns. Use when working with AWS services, secrets, ECS/EKS, RDS, S3, CloudWatch, or debugging infrastructure issues.
NestJS backend development patterns. Use when developing backend APIs with NestJS, TypeORM/Prisma, and TypeScript.
| name | qa-test-planner |
| description | QA test planning patterns. Use when creating test plans, writing test cases, building regression suites, validating designs against Figma, or documenting bugs. |
| triggers | ["qa","test plan","test cases","regression","bug report","testing","quality assurance"] |
| Task | What You Get | Time |
|---|---|---|
| Test Plan | Strategy, scope, schedule, risks | 10-15 min |
| Test Cases | Step-by-step instructions, expected results | 5-10 min each |
| Regression Suite | Smoke tests, critical paths, execution order | 15-20 min |
| Figma Validation | Design-implementation comparison | 10-15 min |
| Bug Report | Reproducible steps, environment, evidence | 5 min |
## TC-001: [Test Case Title]
**Priority:** High | Medium | Low
**Type:** Functional | UI | Integration | Regression
### Preconditions
- [Setup requirement]
### Test Steps
1. [Action]
**Expected:** [Result]
2. [Action]
**Expected:** [Result]
# BUG-[ID]: [Clear, specific title]
**Severity:** Critical | High | Medium | Low
## Environment
- OS, Browser, Build, URL
## Steps to Reproduce
1. [Step]
2. [Step]
## Expected Behavior
[What should happen]
## Actual Behavior
[What happens]
## Evidence
- Screenshot, console errors
| Level | Criteria | Examples |
|---|---|---|
| Critical (P0) | System crash, data loss, security | Payment fails, login broken |
| High (P1) | Major feature broken, no workaround | Search not working |
| Medium (P2) | Feature partial, workaround exists | Filter missing option |
| Low (P3) | Cosmetic, rare edge cases | Typo, minor alignment |
| Suite | Duration | When |
|---|---|---|
| Smoke | 15-30 min | Daily |
| Targeted | 30-60 min | Per change |
| Full | 2-4 hours | Weekly/Release |
| Sanity | 10-15 min | After hotfix |
PASS: All P0 pass, 90%+ P1 pass, no critical bugs open FAIL: Any P0 fails, critical bug, security vulnerability