qa-report

QA Test Planner

Plan and document QA deliverables — test plans, test cases, regression suites, Figma validations, and bug reports — in a structured format compatible with qa-execution execution.

Required Inputs

• qa-output-path (optional): Directory where all QA artifacts are stored. When provided, create the directory if it does not exist. When omitted, use the current working directory. This path must match the same argument passed to qa-execution when both skills are used together.

Shared Output Structure

All artifacts follow this directory layout, shared with qa-execution:

<qa-output-path>/qa/
├── test-plans/          # Test plan documents
├── test-cases/          # Individual test case files (TC-*.md)
├── issues/              # Bug reports (BUG-*.md)
├── screenshots/         # Visual evidence and Figma comparisons
└── verification-report.md  # Generated by qa-execution

Procedures

Step 1: Resolve Output Directory

1. If the user provided a qa-output-path argument, use that path.
2. Otherwise, default to the current working directory.
3. Create the qa/ subdirectory under the resolved path, then create qa/test-plans/, qa/test-cases/, qa/issues/, and qa/screenshots/ if they do not exist.

Step 2: Identify the Deliverable Type

Parse the user request to determine which deliverable to generate:

Request Pattern	Deliverable	Output Path
"Create test plan for..."	Test Plan	test-plans/
"Generate test cases for..."	Test Cases	test-cases/
"Build regression suite..."	Regression Suite	test-plans/
"Compare with Figma..."	Figma Validation	test-cases/ (TC-UI-*)
"Document bug..."	Bug Report	issues/

Step 3: Generate Test Plans

1. Read references/test_case_templates.md for the test plan structure.
2. Generate a test plan document with these mandatory sections:
   • Executive summary with objectives and key risks.
   • Scope definition (in-scope and out-of-scope).
   • Test strategy and approach.
   • Automation strategy covering which flows should become E2E, which remain manual-only, and which are blocked by environment gaps.
   • Environment requirements (OS, browsers, devices).
   • Entry criteria (what must be true before testing begins).
   • Exit criteria (what must be true before testing ends, including pass-rate thresholds and automation follow-up expectations for critical flows).
   • Risk assessment table (Risk, Probability, Impact, Mitigation).
   • Timeline and deliverables.
3. Write the plan to <qa-output-path>/qa/test-plans/<feature-slug>-test-plan.md.