Qa Test Planner
Produce test plans, manual cases, regression suites, Figma design checks, and bug reports when explicitly invoking the QA planner skill.
Overview
qa-test-planner is an agent skill most often used in Ship (also Build) that generates test plans, manual cases, regression suites, Figma checks, and bug reports when explicitly invoked.
Install
npx skills add https://github.com/softaworks/agent-toolkit --skill qa-test-plannerWhat is this skill?
- Explicit activation only (/qa-test-planner or named invocation)—no silent auto-runs
- Five work modes: test plan, manual test cases, regression suite, Figma validation, bug report
- Documented time budgets: plans 10–15 min, cases 5–10 min each, regression 15–20 min, Figma compare 10–15 min
- Figma MCP integration for design–implementation discrepancy lists
- Natural-language quick starts for auth, checkout, payment, and login scenarios
- 5 documented QA task modes
- Quick reference time ranges from 5–20 minutes per artifact type
Adoption & trust: 3.8k installs on skills.sh; 2k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to ship a feature but only have ad-hoc clicking notes and no regression map or reproducible bug write-ups.
Who is it for?
Indie SaaS or app builders explicitly calling a QA skill before merge, release, or design sign-off on critical flows.
Skip if: Builders who want always-on test generation on every message, or teams that only need load-test automation with zero manual case docs.
When should I use this skill?
Explicitly call qa-test-planner by name when you need test plans, cases, regression suites, Figma validation, or bug reports.
What do I get? / Deliverables
You get structured QA documents and design discrepancy lists ready for execution before release or hotfix follow-up.
- Test plan with strategy, scope, schedule, and risks
- Manual test cases with steps and expected results
- Regression suite with smoke tests and execution order
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Ship/testing because the skill’s outputs are release readiness artifacts—plans, cases, regression order, and bug documentation. testing subphase matches explicit QA deliverables rather than ad-hoc coding or marketing work.
Where it fits
Compare implemented login page against Figma after CSS pass to catch spacing and token drift.
Generate checkout manual cases with expected results before tagging a release candidate.
File a structured bug report with repro steps when form validation fails on staging.
Extend the payment-module regression suite after a hotfix to document smoke execution order.
How it compares
Structured QA document generator with optional Figma MCP—not a replacement for your CI test runner or Playwright suite.
Common Questions / FAQ
Who is qa-test-planner for?
It is for solo and indie builders wearing the QA hat on SaaS, API, or mobile products who need professional test artifacts without hiring a dedicated QA engineer.
When should I use qa-test-planner?
Use it in Ship before release for plans and regression suites, in Build when validating UI against Figma after implementation, and whenever you need a formal bug report for triage.
Is qa-test-planner safe to install?
It may use Figma MCP and read design URLs you provide; check the Security Audits panel on this Prism page and limit design links to non-sensitive projects.
SKILL.md
READMESKILL.md - Qa Test Planner
# QA Test Planner A comprehensive skill for QA engineers to create test plans, generate manual test cases, build regression test suites, validate designs against Figma, and document bugs effectively. > **Activation:** This skill is triggered only when explicitly called by name (e.g., `/qa-test-planner`, `qa-test-planner`, or `use the skill qa-test-planner`). --- ## Quick Start **Create a test plan:** ``` "Create a test plan for the user authentication feature" ``` **Generate test cases:** ``` "Generate manual test cases for the checkout flow" ``` **Build regression suite:** ``` "Build a regression test suite for the payment module" ``` **Validate against Figma:** ``` "Compare the login page against the Figma design at [URL]" ``` **Create bug report:** ``` "Create a bug report for the form validation issue" ``` --- ## Quick Reference | 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, discrepancy list | 10-15 min | | Bug Report | Reproducible steps, environment, evidence | 5 min | --- ## How It Works ``` Your Request │ ▼ ┌─────────────────────────────────────────────────────┐ │ 1. ANALYZE │ │ • Parse feature/requirement │ │ • Identify test types needed │ │ • Determine scope and priorities │ ├─────────────────────────────────────────────────────┤ │ 2. GENERATE │ │ • Create structured deliverables │ │ • Apply templates and best practices │ │ • Include edge cases and variations │ ├─────────────────────────────────────────────────────┤ │ 3. VALIDATE │ │ • Check completeness │ │ • Verify traceability │ │ • Ensure actionable steps │ └─────────────────────────────────────────────────────┘ │ ▼ QA Deliverable Ready ``` --- ## Commands ### Interactive Scripts | Script | Purpose | Usage | |--------|---------|-------| | `./scripts/generate_test_cases.sh` | Create test cases interactively | Step-by-step prompts | | `./scripts/create_bug_report.sh` | Generate bug reports | Guided input collection | ### Natural Language | Request | Output | |---------|--------| | "Create test plan for {feature}" | Complete test plan document | | "Generate {N} test cases for {feature}" | Numbered test cases with steps | | "Build smoke test suite" | Critical path tests | | "Compare with Figma at {URL}" | Visual validation checklist | | "Document bug: {description}" | Structured bug report | --- ## Core Deliverables ### 1. Test Plans - Test scope and objectives - Testing approach and strategy - Environment requirements - Entry/exit criteria - Risk assessment - Timeline and milestones ### 2. Manual Test Cases - Step-by-step instructions - Expected vs actual results - Preconditions and setup - Test data requirements - Priority and severity ### 3. Regression Suites - Smoke tests (15-30 min) - Full regression (2-4 hours) - Targeted regression (30-60 min) - Execution order and dependencies ### 4. Figma Validation - Component-by-component comparison - Spacing and typography checks - Color and visual consistency - Interactive state validation ### 5. Bug Reports - Clear reproduction steps - Environment details - Evidence (screenshots, logs) - Severity and priority --- ## Anti-Patterns | Avoid | Why | Inst