Skills qa-test-planner
📦

qa-test-planner

Content revision r1 High Risk ⚙️ External commands🌐 Network access

Plan QA Tests and Bug Reports

QA teams need consistent test plans, cases, regression suites, and bug reports. This skill guides Claude, Codex, and Claude Code to produce structured QA deliverables.

Supports: Claude Codex Code(CC)
⚠️ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "qa-test-planner" from https://skillstore.io/skills/softaworks-qa-test-planner.md and its manifest at https://skillstore.io/api/skills/softaworks-qa-test-planner/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/softaworks-qa-test-planner.md Signed manifest GET /api/skills/softaworks-qa-test-planner/manifest Signed lockfile GET /api/skills/softaworks-qa-test-planner/lockfile

Test it

Using "qa-test-planner". Generate test cases for checkout.

Expected outcome:

A prioritized set of checkout test cases covering valid payment, invalid card handling, empty cart behavior, promo codes, and guest checkout.

Using "qa-test-planner". Create a regression suite for payments.

Expected outcome:

A regression outline with smoke tests first, critical payment paths next, lower priority edge cases last, and clear pass criteria.

Using "qa-test-planner". Document a login validation defect.

Expected outcome:

A bug report with title, severity, priority, environment, reproduction steps, expected result, actual result, impact, and evidence checklist.

Security Audit

High Risk
v4 • 7/7/2026 Open versioned report

Most static findings are false positives from Markdown examples, QA checklists, sample URLs, and timestamp generation. One real issue remains: both helper scripts use eval with interactive user input, which can enable command injection when the scripts are run. No prompt injection or credential exfiltration intent was found.

8
Files scanned
3,267
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

High
scripts/create_bug_report.sh:22-36scripts/generate_test_cases.sh:23-37
Unsafe Shell eval on User Input
Both interactive helper scripts assign user input through eval inside prompt_input. A crafted response can break out of the assignment and execute shell commands when the script runs.
The scripts read interactive input and interpolate it into eval-based assignments. The variable names are fixed, but the user-controlled value can still alter the evaluated shell text.

Risk Factors

⚙️ External commands (43)
scripts/create_bug_report.sh:206 scripts/create_bug_report.sh:208 scripts/create_bug_report.sh:44 scripts/create_bug_report.sh:160 scripts/create_bug_report.sh:1 scripts/generate_test_cases.sh:191 scripts/generate_test_cases.sh:1 SKILL.md:11 SKILL.md:18-20 SKILL.md:20-23 SKILL.md:23-25 SKILL.md:25-28 SKILL.md:28-30 SKILL.md:30-33 SKILL.md:33-35 SKILL.md:35-38 SKILL.md:38-40 SKILL.md:40-58 SKILL.md:58-81 SKILL.md:81-91 SKILL.md:91-92 SKILL.md:92-191 SKILL.md:191-229 SKILL.md:229-249 SKILL.md:249-319 SKILL.md:319-328 SKILL.md:328-371 SKILL.md:371-397 SKILL.md:397-407 SKILL.md:407-410 SKILL.md:410-419 SKILL.md:419-422 SKILL.md:422-429 SKILL.md:429-443 SKILL.md:443-448 SKILL.md:448-511 SKILL.md:511-553 SKILL.md:553-557 SKILL.md:557-565 SKILL.md:565-661 SKILL.md:661-703 SKILL.md:703-710 SKILL.md:710-749
🌐 Network access (1)
SKILL.md:677
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/softaworks-qa-test-planner/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/softaworks-qa-test-planner/security.svg)](https://skillstore.io/skills/softaworks-qa-test-planner?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/softaworks-qa-test-planner?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/softaworks-qa-test-planner/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/softaworks-qa-test-planner.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

softaworks. (2026). qa-test-planner security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/softaworks-qa-test-planner/audits/4

BibTeX citation

@techreport{softaworks-softaworks-qa-test-planner-2026, author = {softaworks}, title = {qa-test-planner security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/softaworks-qa-test-planner/audits/4}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "qa-test-planner security audit report (audit version 4)" version: "unspecified" type: report authors: - name: "softaworks" date-released: "2026-07-07" url: "https://skillstore.io/skills/softaworks-qa-test-planner/audits/4" identifiers: - type: other value: "skillstore:softaworks-qa-test-planner:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
82
Architecture
85
Maintainability
87
Content
70
Community
74
Spec Compliance

What You Can Build

Create Release Test Coverage

Build a test plan and regression outline for a new feature or release candidate.

Turn Requirements Into Test Cases

Convert product requirements into prioritized manual test cases with clear expected results.

Validate UI Against Design

Prepare Figma comparison checklists for spacing, typography, colors, responsive layout, and states.

Try These Prompts

Start a Test Plan 
Create a QA test plan for the user authentication feature. Include scope, risks, environments, entry criteria, and exit criteria.
Generate Manual Cases 
Generate six manual test cases for the checkout flow. Include priority, preconditions, steps, expected results, and test data.
Build Regression Coverage 
Build a regression suite for the payment module. Separate smoke, critical path, and full regression tests with execution order and pass criteria.
Combine Design and Bug Reporting 
Compare the login page against the provided Figma design context. List visual discrepancies and create a bug report for the highest impact issue.

Best Practices

  • Provide requirements, target platforms, test data needs, and release context before asking for QA artifacts.
  • Review generated cases with developers, designers, and product owners before execution.
  • Keep regression suites focused on critical paths and update them after each release.

Avoid

  • Do not accept vague test steps without expected results.
  • Do not use generated bug reports without verifying reproduction steps and environment details.
  • Do not run optional shell scripts before reviewing their local behavior.

Frequently Asked Questions

Can this skill execute tests for me?
No. It plans tests and creates documentation, but a tester or automation system must execute them.
Does it support Figma validation?
Yes. It provides design comparison checklists when you supply Figma context or MCP access.
What artifacts can it create?
It can create test plans, manual test cases, regression suite outlines, Figma validation checklists, and bug reports.
Is it only for QA engineers?
No. Product managers, designers, developers, and release managers can use it to structure testing work.
Are the shell scripts required?
No. They are optional helpers for local Markdown generation and should be reviewed before use.
Can it replace human QA review?
No. It improves structure and coverage, but humans must validate accuracy, priority, and release impact.

Developer Details

Author

softaworks

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/softaworks/agent-toolkit/tree/main/skills/qa-test-planner/

Ref

f93e9bb0daca99badb6a7e574b97737155d57cb3

Maintenance freshness

7/18/2026

Usage

34 downloads · 200 views

File structure

📁 references/

📄 bug_report_templates.md

📄 figma_validation.md

📄 regression_testing.md

📄 test_case_templates.md

📁 scripts/

📄 create_bug_report.sh

📄 generate_test_cases.sh

📄 README.md

📄 SKILL.md

More from softaworks

View all

Related Skills

View all