QA Test Planner

Generates tracker-ready test plans, manual test cases, regression suites, and bug reports for AI coding agents.

SkillMulti-Agent SkillVerified

View source

Category: Test Cases & QA Docs
Author: softaworks
Pricing: free

Install QA Test Planner in your agent

npx skills add softaworks/agent-toolkit

Add the skill
Run this command in your project terminal.
Finish setup
Select Claude Code if the installer asks for a target, then restart Claude Code so it discovers the skill.
Try it
Ask your agent: “Create a QA test plan for the current feature.”

npx skills add softaworks/agent-toolkit

Add the skill
Run this command in your project terminal.
Finish setup
Select Cursor if the installer asks for a target, then reload Cursor so it discovers the skill.
Try it
Ask your agent: “Create a QA test plan for the current feature.”

npx skills add softaworks/agent-toolkit

Add the skill
Run this command in your project terminal.
Finish setup
Select Codex if the installer asks for a target, then restart Codex so it discovers the skill.
Try it
Ask your agent: “Create a QA test plan for the current feature.”

npx skills add softaworks/agent-toolkit

Add the skill
Run this command in your project terminal.
Finish setup
Choose your supported agent when prompted, then restart it so the new skill is discovered.
Try it
Ask your agent: “Create a QA test plan for the current feature.”

What it does

QA Test Planner is an Agent Skills–format resource in softaworks/agent-toolkit that works with multiple AI coding agents. It generates QA documentation rather than automation code: test plans, structured manual test cases with preconditions, numbered steps, expected results, test data, and edge cases, plus tiered regression suites. It also generates Figma design validations via the Figma MCP and bug reports formatted for tracking systems like Jira, Linear, or GitHub Issues.

How QA teams use it

Generate a standardized test plan and manual test case set from a feature description, ready to paste into a test management tool.
Produce a tiered regression suite scoped to the time available before a release — smoke, targeted, full, or sanity.
Turn a design in Figma into a validation checklist, or a bug description into a tracker-ready report for Jira, Linear, or GitHub Issues.