qa

Generate structured QA plans and execute manual test runs with evidence.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/mitchdowd/skills --skill qa-mitchdowd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/mitchdowd/skills/tree/main/qa
Command: npx skills add https://github.com/mitchdowd/skills --skill qa-mitchdowd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual QA planning and execution often bottlenecks product delivery. This skill provides a repeatable framework to plan, execute, and document manual QA runs for a given task source, preserving evidence for audit and collaboration.

Core Features & Use Cases

  • Create a deterministic QA run plan from a task, including source validation, output destinations, and regression scope.
  • Execute the planned steps and save evidence to a local TestResults directory with run-001, plan.md, summary.md, and artifacts/.
  • Generate a comprehensive Auto QA Report summarizing results, issues, and artifacts for audit and traceability.

Quick Start

Provide a task source (Jira issue key, local path, or inline text) and specify the local destination for results to generate the plan and run.

Frequently Asked Questions about qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan and document manual QA tests for a Jira issue?▼

To plan manual QA tests for a Jira issue, you provide the issue key to generate a structured test plan, execute the steps, and save documented results to a local TestResults directory.

What is the best way to capture and organize manual QA evidence locally?▼

The best way to capture manual QA evidence is to output run artifacts into an organized local directory structure, using folders like run-001 with plan.md, summary.md, and an artifacts subfolder.

Can I generate a QA test plan from inline text or local files instead of Jira?▼

Yes, you can generate a QA test plan from inline text or local file paths. The tool validates the task source and creates a deterministic run plan regardless of the input format.

Does manual test management work without external dependencies or components?▼

Yes, manual test management works without external dependencies or components. It operates locally to generate test plans, package evidence, and report status directly to your file system.

How does a structured test plan handle regression scope and status reporting?▼

A structured test plan handles regression scope by validating the task source upfront, then executing the planned steps and generating a comprehensive Auto QA Report summarizing issues and artifacts for traceability.

When should I use an automated QA run framework instead of manual testing?▼

You should use an automated QA run framework when manual test planning bottlenecks product delivery, ensuring a repeatable process for plan creation, evidence packaging, and audit-ready status reporting.